[HEADER]  <Commit Type> <Scope (files affected by the change)>: <short summary>

[Commit Message Body] Issue, Change, Motive, Comparison

[Commit Message Footer] Reference

• Header —
• Commit Message Body —
• Commit Message Footer —

Things to keep in mind

1. Use “git init” in a project folder that you know for sure has the correct name otherwise rename the folder before initializing a git project.
2. Reformat your code every time you save the code. use a consistent format style.
3. Commit only when you are sure that the changes you have made are of significant nature. otherwise, there's no need to clog up the commit history with "fixed a typo" like commit messages.
4. Follow a definite commit message convention. Tip: you can use git hooks to remind you of the convention.
5. Remember to regularly push your code to the cloud once you feel that the changes are significant but be very careful before you push your changes upstream unless you want to frequently encounter merging errors.