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 test.
More Examples:
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)
References:
I'd say the commit type is more like an enum:
Thinking like this, semantically maybe the type should be capitalised, or even all upper-case? You could also imagine the types to be like the keys of a JS object, and then you'd be convinced they should be camelCased!
I find capitalisation in commit messages to be frivolous, but as long as you're consistent, feel free to enforce your own style. Lower-case is simple.