How (and why!) to keep your Git commit history clean
June 07, 2018
Commits are one of the key parts of a Git repository, and more so, the commit message is a life log for the repository. As the project/repository evolves over time (new features getting added, bugs being fixed, architecture being refactored), commit messages are the place where one can see what was changed and how. So it’s important that these messages reflect the underlying change in a short, precise manner.
I wrote a detailed guide on keeping Git commit history clean which was originally published on GitLab Blog and later on DZone.