Excellent article, Paul!
Writing a meaningful git commit message is a good practice because it not only helps in debugging issues later (especially if it's been caused by one's own git commit) but also is one form of effective documentation that can be referred by anyone (e.g: new team-members) to get up-to speed on a project.
While I'm sure there are numerous articles on the internet towards this, here's one I found to add more detail
Thanks for the comment and the reference, Vinay!
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.