by Ciro Santilli (@cirosantilli, 34)
Option 1) git commit. Doh!!!
Option 2) git rebase. Basically allows you to do arbitrary modifications to the tree. The most important ones are:
Before: 
5 master
|
4 7 my-feature HEAD
| |
3 6
|/
2
|
1
Action: 
git rebase
After: 
7 my-feature HEAD
|
6
|
5 master
|
4
|
3
|
2
|
1
Ready to push with linear history!
Before: 
7 my-feature HEAD
|
6
|
5 master
|
4
|
3
|
2
|
1
Oh, commit 6 was crap: 
git rebase -i HEAD~2
Mark 6 to be modified.
After: 
7 my-feature HEAD
|
6v2
|
5 master
|
4
|
3
|
2
|
1
Better now, ready to push.
Note: history changes change all commits SHAs. All parents are considereEven time is considered. So is commit message/author. And obviously file contents. So now commit "7" will actually have a different SHA.
Before 
7 my-feature HEAD
|
6
|
5 master
|
4
|
3
|
2
|
1
Oh, commit 6 was just a temporary step, should be put together with commit 7: 
git rebase -i HEAD~2
Mark 6 to be squashed.
After: 
67 my-feature HEAD
|
5 master
|
4
|
3
|
2
|
1
Better now, ready to push.

Ancestors (10)

  1. Git tips
  2. Git
  3. List of version control systems
  4. Version control
  5. Software
  6. Computer
  7. Information technology
  8. Area of technology
  9. Technology
  10. Home

View article source

Discussion (0)

New discussion

There are no discussions about this article yet.

Articles by others on the same topic (0)

There are currently no matching articles.
See all articles in the same topic Create my own version