type(branch): subject
Example: feat(backoffice): support full game editing
Must be one of the following:
feat
: A new featurefix:
A bug fixdocs:
Documentation only changesstyle:
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)refactor:
A code change that neither fixes a bug nor adds a featureperf:
A code change that improves performancetest:
Adding missing or correcting existing testschore:
Changes to the build process or auxiliary tools and libraries such as documentation generation
The subject contains a succinct description of the change:
- Imperative, present tense (changed/changes ❌ - change ✔️)
- Don't capitalize first letters
- No dot (.) needed at the end