-
Notifications
You must be signed in to change notification settings - Fork 172
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2,159 changed files
with
24,370 additions
and
16,072 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,41 +1,11 @@ | ||
PLEASE FOLLOW THE CHECKLIST BELOW WHEN CREATING A NEW PULL REQUEST. THE | ||
CHECKLIST IS FOR YOUR INFORMATION AND MUST BE REMOVED BEFORE SUBMITTING THE PULL | ||
REQUEST. | ||
PLEASE DESCRIBE YOUR CHANGES. | ||
THIS MESSAGE ENDS UP AS THE COMMIT MESSAGE. | ||
DO NOT USE @-MENTIONS HERE! | ||
|
||
## Checklist | ||
--- END COMMIT MESSAGE --- | ||
|
||
- [ ] Does the PR title follow the `<prefix>: title` scheme? | ||
Any further description goes here, @-mentions are ok here! | ||
|
||
The prefix must be one of: | ||
|
||
- `fix`: for a bugfix | ||
- `feat`: for a new feature | ||
- `refactor`: for an improvement of an existing feature | ||
- `perf`, `test`: for performance- or test-related changes | ||
- `docs`: for documentation-related changes | ||
- `build`, `ci`, `chore`: as appropriated for infrastructure changes | ||
|
||
- [ ] Does this modify the public API as defined in `docs/versioning.rst`? | ||
|
||
- [ ] Does the PR title contain a `!` to indicate a breaking change? | ||
- [ ] Is there section starting with `BREAKING CHANGE:` in the PR body | ||
that explains the breaking change? | ||
|
||
- [ ] Is the PR ready to be merged? | ||
|
||
- [ ] If not: is it marked as a draft PR? | ||
|
||
- [ ] Does this PR close an existing issue? | ||
|
||
- [ ] Is the issue correctly linked so it will be automatically closed | ||
upon successful merge (See closing keywords link in the sidebar)? | ||
|
||
- The CI will initially report a missing milestone. One of the maintainers will | ||
handle assigning a milestone for book-keeping. | ||
|
||
- An automated workflow will assign labels based on changed files, and whether | ||
or not reference files were changed. These do not have to be set manually. | ||
|
||
- If you push updates, and you know they will be superseded later on, consider adding | ||
`[skip ci]` in the commit message. This will instruct the CI system not to run any | ||
jobs on this commit. | ||
- Use a *conventional commits* prefix: [quick summary](https://www.conventionalcommits.org/en/v1.0.0/#summary) | ||
- We mostly use `feat`, `fix`, `refactor`, `docs`, `chore` and `build` types. | ||
- A milestone will be assigned by one of the maintainers |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.