Explore >> Select a destination
|
You are here 
|
www.ncameron.org | ||
| | | | |
pboyd.io
|
|
| | | | | Small Git commits are great when working, but they aren't so great when looking at the history. This post examines the commands to make a clean Git history. | |
| | | | |
8yd.no
|
|
| | | | | Git squash takes your commits and squashes them together, usually into one commit. Useful for creating one commit if you've got a lot of smaller commits that creates a messy Git history. Git rebase ... | |
| | | | |
blog.bloomca.me
|
|
| | | | | The blog of Seva Zaikov | |
| | | | |
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. Lets walk through an example. Lets write some history Lets start by creating an empty project in a new directory: $ git init . | ||
