Your Git Commit Messages Suck! Here's What To Fix šŸ› 

Arjun Vijay Prakash - Mar 19 - - Dev Community

Writing commit messages is like a daily exercise you have to practice as a programmer.

Even if you are writing code for fun, it's important to realise this small detail reflects your developer personality in general.

Writing quality commits is what separates the average developer from the extraordinary one.


Do this! šŸ‘‡

Write better Git commit messages with these things in mind:

  • Start with a verb and use the present tense.
  1. āŒ Improved, Fixed, Updated
  2. āœ… Improve, Fix, Update
  • Describe why the commit is necessary.

  • Describe what the commit does. Refer to tickets/issues if applicable.

Example:

Image


Final Thoughts šŸ™Œ

Comment down some tips on writing Git commits you use as a Software Developer!

Also, insights on this short-form content would be appreciated.

I hope you liked the article! ā¤ļø

Connect with me on linktree.

Happy Coding! šŸš€
Thanks for 23102! šŸ¤—

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .