I have been guilty of writing short, pointless, and completely useless commit messages [before]. Stoked by a recent thread on StackOverflow about the worst commit message that one has ever authored, I looked into the commit log for a project I have been working on and subsequently maintaining for the last one year. I had to learn git as it had been decided that git would be used for version control for the project. Git indeed has been used since the onset of the project, but during the first three quarters working on the project, due to my unfamiliarity with working with distributed version control and shameful lack of knowledge of how git worked and a growing misperception that git is overly complicated for beginners to distributed version control, I used git sparingly (in the sense that I did not commit regularly, nor did I use any of its more than simple features) and ham-handedly. Nevertheless, skimming through the commit log from since the very initial commit, I found the following gems:
- minor changes
- some brief changes
- assorted changes
- lots and lots of changes
- another big bag of changes
- lots of changes after a lot of time
- LOTS of changes. period
Of course, the ever notorious “bug fixes” is also to be found at a lot of places.
On a happier note, since then, I have come to understand and utilise the full potential of git. And I no longer blurt out when authoring commit messages.