test_ok2/.github/PULL_REQUEST_TEMPLATE.md

<!--
Thanks for submitting a PR, your contribution is really appreciated!

Here is a quick checklist that should be present in PRs.

- [ ] Include documentation when adding new features.
- [ ] Include new tests or update existing tests when applicable.
- [X] Allow maintainers to push and squash when merging my commits. Please uncheck this if you prefer to squash the commits yourself.

Unless your change is trivial or a small documentation fix (e.g., a typo or reword of a small section) please:

- [ ] 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.

  Write sentences in the **past or present tense**, examples:

  * *Improved verbose diff output with sequences.*
  * *Terminal summary statistics now use multiple colors.*

  Also make sure to end the sentence with a `.`.

- [ ] Add yourself to `AUTHORS` in alphabetical order.
-->
GitHub: revisit issue/PR templates [ci skip] The motivation here is to not have the same boilerplate with PRs. 2019-04-24 00:00:16 +08:00			`<!--`
Add issue and PR GitHub templates 2016-02-19 04:26:38 +08:00			`Thanks for submitting a PR, your contribution is really appreciated!`

Small change to test if pushing directly to master is disabled 2019-05-24 23:11:15 +08:00			`Here is a quick checklist that should be present in PRs.`
Add issue and PR GitHub templates 2016-02-19 04:26:38 +08:00
Add changelog/README.rst and streamline our PR template text This streamlines the PR template text and adds a more in-depth explanation about how the changelog entries work because this topic is a common source of confusion: - How to name the files. - Which formatting to use (people in general assume it is Markdown). - Recommend adding `.rst` extension to changelog files to help with the above (`towncrier` doesn't care). This was heavily inspired by the excellent python-trio/trio docs. 2018-02-07 08:13:04 +08:00			`- [ ] Include documentation when adding new features.`
			`- [ ] Include new tests or update existing tests when applicable.`
Explicitly state on the PR template that we can squash commits (#6662) * Explicitly state on the PR template that we can squash commits This way we don't need to ask every time, and users who for some reason would not like us to squash their commits can explicitly state so. 2020-02-04 01:35:50 +08:00			`- [X] Allow maintainers to push and squash when merging my commits. Please uncheck this if you prefer to squash the commits yourself.`
Mention small doc fixes don't need tests/changelog entries in PR template 2016-10-06 02:36:38 +08:00
Update text in PR template 2019-11-14 17:36:47 +08:00			`Unless your change is trivial or a small documentation fix (e.g., a typo or reword of a small section) please:`
Mention small doc fixes don't need tests/changelog entries in PR template 2016-10-06 02:36:38 +08:00
Make it clear that small typos in docs don't require a CHANGELOG entry From: https://github.com/pytest-dev/pytest/pull/5273#issuecomment-493076587 2019-05-16 21:54:50 +08:00			- [ ] 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.
Improve instructions on how to write CHANGELOG entries This makes easier for contributors to get the CHANGELOG entry right the first time. 2019-11-20 01:04:21 +08:00
			`Write sentences in the past or present tense, examples:`

			`* Improved verbose diff output with sequences.`
			`* Terminal summary statistics now use multiple colors.`

			Also make sure to end the sentence with a `.`.

Update text in PR template 2019-11-14 17:36:47 +08:00			- [ ] Add yourself to `AUTHORS` in alphabetical order.
Make whole checklist a comment to avoid incomplete TODOs in PRs 2019-11-14 18:01:40 +08:00			`-->`