Skip to content

merge queue: embarking main (5073dc5) and #11702 together#11703

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

merge queue: embarking main (5073dc5) and #11702 together#11703
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/5ac23a4a11

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Jun 2, 2026

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

Branch main (5073dc5) and #11702 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #11702.
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: 5073dc51f451da17f707b07cdab62a90db940ff9
previous_failed_batches: []
pull_requests:
  - number: 11702
    scopes: []
scopes: []
...

sileht and others added 2 commits June 2, 2026 10:23
…atching

The batch-grouping section listed priority, scopes, changed directories,
and queue time as the similarity ranking, then described stacks in a
separate paragraph that read as a fifth tier of that order. Readers
(jd on PR #11693) took it as "scope -> files -> stack" and expected
stack to come before files.

Reframe the stack rule to match the engine: in serial mode stack
co-location is a separate constraint outside the similarity ranking
(_add_pull_with_predecessors), not a ranking tier. Selected pull
requests drag their queued predecessors into the same batch regardless
of scope or directory overlap, so stack relationships take precedence
over scope and directory similarity, bounded only by batch_size.

Also repoint the stale parallel-scopes link to queue-modes#parallel-mode.

Fixes MRGFY-7466

Change-Id: I8a0172f86b0629e0086e51c038e0244339086447
@mergify mergify Bot deployed to Mergify Merge Protections June 2, 2026 09:21 Active
@mergify mergify Bot closed this Jun 2, 2026
@mergify mergify Bot deleted the mergify/merge-queue/5ac23a4a11 branch June 2, 2026 09:23
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