forked from pymc-devs/pymc-examples
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update PULL_REQUEST_TEMPLATE.md (pymc-devs#233)
* Update PULL_REQUEST_TEMPLATE.md * Update PULL_REQUEST_TEMPLATE.md * Update PULL_REQUEST_TEMPLATE.md * Update PULL_REQUEST_TEMPLATE.md * Update per feedback * update link to issue checkpoint Co-authored-by: Oriol (ZBook) <oriol.abril.pla@gmail.com>
- Loading branch information
1 parent
ea6f8ee
commit d1bf72a
Showing
1 changed file
with
11 additions
and
11 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,16 +1,16 @@ | ||
## Description | ||
<!-- Thank you so much for your PR! | ||
# {Insert Description} | ||
<!-- Thank you so much for your PR to pymc-examples! | ||
To help us review your contribution, please provide the info requested below. Otherwise, | ||
we may leave reviews that are actually out of the scope of the current PR. --> | ||
To make the merge process smoother we've provided some links and a checklist below. | ||
Addresses issue #xxx and aims to advance it to <!-- Tracker column: General Updates, ArviZ, Best Practices --> | ||
|
||
<!-- We understand that PRs can sometimes be overwhelming, especially as the reviews start coming in. | ||
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, | ||
if you would like help in addressing a reviewer's comments, | ||
or if you have been waiting too long to hear back on your PR. | ||
or if you have been waiting too long to hear back on your PR. --> | ||
|
||
+ [ ] Notebook follows style guide https://github.com/pymc-devs/pymc/wiki/PyMC-Jupyter-Notebook-Style-Guide | ||
+ [ ] PR description contains a link to the relevant issue: a tracker one for existing notebooks or a proposal one for new notebooks | ||
|
||
|
||
Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at | ||
- https://github.com/arviz-devs/arviz/blob/main/CONTRIBUTING.md | ||
- https://github.com/arviz-devs/arviz/blob/main/CODE_OF_CONDUCT.md --> | ||
### Helpful links | ||
* https://github.com/pymc-devs/pymc-examples/blob/main/CONTRIBUTING.md |