Skip to content

Commit

Permalink
docs: allow chore prefix in contribution commit guidelines
Browse files Browse the repository at this point in the history
  • Loading branch information
lfleischmann authored Nov 18, 2022
1 parent 8742ec1 commit 3c1568f
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,17 +133,18 @@ The commit message headline should have the following structure:
│ │
│ └─⫸ Commit Scope: optional
└─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test
└─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test|chore
```
The `<type>` should be one of the following:
* **build**: Changes that affect the build system or external dependencies
* **build**: Changes that affect the build system
* **ci**: Changes that affect the CI workflows (e.g. changes to `.github` CI configuration files)
* **docs**: Documentation only changes (this includes both content in the `docs` as well as changes to readmes)
* **feat**: A new feature
* **fix**: A bug fix
* **perf**: A code change that improves performance
* **refactor**: A code change that neither fixes a bug nor adds a feature
* **test**: Adding missing tests or correcting existing tests
* **chore**: Anything that cannot be categorized properly using the above prefixes (e.g. increasing versions)

The `<scope>` is optional. If present, it should be the name of the (npm) package or directory affected by the changes of
the commit.
Expand Down

0 comments on commit 3c1568f

Please sign in to comment.