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.
- โ Improved, Fixed, Updated
- โ Improve, Fix, Update
Describe why the commit is necessary.
Describe what the commit does. Refer to tickets/issues if applicable.
Example:
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! ๐ค
Top comments (10)
Thank you for the post. Writing good git commits is really important. There is a git repo regarding it github.com/joelparkerhenderson/git... and also you can create a commit template and share it with the community ๐ฅณ
Oh, I didn't knew that.
Thanks!
Knowledge in return of knowledge, haha.
Good advice, I like the "reason" part, people usually leave that out and that's the important bit - we can see what the code changes are, and figure out what the commit is supposed to do, but why is much harder to work out, especially when browsing through older code base when original developers are not available to answer the questions anymore.
Exactly! Thanks for reading.
Implement form validation to prevent unnecessary API calls that results in error because of validation
Something like this?
"Implement form validation to prevent unnecessary API calls" should do fine. Thanks for the comment!
Thanks for sharing.
Appreciate those kind words!
This help meใTHS
Thanks for reading.