You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+8-7
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,14 @@ Thanks for submitting a PR, your contribution is really appreciated!
2
2
3
3
Here's a quick checklist that should be present in PRs:
4
4
5
-
-[ ] Target: for bug or doc fixes, target `master`; for new features, target `features`;
5
+
-[ ] Add a new news fragment into the changelog folder
6
+
* name it `$issue_id.$type` for example (588.bug)
7
+
* if you don't have an issue_id change it to the pr id after creating the pr
8
+
* ensure type is one of `removal`, `feature`, `bugfix`, `vendor`, `doc` or `trivial`
9
+
* Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."
10
+
-[ ] Target: for `bugfix`, `vendor`, `doc` or `trivial` fixes, target `master`; for removals or features target `features`;
11
+
-[ ] Make sure to include reasonable tests for your change if necessary
6
12
7
-
Unless your change is trivial documentation fix (e.g., a typo or reword of a small section) please:
13
+
Unless your change is a trivial or a documentation fix (e.g., a typo or reword of a small section) please:
8
14
9
-
-[ ] Make sure to include one or more tests for your change;
10
15
-[ ] Add yourself to `AUTHORS`;
11
-
-[ ] Add a new entry to `CHANGELOG.rst`
12
-
* Choose any open position to avoid merge conflicts with other PRs.
13
-
* Add a link to the issue you are fixing (if any) using RST syntax.
14
-
* The pytest team likes to have people to acknowledged in the `CHANGELOG`, so please add a thank note to yourself ("Thanks @user for the PR") and a link to your GitHub profile. It may sound weird thanking yourself, but otherwise a maintainer would have to do it manually before or after merging instead of just using GitHub's merge button. This makes it easier on the maintainers to merge PRs.
0 commit comments