cilium / cilium/github-actions
Check that backport PRs have relevant PR references
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
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/*.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MLH bot's pull-request description and label checks in this github-actions repository, then review how its existing GitHub Actions tests are run. The work is done when a backport PR is accepted with either an upstream-prs section or a release-note/* label, and is flagged when neither is present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100