Skip to content

merge queue: checking #12782 on main (65b5e32) - #12790

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/1a0c11cb98
Closed

merge queue: checking #12782 on main (65b5e32)#12790
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/1a0c11cb98

Conversation

@mergify

@mergify mergify Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

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

#12782 is queued for merge on branch main (65b5e32).

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

flagendijk89 and others added 2 commits September 11, 2026 12:04
Two things on the Merge Queue hub were built inline in the MDX, and
between them they were the last content file on the site reaching for
`--color-*` primitives directly.

The headline figures. The homepage and the hub carry the same three
numbers — 3-5×, 60-90%, 0 — and drew them differently: the homepage
through `.home-metrics-strip` in index.css with semantic tokens, the hub
through nested divs with inline styles, hardcoded padding, radius and
font sizes, numerals at weight 700 where the type scale's 1.5rem step is
500, and teal pulled from a primitive. Being inline it could not pick up
the dark-mode remap the way every other surface does, so the same claim
read as a different kind of object depending which page you came from.
Both pages now render <MetricStrip>, which owns the markup and the
styles the homepage already had; the superseded rules leave index.css.

The comparison marks. The yes/no marks in "Mergify vs GitHub Native
Merge Queue" were two `export const` arrow functions inside the MDX,
each with a hand-written inline <svg> and its color in a style
attribute, duplicating marks already in the site's icon set. <Verdict>
replaces them, drawing from astro-icon. Its color stays a product
primitive rather than a --theme-* token, because yes and no are a
semantic pair with no semantic token behind them and DESIGN.md allows a
primitive inside a component for that; what changes is that the content
file no longer carries one.

merge-queue.mdx loses about 90 lines of inline markup and styling, and
`src/content/docs/` is now free of `--color-*` entirely.

The tables are untouched. Glossary and the symptom/cause/help table are
genuinely tabular and read better as tables than as cards.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Change-Id: Ida30f19564a144a12561edd3215e324bd049e9d7
Claude-Session-Id: 18413631-aa75-4182-9e79-4c1ce31bb683
@mergify
mergify Bot deployed to Mergify Merge Protections September 11, 2026 13:29 Active
@mergify mergify Bot closed this Sep 11, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/1a0c11cb98 branch September 11, 2026 13:33
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