Senior DevOps Engineer with 8.5+ years of experience. Otherwise an avid artist, reader, cinephile & football fan. Looking forward to connecting with everyone :)
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
Software Engineer @SciFY.
Live to learn something new -and write cleaner and more sustainable code- every day.
Passionate with learning and discovering new technologies, history, and psychology.
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
My commit message workflow
Shreyas Minocha ・ Jun 22 '18 ・ 4 min read
Thanks for the comment and the reference, Vinay!