<aside> 💡 Original post: https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716

</aside>

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: chore, docs, feat, fix, refactor, style, or test.

More Examples:

• feat: (new feature)
• fix: (bug fix)
• docs: (changes to the documentation)
• style: (formatting, missing semi colons, etc)
• refactor: (refactoring production code, eg. renaming a variable)
• test: (adding missing tests, refactoring tests)
• chore: (daily or common tasks)

Commit message with description and breaking change footer

feat: allow provided config object to extend other configs

BREAKING CHANGE: `extends` key in config file is now used for extending other config files

Commit message with ! to draw attention to breaking change

refactor!: drop support for Node 6

References:

• https://www.conventionalcommits.org/