Explore >> Select a destination
|
You are here 
|
codeinthehole.com | ||
| | | | |
di.nmfay.com
|
|
| | | | | analyzing the organization-wide impact of database schema changes, as a service | |
| | | | |
ricardolopes.net
|
|
| | | | | How using existing processes and tools can massively improve documentation and give you debugging superpowers. | |
| | | | |
www.aleksandrhovhannisyan.com
|
|
| | | | | It can be tempting to lump unrelated code changes into a single commit, but this makes it difficult to debug and time travel in Git. Prefer to write atomic commits that have a single responsibility. | |
| | | | |
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 . | ||
