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

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 917791eb287f99cd8de0c72a8120514787f95948..2731c0e8e5503b034efbc9991f9de6decc398c66 100644 (file)
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -5,9 +5,11 @@ Please read this comment in its entirety. It's quite important.
 # Pull Request title
 
 It should be in the following format:
+
 ```
 bpo-NNNN: Summary of the changes made
 ```
+
 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.
@@ -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`),
 please ensure that the PR title is in the following format:
+
 ```
 [X.Y] <title from the original PR> (GH-NNNN)
 ```
+
 Where: [X.Y] is the branch name, e.g. [3.6].
 
 GH-NNNN refers to the PR number from `master`.