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:
@marijoo I think changing a headline should be handled similarly to a change in UI.
For example, if one of the UI buttons were misaligned, that would be a
fix
. If you introduce a new button, that would be afeature
. It should be the same for UI text as well. Fixing a typo should better be afix
. And introducing new text, or updating an existing text should be afeature
.chore
,docs
, orrefactor
are for the development side of things. But a change in the headline is a user-facing change.