bpo-33488: Satisfy markdownlint for the pull request template. (GH-6786)

./.github/PULL_REQUEST_TEMPLATE.md:8: MD031 Fenced code blocks should be
surrounded by blank lines
./.github/PULL_REQUEST_TEMPLATE.md:10: MD031 Fenced code blocks should
be surrounded by blank lines
./.github/PULL_REQUEST_TEMPLATE.md:19: MD031 Fenced code blocks should
be surrounded by blank lines
./.github/PULL_REQUEST_TEMPLATE.md:21: MD031 Fenced code blocks should
be surrounded by blank lines
This commit is contained in:
Eitan Adler 2018-05-13 17:55:35 -07:00 committed by Benjamin Peterson
parent 898ff92dac
commit 5cd22cf209
1 changed files with 4 additions and 0 deletions

View File

@ -5,9 +5,11 @@ Please read this comment in its entirety. It's quite important.
# Pull Request title # Pull Request title
It should be in the following format: It should be in the following format:
``` ```
bpo-NNNN: Summary of the changes made bpo-NNNN: Summary of the changes made
``` ```
Where: bpo-NNNN refers to the issue number in the https://bugs.python.org. 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. Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.
@ -16,9 +18,11 @@ Most PRs will require an issue number. Trivial changes, like fixing a typo, do n
If this is a backport PR (PR made against branches other than `master`), If this is a backport PR (PR made against branches other than `master`),
please ensure that the PR title is in the following format: please ensure that the PR title is in the following format:
``` ```
[X.Y] <title from the original PR> (GH-NNNN) [X.Y] <title from the original PR> (GH-NNNN)
``` ```
Where: [X.Y] is the branch name, e.g. [3.6]. Where: [X.Y] is the branch name, e.g. [3.6].
GH-NNNN refers to the PR number from `master`. GH-NNNN refers to the PR number from `master`.