/git-commit-convention

The seven rules of a great Git commit message

Best Practices

1

https://www.freecodecamp.org/news/writing-good-commit-messages-a-practical-guide/

feat: The new feature you're adding to a particular application
fix: A bug fix
style: Feature and updates related to styling
refactor: Refactoring a specific section of the codebase
test: Everything related to testing
docs: Everything related to documentation
chore: Regular code maintenance.[ You can also use emojis to represent commit types]

2

https://github.com/andela/bestpractices/wiki/Git-naming-conventions-and-best-practices

3

https://chris.beams.io/posts/git-commit/

The seven rules of a great Git commit message
  1. Separate subject from body with a blank line
  2. Limit the subject line to 50 characters
  3. Capitalize the subject line
  4. Do not end the subject line with a period
  5. Use the imperative mood in the subject line
  6. Wrap the body at 72 characters
  7. Use the body to explain what and why vs. how