This weekend’s developer drama is brought to us by Linus on the topic of GitHub pull requests and how they handle commit messages. It’s his project and the standards he sets are up to him. I have to admit, I’ve never looked into standards for commit messages. Nor the reason why Vim wraps my commit messages, or why the second line of the message is always in red. After reading his comments, I now understand.
I came across tpope’s blog post which explains how commit messages should be formated. Most of my time has been spent using git to interface with Subversion repositories for work, and commit messages are long stories of why these changes are required. I see the advantages of this style of commit messages, and will try use them from now on.