If a self mutation happens in a merge queue, the failure is confusing and the next step is unclear
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 215
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 27
Description
Example https://github.com/winglang/wing/pull/3966
This PR failure was because main was merged into the branch, which caused a snapshot change. The self mutation was applied to the merge queue, but this is a waste of time because mergify already throws away this PR.
The next action depends on the exact circumstance, but generally will require the same update and mutation to be applied to the original PR. At the very least there should be some messaging to clarify that the mergify queue failed for this reason and some possible next steps.
Contributor guide
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 reviewing PR 3966 and the merge-queue/self-mutation workflow that produced its failure. Confirm the behavior when merging main causes a snapshot change; done means the failure identifies this cause and gives applicable next steps for updating and rerunning the original PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100