Conventional Commits

Semantic Commit Message Format

<type>(<scope>): <subject> <scope> is optional

Example

feat: add hat wobble
^--^  ^------------^
|     |
|     +-> Summary in present tense.
|
+-------> Type: chore, docs, feat, fix, refactor, style, or test.

Type	Title	Description	Emoji	Release	Changelog
feat	Feature	New feature for the user, not a new feature for build script	✨	minor	true
fix	Bug Fix	Bug fix for the user, not a fix to a build script	🐛	patch	true
docs	Documentation	Changes to documentation	📚	patch if scope is readme	true
style	Style	Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)	💎	-	true
refactor	Code Refactoring	A code change that neither fixes a bug nor adds a feature	📦	-	true
perf	Performance Improvement	A code change that improves performance	🚀	patch	true
test	Test	Adding missing tests or correcting existing tests	🚨	-	true
build	Build	Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)	🛠	patch	true
ci	Continuous Integration	Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)	⚙️	-	true
chore	Chore	Other changes that don't modify src or test files	♻️	-	true
revert	Revert	Reverts a previous commit	🗑	-	true