@@ -122,9 +122,8 @@ concurrency:
122122# github.event_name != 'pull_request'
123123#
124124# in its `if:`, so a dogfood red shows on the queue build of the entry that
125- # carries it rather than first on `main`'s push run after it. It is advisory
126- # there: the context is outside the required set (below), so the queue may
127- # merge the entry before or despite the shards.
125+ # carries it rather than first on `main`'s push run after it, and the red
126+ # ejects that entry: the context is in the required set again (below).
128127# `main`'s 4-hourly `schedule` run, its `push` runs and an on-demand
129128# `workflow_dispatch` carry the FULL BATTERY: all of that plus the three jobs
130129# below that spell
@@ -139,9 +138,9 @@ concurrency:
139138# `scripts/ci/scheduled-full-run.mjs --release-gate`). ⛔ No affected-only
140139# dogfood filter on the queue: the shards run on every entry, through the
141140# `core` output, which is 'true' on `merge_group` (letter C was not ruled).
142- # The queue enforces only the ruleset's required set, and `Dogfood Regression
143- # Gate` is outside it since #22998 (check:required-contexts' tombstone); this
144- # file does not decide whether it rejoins .
141+ # The queue enforces only the ruleset's required set. `Dogfood Regression
142+ # Gate` left it by #22998 and rejoined it by the #30461 follow-up ruling
143+ # (ruling record 6669982756); check:required-contexts pins its row .
145144#
146145# Spelled as a DENY-list of the per-PR events on purpose — the filter
147146# contract's half 1 below, applied to events: a trigger added to `on:` later
@@ -2724,8 +2723,8 @@ jobs:
27242723 overwrite : true
27252724
27262725 dogfood-gate :
2727- # Stable check name for a SHARDED job (#3622 follow-up). Since #22998 the
2728- # context is outside the required set (THE TWO SPEEDS above `jobs:`). On a
2726+ # Stable check name for a SHARDED job (#3622 follow-up). A required context
2727+ # again since #30461 (THE TWO SPEEDS above `jobs:`). On a
27292728 # PR both legs skip and this gate counts zero expected attestations; on a
27302729 # queue build (since #30461) the three dogfood shards run and are counted,
27312730 # while `dogfood-verify` skips and is judged with zero expected; the full
@@ -2738,10 +2737,9 @@ jobs:
27382737 # EVERY pull request in the repo sat permanently BLOCKED (mergeable, all
27392738 # checks green, merge button dead). #3622's own comment called for updating
27402739 # branch protection; keeping the contract HERE instead means a future
2741- # shard-count change cannot deadlock the repo a second time. From #6865
2742- # until #22998 the bare name was pinned by `check:required-contexts`; it
2743- # left that registry with the required set, so a rename now falsifies the
2744- # prose that names it without reddening anything — treat it as contract.
2740+ # shard-count change cannot deadlock the repo a second time. The bare name
2741+ # is pinned by `check:required-contexts` (since #6865; out of that registry
2742+ # from #22998 until #30461) — treat it as contract.
27452743 #
27462744 # Also aggregates dogfood-verify (the CLI pass that used to ride shard 1),
27472745 # so the one context still covers everything it covered before the split.
0 commit comments