# What this PR does - Automate our release note creation using `.github/release.yml` (see docs [here](https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#example-configurations)). - Add a GitHub Actions check for PRs to ensure that each PR contains one `release:` label (which dictates how it will show up in the release notes) In addition, created the required labels: <img width="701" alt="Screenshot 2024-03-04 at 13 25 45" src="https://github.com/grafana/oncall/assets/9406895/eab83658-dfe9-478e-90d1-7cd66d9fce5d"> Once these changes are adopted and merged to `main` we can also delete the `pr:no changelog` label. ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [ ] Documentation added (or `pr:no public docs` PR label added if not required) - [ ] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not required)
16 lines
783 B
Markdown
16 lines
783 B
Markdown
# What this PR does
|
|
|
|
## Which issue(s) this PR closes
|
|
|
|
Closes [issue link here]
|
|
|
|
*Note*: 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.
|