Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 80c4496

Browse files
committed
DOCS: pr template grammar and visual organization
1 parent 427cca4 commit 80c4496

File tree

1 file changed

+22
-19
lines changed

1 file changed

+22
-19
lines changed

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 22 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,36 @@
11
## PR Summary
22

33
<!--
4-
Please provide at least a 1-2 sentence summary of the purpose of the PR.
4+
Thank you so much for your PR! Please summarize the purpose of the PR here
5+
using at least 1-2 sentences.
6+
7+
To help us review your pull request, make sure:
8+
9+
- The PR title descriptively summarizes the changes.
10+
- e.g. "Raise `ValueError` on non-numeric input to `set_xlim`"
11+
- Please don't use non-descriptive titles such as "Addresses issue #8576".
12+
- The PR summary includes:
13+
- How the PR implements any changes.
14+
- Why these changes are necessary.
15+
- The PR is not out of master, but out of a separate branch.
16+
- e.g. `your-user-name:non-numeric-xlim -> matplotlib:master`
17+
- Optional: PR cross-links related issues.
518
-->
619

7-
820
## PR Checklists
921

1022
<!-- Feel free to delete any checkboxes that do not apply to this PR. -->
1123

1224
New code:
1325

14-
- [ ] Has Pytest style unit tests (and `pytest lib/matplotlib/tests` passes)
15-
- [ ] Code is [Flake 8](http://flake8.pycqa.org/en/latest/) compliant (run `flake8` on changed files to check)
16-
- [ ] Code is documented, with examples if plot related
26+
- [ ] has Pytest style unit tests (and `pytest lib/matplotlib/tests` passes)
27+
- [ ] is [Flake 8](http://flake8.pycqa.org/en/latest/) compliant (run `flake8` on changed files to check)
28+
- [ ] is documented, with examples if plot related
1729

1830
New documentation:
1931

20-
- [ ] Documentation is sphinx and numpydoc compliant (the docs should [build](https://matplotlib.org/devel/documenting_mpl.html#building-the-docs) without error)
21-
- [ ] Documentation conforms to matplotlib style conventions. (If you have `flake8-docstrings` and `pydocstyle<4` installed, run `flake8 --docstring-convention=all` on changed files to check).
32+
- [ ] is sphinx and numpydoc compliant (the docs should [build](https://matplotlib.org/devel/documenting_mpl.html#building-the-docs) without error)
33+
- [ ] conforms to matplotlib style conventions (if you have `flake8-docstrings` and `pydocstyle<4` installed, run `flake8 --docstring-convention=all` on changed files to check).
2234
<!--
2335
- If you are contributing fixes to docstrings, please pay attention to
2436
http://matplotlib.org/devel/documenting_mpl.html#formatting. In particular,
@@ -28,20 +40,11 @@ New documentation:
2840

2941
New features:
3042

31-
- [ ] Have an entry in `doc/users/next_whats_new/` (follow instructions in `doc/users/next_whats_new/README.rst`)
43+
- [ ] have an entry in `doc/users/next_whats_new/` (follow instructions in `doc/users/next_whats_new/README.rst`)
3244

3345
API changes:
3446

35-
- [ ] Documented in `doc/api/api_changes_[NEXT_VERSION]` if API changed in a backward-incompatible way (follow instructions in `doc/api/api_changes_[NEXT_VERSION]/README.rst`)
36-
37-
<!--
38-
Meta:
39-
40-
- PR title descriptively summarizes the changes. (For example, prefer "Raise `ValueError` on non-numeric input to `set_xlim`" to "Addresses issue #8576").
41-
- PR has at least a 1-2 sentence summary.
42-
- PR is not out of master, but out of a separate branch (e.g. `your-user-name:non-numeric-xlim -> matplotlib:master`)
43-
- Optional: PR cross-links related issues.
44-
-->
47+
- [ ] are documented in `doc/api/api_changes_[NEXT_VERSION]` if API changed in a backward-incompatible way (follow instructions in `doc/api/api_changes_[NEXT_VERSION]/README.rst`)
4548

4649
<!--
4750
If you have further questions:
@@ -53,7 +56,7 @@ If you have further questions:
5356
https://matplotlib.org/devel/gitwash/development_workflow.html.
5457
5558
We understand that PRs can sometimes be overwhelming, especially as the
56-
reviews start coming in. Please let us know if the reviews are unclear,
59+
reviews start coming in. Please let us know if the reviews are unclear,
5760
the recommended next step seems overly demanding, you would like help in
5861
addressing a reviewer's comments, or you have been waiting too long to hear
5962
back on your PR.

0 commit comments

Comments
 (0)