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:
@dpinol Performance improvements make the app faster, which can be considered a
feat
orfix
, depending on the severity. If the app was unusable slow, it was a fix, if the app was fast, but now is faster, it's a feature. Not gonna say it's wrong to pickperf
, but I think that is what semantic commit messages boil down to.It's basically a similar case to
tweak
. We were thinking that it would make sense, but after a long back and forth, atweak
can also be afix
or afeat
, depending on the severity.