When generating release notes for a backport PR, the release tool first checks for a stanza like the following, and in that case uses the parent PR to determine the release note categorization and release note:
```upstream-prs
40399
```
If this is omitted, then the release note tool categorizes the PR as "other", which puts it right at the end - even if the release note might be important to highlight to users.
We've hit a few cases recently where developers have posted bugfix PRs without properly categorizing them.
MLH bot could lint for this, to check that either there is an upstream-prs section in the PR description, OR a label is set with release-note/*.
When generating release notes for a backport PR, the release tool first checks for a stanza like the following, and in that case uses the parent PR to determine the release note categorization and release note:
If this is omitted, then the release note tool categorizes the PR as "other", which puts it right at the end - even if the release note might be important to highlight to users.
We've hit a few cases recently where developers have posted bugfix PRs without properly categorizing them.
MLH bot could lint for this, to check that either there is an
upstream-prssection in the PR description, OR a label is set withrelease-note/*.