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:
@snurfer0 by definition,
chore
changes stuff that won't change the behavior of the build, like reformatting code or adding stuff around the build tools like helper scripts, etc. Another example is modifying the.gitignore
.In case of adding logger calls, I think
feat
would be more appropriate. The end-user might not notice the change, but the behavior has changed and the user can still experience that. It's a feature, the app now logs more steps.