floraachy
/
pytest2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

GitHub: revisit issue/PR templates [ci skip] 

The motivation here is to not have the same boilerplate with PRs.
This commit is contained in:
Daniel Hahler 2019-04-23 18:00:16 +02:00
parent e87d3d70e2
commit 3df32e2732
2 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
.github/ISSUE_TEMPLATE.md vendored
View File

@ -1,8 +1,10 @@
<!--
Thanks for submitting an issue! Thanks for submitting an issue!
Here's a quick checklist in what to include: Here's a quick checklist for what to provide:
-->
- [ ] Include a detailed description of the bug or suggestion - [ ] a detailed description of the bug or suggestion
- [ ] `pip list` of the virtual environment you are using - [ ] output of `pip list` from the virtual environment you are using
- [ ] pytest and operating system versions - [ ] pytest and operating system versions
- [ ] Minimal example if possible - [ ] minimal example if possible

6
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -1,7 +1,9 @@
<!--
Thanks for submitting a PR, your contribution is really appreciated! Thanks for submitting a PR, your contribution is really appreciated!
Here's a quick checklist that should be present in PRs (you can delete this text from the final description, this is Here's a quick checklist that should be present in PRs.
just a guideline): (please delete this text from the final description, this is just a guideline)
-->
- [ ] Create a new changelog file in the `changelog` folder, with a name like `<ISSUE NUMBER>.<TYPE>.rst`. See [changelog/README.rst](https://github.com/pytest-dev/pytest/blob/master/changelog/README.rst) for details. - [ ] Create a new changelog file in the `changelog` folder, with a name like `<ISSUE NUMBER>.<TYPE>.rst`. See [changelog/README.rst](https://github.com/pytest-dev/pytest/blob/master/changelog/README.rst) for details.
- [ ] Target the `master` branch for bug fixes, documentation updates and trivial changes. - [ ] Target the `master` branch for bug fixes, documentation updates and trivial changes.