65a794af0a
Make it so that you need to explicitly use the "Closes" keyword when opening PRs (as per [this sprint retro comment](https://miro.com/app/board/uXjVKzhhfgE=/?moveToWidget=3458764594901560846&cot=14))
19 lines
910 B
Markdown
19 lines
910 B
Markdown
# What this PR does
|
|
|
|
## Which issue(s) this PR closes
|
|
|
|
Related to [issue link here]
|
|
|
|
<!--
|
|
*Note*: If you want the issue to be auto-closed once the PR is merged, change "Related to" to "Closes" in the line above.
|
|
If you have more than one GitHub issue that this PR closes, be sure to preface
|
|
each issue link with a [closing keyword](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue).
|
|
This ensures that the issue(s) are auto-closed once the PR has been merged.
|
|
-->
|
|
|
|
## Checklist
|
|
|
|
- [ ] Unit, integration, and e2e (if applicable) tests updated
|
|
- [ ] Documentation added (or `pr:no public docs` PR label added if not required)
|
|
- [ ] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will
|
|
show up in the autogenerated release notes.
|