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: chore, docs, feat, fix, refactor, style [...]
Or, with the scope:
feat (main page): add hat wobble
^--^ ^--------^ ^------------^
| | |
| +-> Scope (optional)
| |
| +-> Summary in present tense.
|
+-------> Type: chore, docs, feat, fix, refactor, style [...]
benchmark
: benchmarks-related codebuildfix
: e.g. add missing semicolonbump
: version updatechore
: e.g. updating grunt tasks; no production code changeconfig
: changes in configurationcross-cutting
: e.g. logging, dependency injectionci
: changes to the build/release configdeploy
: changes to deployment scriptsdocs
: changes to the documentationfeat
: new feature for the user, not a new feature for build scriptfix
: bug fix for the user, not a fix to a build scriptformat
: formatting, e.g. tabs to/from spaces, remove trailing whitespacelocalize
: translations updateperformance
: performance improvementsrefactor
: refactoring production codestyle
: change in frontend stylingtest
: adding missing tests, refactoring tests; no production code change