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

Skip to content

Pull Request template #8476

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Apr 14, 2017
Merged

Pull Request template #8476

Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
8e796b3
Merge pull request #20 from matplotlib/master
story645 Apr 13, 2017
17bc9fe
Create PULL_REQUEST_TEMPLATE.md
story645 Apr 13, 2017
90096e0
Update PULL_REQUEST_TEMPLATE.md
story645 Apr 13, 2017
5a96eff
Update PULL_REQUEST_TEMPLATE.md
story645 Apr 13, 2017
f155f56
point to devdocs instead of devel
story645 Apr 13, 2017
341767f
Update PULL_REQUEST_TEMPLATE.md
story645 Apr 13, 2017
408d78b
shortened, moved to comments, removed links
story645 Apr 13, 2017
aabe383
Update PULL_REQUEST_TEMPLATE.md
story645 Apr 13, 2017
adbc03f
language tidying
story645 Apr 13, 2017
4bf429b
Update PULL_REQUEST_TEMPLATE.md
story645 Apr 14, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
Thank you so much for your PR! To help us review, fill out the form to the best of your ability. Also, please make use of the development guide at http://matplotlib.org/devdocs/devel/index.html

<!--- Provide a general summary of your changes in the Title above, for example "Raises ValueError on Non-Numeric Input to set_xlim". Please avoid non-descriptive titles such as "Addresses issue #8576"-->

## PR Summary
<!--- Please provide at least 1-2 sentences describing the pull request in detail. Why is this change required? What problem does it solve? -->
<!--- If it fixes an open issue, please link to the issue here. -->

## PR Checklist
- [ ] Has Pytest style unit tests
- [ ] Code is PEP 8 compliant
- [ ] New features are documented, with examples if plot related
- [ ] Documentation is sphinx and numpydoc compliant
- [ ] Added an entry to doc/users/whats_new.rst if major new feature
- [ ] Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

We understand that PRs can sometimes be overwhelming, especially as the reviews start coming in. Please let us know
if the reviews are unclear or the recommended next step seems overly demanding , or if you would like help in addressing a reviewer's comments. And please ping us if you've been waiting too long to hear back on your PR!