Write better commit messages

One of the most valuable things that I was taught as a software developer, is to write “good” Git commit messages. Obviously “good” is very subjective, so let me dive into it a bit. I want to explain what I think a “good” message is, but also why I think it’s relevant that you write a good message. I’m hoping that towards the end of this post, I could convince at least one other person to improve their workflow and write more relevant and thoughtful commit messages. If the rest of this post feels weirdly familiar, it’s because my thoughts are mostly a rehash of Chris Beams’ “How to write a Git Commit Message”. That’s the one post that got me up to speed and then I have to shout out my friend Omar who hammered the points home over countless reviews. Thanks, man! What is “good” anyway? The most important rule that I follow is, that a commit message should describe why something was done and not elaborate how something was done. This is the most common mistake I see out in the wild. It’s…