Nice article about commit messages. The basic rules you describe are important. I did the same until I found out about Conventional Commits Pattern. I would suggest that you try it at least once.
It has several benefits in terms of readability, maintainability, or if you want to revert to a specific point without investigating much.
Furthermore, it works with SemVer (semantic version). This means, you can generate changelog files automatically!
Nice article about commit messages. The basic rules you describe are important. I did the same until I found out about Conventional Commits Pattern. I would suggest that you try it at least once.
It has several benefits in terms of readability, maintainability, or if you want to revert to a specific point without investigating much.
Furthermore, it works with SemVer (semantic version). This means, you can generate changelog files automatically!
Some months ago, I wrote an article on Medium about that pattern: betterprogramming.pub/write-better...
Check it out! Until today, the feedback I got was really positive. I have also adopt the pattern at work and everyone loves it.