From e2197d4bc4e5bb1a9b49591732dd8a0d78e44144 Mon Sep 17 00:00:00 2001 From: Eitan Adler Date: Sun, 13 May 2018 23:29:43 +0000 Subject: [PATCH] bpo-33488: Satisfy markdownlint for pull request ./.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 --- .github/PULL_REQUEST_TEMPLATE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 917791eb287f99c..2731c0e8e5503b0 100644 --- 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] (GH-NNNN) ``` + Where: [X.Y] is the branch name, e.g. [3.6]. GH-NNNN refers to the PR number from `master`.