How to Write Commit Messages - Semantic Commit Messages

git

There is a nice format for commit messages. It is called semantic commit messages ¹.

Format: <type>(<scope>): <subject>
I haven’t seen people use scope a lot. So, I’ll stick to <type>: <subject.

These are the types ²:

• feat: (new feature for the user, not a new feature for build script)
• fix: (bug fix for the user, not a fix to a build script)
• docs: (changes to the documentation)
• style: (formatting, missing semi colons, etc; no production code change)
• refactor: (refactoring production code, eg. renaming a variable)
• test: (adding missing tests, refactoring tests; no production code change)
• chore: (updating grunt tasks etc; no production code change)

Footnotes

1. Semantic Commit Messages ↩

2. Semantic Commit Messages · GitHub ↩