<type>(<scope>): <subject>
<body>
<footer>
- feat: new features
- fix: for bug fixes
- build: changes that affect the build system or external dependencies
- ci: changes to our CI configuration files and scripts
- docs: documentation changes
- perf: for performance improvements
- style: for code style stuff
- refactor: for code refactoring
- test: for adding missing tests
- chore: for relases, dependencies, stuff
- use imperative, present tense (change, not changed or changes)
- don't capitalize first letter
- no . at the end
- use imperative (view subject)
- include motivation for the change and contrast with previous behavior
- should include reference to issues (github or JIRA or whatever)
- should include breaking changes (should start with
BREAKING CHANGE:
)