2018-02-23 23:48:21 +00: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 00:55:35 +00:00
|
|
|
|
2018-02-23 23:48:21 +00:00
|
|
|
```
|
|
|
|
|
bpo-NNNN: Summary of the changes made
|
|
|
|
|
```
|
2018-05-14 00:55:35 +00:00
|
|
|
|
2018-02-23 23:48:21 +00: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
|
|
|
|
|
|
2021-05-03 22:36:55 +00:00
|
|
|
If this is a backport PR (PR made against branches other than `main`),
|
2017-09-07 00:27:05 +00:00
|
|
|
please ensure that the PR title is in the following format:
|
2018-05-14 00:55:35 +00:00
|
|
|
|
2017-09-29 18:16:38 +00:00
|
|
|
```
|
|
|
|
|
[X.Y] <title from the original PR> (GH-NNNN)
|
|
|
|
|
```
|
2018-05-14 00:55:35 +00:00
|
|
|
|
2017-09-29 18:16:38 +00:00
|
|
|
Where: [X.Y] is the branch name, e.g. [3.6].
|
2017-09-07 00:27:05 +00:00
|
|
|
|
2021-05-03 22:36:55 +00:00
|
|
|
GH-NNNN refers to the PR number from `main`.
|
2017-09-07 00:27:05 +00:00
|
|
|
|
2018-02-23 23:48:21 +00:00
|
|
|
-->
|
