-
Notifications
You must be signed in to change notification settings - Fork 39
Closed
Labels
t:bugSomething isn't workingSomething isn't working
Description
Contact Details
No response
Current Behavior
A PR, which will break CI, could be merged with GitHub merge queue.
For example:
Expected Behavior
From the official GitHub Docs, we can find the follow description:
The merge queue provides the same benefits as the Require branches to be up to date before merging branch protection,
With the correct use of GitHub merge queue, we should have "the same benefits" as "to be up to date".
Otherwise, why we don't just click the "merge" button to merge PR directly?
OS
Not Associated
Axon version
No response
Kernel
Not Associated
Relevant log output
No response
Anything else?
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
t:bugSomething isn't workingSomething isn't working