cilium / cilium/github-actions
MLH sometimes does not set the "mergeability" status
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Over the past month or two, I have noticed that PRs can sometimes get stuck with the only failing check being the "Mergeability" check that MLH is responsible to set.
Typically the workaround from a developer perspective is to set a label like dont-merge/bad-bot, wait a few seconds for MLH to receive the event, then remove the label again, and wait to see that MLH receives an event and sets the mergeability check to pass.
It seems like some time recently, MLH has begun to miss some events or does not complete event handling by setting the status for this check. It's unclear to me which is the case.
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
No files, tests, or entry points are named. Start by reproducing the issue with the dont-merge/bad-bot label workflow and tracing whether MLH receives the event and sets the Mergeability check. Done means the missed-event or incomplete-handling case is identified and the check is reliably set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100