A commit guideline will help you to put an architecture to your commit. There are a lot of others a few of them are Conventional Commits, and Angular Guideline. In my case, I choose this simple one from Udacity. If you want to have a clear git commit history, I recommend you to follow a guideline. So, "-m 'title' "is to write the short title of the commit, and "-m 'description' "is to write the description if you need to give more details. It's the same as before, but with a second part for the description. If you are not using a git software, you should know that you can create detailed commit by typing this command:Įnter fullscreen mode Exit fullscreen mode In the case you need to detail a lot, I recommend you to use the description part of the commit.ĪDDITIONAL INFORMATION: I want to share with you more details on the 'git commit' command. Take the time to reread your code to write what you did. I recommend you to use simple English to go straight to the point. When you are writing a commit, try to be as transparent as possible. It will be easier for you to go back to previous work. The ideal is to have each change in a different commit. These tools are not perfect, but they will remove most of your errors. If you are writing in English, you can use Grammarly, Reverso, or GrammarCheck. To do this, I recommend you to use a grammar tool. It's never pleasant to read a message full of errors. Every time you want to commit, take the time to refer to this list. If you want to write a good commit message, you need to follow some rules. Probably the next part of the series will be on this, if you want to be updated, you can follow me on Twitter. I share with you a few tools to do it: Github Changelog Generator, Git Chglog, Auto Changelog, and Conventional Changelog.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |