Semantic Git commits start with a semantic tag and use an imperative voice. Git commit messages should be prefixed with one the following tags:
feat: - implement new features for endusers
fix: - bug fix for endusers (not a build-process fix)
docs: - update to project documentation
style: - update code formatting (indentation, tabs vs spaces, etc.)
refactor: - refactoring of code
test: - adding or updating tests
chore: - updates to build processcommon type uses include:
feat: a new feature for the user, not a new feature for a build script
fix: bug fix for the user, not a fix to a build scripts
refactor: refactoring production code
chore: updating gulp tasks etc.; no production code change
docs: changes to documentation
style: formatting, missing semicolons, etc.; no code change
perf: code improved in terms of processing performance
vendor: update version for dependencies, packages.
test: adding missing tests, refactoring tests; no production code change