Skip to content

merge queue: embarking main (8b6fc95), #11697 and #11693 together#11700

Closed
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/edac156669
Closed

merge queue: embarking main (8b6fc95), #11697 and #11693 together#11700
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/edac156669

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 (8b6fc95), #11697 and #11693 are embarked together for merge.

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

jd and others added 4 commits June 1, 2026 17:36
GraphViz diagrams are rendered to static SVG at build time, so a
graph-level `label` (e.g. "Merge Queue" on the batches page) becomes a
`<text>` element with no `fill` attribute and defaults to black. That is
fine on the light page background but invisible in dark mode.

Add a CSS rule that colors the graph-level label with `--theme-text` so
it adapts to the active theme. The `svg.graph > g.graph > text` selector
targets only the top-level caption — node labels (`g.node > text`) and
cluster labels (`g.cluster > text`, which carry their own colors on
filled backgrounds) are unaffected. This also fixes the same latent
issue on other diagrams with top-level captions (scopes, parallel
scopes, monorepo CI, performance, etc.).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Change-Id: I861269fc345aff13be984af43b88ab3f37571a89
The heuristic that groups pull requests into batches in serial mode was
changed in #32298 (group by changed-directory similarity when no scopes
source is configured) and was undocumented.

Document, in the Batches page, how Mergify decides which pull requests
share a batch: priority and queue order come first, then similarity
fills the batch (scopes when configured, otherwise the directories each
PR changes), and stacks are kept together. Replace the vague,
out-of-place note in the failure-handling section with this accurate
description.

Fixes MRGFY-7456

Change-Id: Ia6adeea393375646d6c530dc85e560339e81a9a3
@mergify mergify Bot deployed to Mergify Merge Protections June 2, 2026 07:30 Active
@mergify mergify Bot closed this Jun 2, 2026
@mergify mergify Bot deleted the mergify/merge-queue/edac156669 branch June 2, 2026 07:31
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.

2 participants