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 [...]
bump: (version update)chore: (updating grunt tasks etc; no production code change)ci: (changes to the build config)docs: (changes to the documentation)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)localize: (translations update)perf: (performance improvements)refactor: (refactoring production code, eg. renaming a variable)style: (formatting, missing semi colons, etc; no production code change)test: (adding missing tests, refactoring tests; no production code change)