Conventional Commits

See how a minor change to our commit message format can make us a better programmers.

Format: <type>(<scope>): <subject>

feat(scope)!: add hat wobble
^--^ ^---^ ^  ^------------^
|    |     |  |
|    |     |  +-> Summary in present tense.
|    |     |
|    |     +-> Optional breaking change notation.
|    |
|    +-> Optional scope
|
+-------> Type: chore, docs, feat, fix, refactor, style, test or revert.

• 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
• revert: reverting existing comments; with references of the reverts in footer.

Reference

• Conventional Commits.
• Commit Message Format — Angular.
• Semantic Commit Messages.
• Karma’s Commit Style.