Skip to content

merge queue: embarking main (ffba393) and #11683 together#11688

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/5c70a23a25
Closed

merge queue: embarking main (ffba393) and #11683 together#11688
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/5c70a23a25

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Jun 1, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (ffba393) and #11683 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #11683.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: ffba393dcc45fa096418b1ca06cf49663773b2c2
previous_failed_batches: []
pull_requests:
  - number: 11683
    scopes: []
scopes: []
...

sileht and others added 2 commits May 29, 2026 17:16
Add the `isolated` merge_queue.mode to the Parallel Scopes page: every
batch runs as a fully independent car with no dependency on any other
batch, scopes are optional, and batches form by scope-aware similarity
when scopes are set or by priority + arrival order when they are not.
Cover the shared non-serial limitations (no fast-forward, no
skip_intermediate_results, no partition_rules).

Fixes MRGFY-7436

Change-Id: I8fe738f299d1626774ccb201d735b380ab801a3e
@mergify mergify Bot deployed to Mergify Merge Protections June 1, 2026 08:38 Active
@mergify mergify Bot closed this Jun 1, 2026
@mergify mergify Bot deleted the mergify/merge-queue/5c70a23a25 branch June 1, 2026 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant