/explore
|
You are here 
|
andrew.yurisich.com | ||
| | | | |
blog.bloomca.me
|
|
| | | | | The blog of Seva Zaikov | |
| | | | |
www.simpleprimate.com
|
|
| | | | | The other day I found myself having serious trouble publishing a new post to my blog. I was able to solve the problem through the use of Git rebase and I thought I would share my experience in case somebody else happens to go through the same thing. | |
| | | | |
andreabergia.com
|
|
| | | | | Git has an excellent tool designed to help you reorder the commit history: interactive rebase. This can be excellent if you want to keep the history clean, so that it helps other programmers understand the logic behind the changes rather than the actual sequence of commits. Let's walk through an example. Let's write some history Link to heading Let's start by creating an empty project in a new directory: | |
| | | | |
it-notes.dragas.net
|
|
| | | |||
