See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
feat π: add hat wobble
^--^ ^------------^
| |
| +-> Summary in present tense.
|
+-------> Type: upgrade, chore, docs, feat, fix, refactor, style, or test.
More Examples:
upgrade π
: (updgrade dependencies)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)
Reference(s):