
Anatomy of a “Good” commit message
Current thinking about what should be in a commit
Git is a tool that’s fundamental to my software development workflow. In the 5 years I have been a developer I have swapped out almost all my tools, but I have found nothing super to git. It’s adoption, tooling, speed and reliability have made it a supremely difficult competitor to beat in terms of version control.
One of the more useful features of git is the “Commit Message”. As each change is applied the software repository, it is annotated with a message. Users can put whatever they like in this message, however there are some practices that make it much easier when reviewing the history of the repository.
Bait and Switch: I’ve now moved all my posts to andrewhowden.com. You can read this post further over there!