diff options
| author | lovetox <philipp@hoerist.com> | 2022-08-14 09:42:17 +0300 |
|---|---|---|
| committer | lovetox <philipp@hoerist.com> | 2022-08-14 09:42:17 +0300 |
| commit | 996c43464d7e2cf3f5090f31a97d8aec6c243725 (patch) | |
| tree | d9505456a938c8c2b79bb1fb1283badf6646ab35 /CONTRIBUTING.md | |
| parent | 0c95e7c508f801ae9d31b481ba4e975f7ca9c750 (diff) | |
chore: Add new commit prefixes
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index fac8eed68..ff8e55d9c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -34,15 +34,22 @@ A good article regarding [good commit messages](https://chris.beams.io/posts/git Every commit message must be prefixed with one of the following tags: -- ci (ci related changes) -- cq (code quality changes e.g. formatting, typing, codestyle) +Changelog relevant + - feat (a new feature was added) - fix (something was fixed) - perf (performance related changes) - imprv (improvements) +- change (existing functionality was changed) + +Prefixes for development + +- new (new code, but the end user will not notice) +- ci (ci related changes) +- cq (code quality changes e.g. formatting, typing, codestyle) +- cfix (code fixes which should not show up in the changelog) - refactor (code was changed, but the end user will not notice) - chore (reoccuring tasks which need to be done) -- change (existing functionality was changed) - release (only used for release commits) - other |