diff options
author | Bryan Quigley <code@bryanquigley.com> | 2021-06-15 23:50:31 -0700 |
---|---|---|
committer | Jake Hunsaker <jhunsake@redhat.com> | 2021-06-16 19:06:38 -0400 |
commit | 69a2d8e7e82d7c7dbf2b8e3c0f65ac1ed954faef (patch) | |
tree | 0024f93e89af0ca1cef2729b9ce4d42f3b0db441 /.github | |
parent | ea3d6ba1ee9d2d8b352f1d8d0964f52c1589c823 (diff) | |
download | sos-69a2d8e7e82d7c7dbf2b8e3c0f65ac1ed954faef.tar.gz |
[github] Merge Closes and Resolves lines
While using Github merging we don't need to track Resolves to
close PRs anymore. If existing (and not the PR currently on)
it still makes sense to use Resolves though.
Signed-off-by: Bryan Quigley <code@bryanquigley.com>
Diffstat (limited to '.github')
-rw-r--r-- | .github/PULL_REQUEST_TEMPLATE.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 256483ce..d3b39feb 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -5,5 +5,4 @@ Please place an 'X' inside each '[]' to confirm you adhere to our [Contributor G - [ ] Is the subject and message clear and concise? - [ ] Does the subject start with **[plugin_name]** if submitting a plugin patch or a **[section_name]** if part of the core sosreport code? - [ ] Does the commit contain a **Signed-off-by: First Lastname <email@example.com>**? -- [ ] If this commit closes an existing issue, is the line `Closes: #ISSUENUMBER` included in an independent line? -- [ ] If this commit resolves an existing pull request, is the line `Resolves: #PRNUMBER` included in an independent line? +- [ ] Are any related Issues or existing PRs [properly referenced](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) via a Closes (Issue) or Resolved (PR) line?
\ No newline at end of file |