2018-02-24 00:48:21 +01:00
|
|
|
<!--
|
|
|
|
|
Thanks for your contribution!
|
|
|
|
|
Please read this comment in its entirety. It's quite important.
|
|
|
|
|
|
|
|
|
|
# Pull Request title
|
|
|
|
|
|
|
|
|
|
It should be in the following format:
|
2018-05-14 02:55:35 +02:00
|
|
|
|
2018-02-24 00:48:21 +01:00
|
|
|
```
|
|
|
|
|
bpo-NNNN: Summary of the changes made
|
|
|
|
|
```
|
2018-05-14 02:55:35 +02:00
|
|
|
|
2018-02-24 00:48:21 +01:00
|
|
|
Where: bpo-NNNN refers to the issue number in the https://bugs.python.org.
|
|
|
|
|
|
|
|
|
|
Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.
|
|
|
|
|
|
|
|
|
|
# Backport Pull Request title
|
|
|
|
|
|
|
|
|
|
If this is a backport PR (PR made against branches other than `master`),
|
2017-09-07 02:27:05 +02:00
|
|
|
please ensure that the PR title is in the following format:
|
2018-05-14 02:55:35 +02:00
|
|
|
|
2017-09-29 20:16:38 +02:00
|
|
|
```
|
|
|
|
|
[X.Y] <title from the original PR> (GH-NNNN)
|
|
|
|
|
```
|
2018-05-14 02:55:35 +02:00
|
|
|
|
2017-09-29 20:16:38 +02:00
|
|
|
Where: [X.Y] is the branch name, e.g. [3.6].
|
2017-09-07 02:27:05 +02:00
|
|
|
|
|
|
|
|
GH-NNNN refers to the PR number from `master`.
|
|
|
|
|
|
2018-02-24 00:48:21 +01:00
|
|
|
-->
|
