Writing good commit messages
Here are few rules I follow when writing commit message.
- include type of work (FEATURE, BUG, TASK etc.)
- if using project management tool, include reference number to a card/ticket
- make your commit message meaningful
- explain the reason, purpose and context for changes
- commit frequently (frequent commits could be used for context if you squash before merging)
The goal is to be able to look at commit message after few months and get a clear picture about changes.
Thanks for reading!