Describe the bug
When merging a PR, the merge queue should:
- Process PRs one by one.
- For each PR, apply its diff on top of
main, ensure there are no merge conflicts, verify that all CI tests pass, and then merge it.
However, it seems possible for the merge queue to reject a PR even when all CI tests have passed. It would be helpful to understand why this happens.
The failure case:
To Reproduce
No response
Expected behavior
No response
Additional context
No response
Describe the bug
When merging a PR, the merge queue should:
main, ensure there are no merge conflicts, verify that all CI tests pass, and then merge it.However, it seems possible for the merge queue to reject a PR even when all CI tests have passed. It would be helpful to understand why this happens.
The failure case:
To Reproduce
No response
Expected behavior
No response
Additional context
No response