Most of us use some sort of version control system; if you’re doing devops-y stuff, it’s likely you are using git. Using these follows a familiar pattern: You do some work, commit the work, and push it to a remote repository, perhaps creating a Pull Request or Merge Request for review.
Here’s the thing – what you put into your commit messages matters. Those commit messages are either love letters to your future self, or hate mail. You’ve heard the maxim that code is written once and read many times, and the same goes for commit messages. Putting some thought into what you put into your commit messages (and making them readable) is important.
In this five minute ignite talk, you’ll learn the anatomy of a good commit message and how to structure your work for maximum impact to others (and yourself!) that have to ready them. We’ll also touch briefly on some commit anti-patterns.
So get commit-ted to crafting useful commit messages!