|
| 1 | +# <type>(<scope>): <subject> |
| 2 | +# |
| 3 | +# <body> |
| 4 | +# |
| 5 | +# <footer> |
| 6 | + |
| 7 | +# Type should be one of the following: |
| 8 | +# * feat: a new feature |
| 9 | +# * fix: a bug fix |
| 10 | +# * docs: documentation only changes |
| 11 | +# * style: changes that do not affect the meaning of the code |
| 12 | +# * refactor: a code change that neither fixes a bug nor adds a feature |
| 13 | +# * perf: a code change that improves performance |
| 14 | +# * test: adding missing tests or correcting existing tests |
| 15 | +# * build: changes that affect the build system or external dependencies |
| 16 | +# * ci: changes to our ci configuration files and scripts |
| 17 | +# * chore: other changes that don't modify src or test files |
| 18 | +# * revert: reverts a previous commit |
| 19 | +# |
| 20 | +# Scope is optional, but should be one of the following: |
| 21 | +# * assets: changes to assets (images, fonts, etc.) |
| 22 | +# * audio: changes relating to sound or music |
| 23 | +# * core: changes to the core game functionality |
| 24 | +# * deps: changes to dependencies |
| 25 | +# * dev: changes to the development environment |
| 26 | +# * lint: changes that only affect linting such as auto-formatting |
| 27 | +# * mtx: changes to monetization or in-game purchases |
| 28 | +# |
| 29 | +# Subject line rules: |
| 30 | +# * Use imperative mood: "change" not "changed" nor "changes" |
| 31 | +# * No dot (.) at the end |
| 32 | +# * Limit to 72 characters |
| 33 | +# * No capitilization in the subject aside from issue references |
| 34 | +# |
| 35 | +# Body rules: |
| 36 | +# * Wrap at 72 characters |
| 37 | +# * Use imperative mood |
| 38 | +# * Explain what and why vs. how |
| 39 | +# |
| 40 | +# Footer rules: |
| 41 | +# * Reference issues and pull requests liberally |
| 42 | +# * Use "Fixes #123" or "Closes #123" for issues |
| 43 | +# * Use "BREAKING CHANGE:" for breaking changes |
0 commit comments