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
- A new feature for the user, not a new feature for the build scriptfix
- A bug fix for the user, not a fix to a build scriptdocs
- Changes to the documentationstyle
- Code formatting, white-space, missing semi-colons, etc; no production code changerefactor
- A code change that neither fixes a bug nor adds a feature, eg. renaming a variabletest
- Adding missing tests or correcting existing testschore
- Other changes that don't modify src or test files
Extras:
perf
- A code change that improves performance or optimizesbuild
- Changes that affect the build system or external dependencies, eg. gulp, broccoli, npmci
- Changes to our CI configuration files and scripts, eg. Travis, Circle, BrowserStack, SauceLabsrevert
- Change back to the previous commitlicense
- Edits regarding licensing, no production code change
References: