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 that chore fits better. These are not changes that a client would really see. Now, granted, refactoring also doesn't really change the visible side of things, but I always imagined it to be related to the code we write instead of infrastructural changes like changing a library.
IMHO, the best option for stuff like this is probably a separate label that didn't mean much sense in the context of Angular, but makes a lot of sense in the server side development: 'infra' for infrastructure.
I think I will add 'infra' to my tool sema.