f6b6bb053c
# What this PR does See internal conversation [here](https://raintank-corp.slack.com/archives/C04JCU51NF8/p1709734053681209?thread_ts=1709116950.477509&cid=C04JCU51NF8). tldr; - `MAINTAINERS.md` - outdated + `.github/CODEOWNERS` contains the same/automated up-to-date information (via references to GitHub teams rather than individual users in a `.md` file) - `GOVERNANCE.md` - outdated; for example, a lot of references to GitHub discussions, which we do not use in this repo + another list of outdated users ## Which issue(s) this PR closes N/A ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] 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.
18 lines
792 B
Markdown
18 lines
792 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.
|