cilium / cilium/github-actions
`ready-to-merge` label is incorrectly applied even though `needs-rebase` has been set
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
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
Review the GitHub Actions logic in this repository, then use the screenshot and referenced cilium/cilium pull request 11328 to understand the label transition. Reproduce the case where needs-rebase is set and verify that ready-to-merge is not applied; the issue is done when that conflicting label state is handled correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100