Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

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

<scope> is optional

Example

feat: add hat wobble
^--^  ^------------^
|     |
|     +-> Summary in present tense.
|
+-------> Type: feat, improvement, fix, refactor, style, chore, test, or docs.

More Examples:

• feat: new feature for production
• improvement: production improvements without adding new features or correcting errors
• fix: bug fix for production
• refactor: refactoring production code, eg. renaming a variable
• style: formatting, missing semi colons, etc.
• chore: routine tasks related to the environment, libraries, scripts, etc.; no production code change
• test: adding missing tests, refactoring tests; no production code change
• docs: changes to the documentation; no production code change

Reference(s):

• https://seesparkbox.com/foundry/semantic_commit_messages
• http://karma-runner.github.io/1.0/dev/git-commit-msg.html
• https://www.conventionalcommits.org