cilium / cilium/github-actions
Remove `ready-to-merge` label when commits are pushed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
We may want to consider whether to remove the ready-to-merge label when new commits are pushed into a branch. It's hard to tell whether there have been substantial changes in the commits since the tests were run and reviews were submitted the first time, so at the very least MLH could remove the ready-to-merge label until someone runs CI again.
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
The issue names no file, test, or entry point. Start by locating the GitHub Actions logic that applies or removes the ready-to-merge label when commits are pushed, then determine how CI status is detected; done means the label is removed after a new commit until CI runs again, with coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100