You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 529c4de
Browse filesBrowse the repository at this point in the historyBrowse files
* #22998 ruling (two-speed CI; ruling record 6120820653 on #22991): its leg
377
+
* runs in the FULL BATTERY only — `main`'s push, hourly and dispatch runs — so a
378
+
* PR or queue build carries the fast set and the context left the
379
379
* required set. The order is the #9325 two-step: the registry and the
380
-
* instruction surfaces drop the rows in the PR, and the maintainer removes the
381
-
* two contexts from the ruleset in the same sitting as the merge; until then
382
-
* `--verify-required-set` reports them in direction B (required, pinned by no
380
+
* instruction surfaces drop the row in the PR, and the maintainer removes the
381
+
* context from the ruleset in the same sitting as the merge; until then
382
+
* `--verify-required-set` reports it in direction B (required, pinned by no
383
383
* row), report-only, which is the sitting's own reminder. Prose and not a
384
384
* RETIRED_CONTEXT_NAMES row, for the reason the `Build Docs` / `Console Pin
385
-
* Gate` tombstone above gives: neither name is dead — both jobs still publish
386
-
* these check-runs on every full-battery run, and the instruction files name
387
-
* where each runs.
388
-
* Since #30461 (ruling record 6663883327, letter B) the three dogfood shards
389
-
* also run on `merge_group`, so a queue build publishes `Dogfood Regression
390
-
* Gate` over their credentials; `Temporal Conformance` stays full-battery
391
-
* only. The context stays out of this registry and of the ruleset for now: the
392
-
* follow-up ruling on #30461 (A, in two steps, 6669982756) puts it back only
393
-
* after a clean 24-hour reading of the queue builds, the row here landing
394
-
* first and the ruleset edit after it.
385
+
* Gate` tombstone above gives: the name is not dead — the job still publishes
386
+
* this check-run on every full-battery run, and the instruction files name
387
+
* where it runs.
388
+
* Returned: `Dogfood Regression Gate` (ci.yml:dogfood-gate) left with it by #22998 and is back since #30461 (letter B 6663883327 put its shards on `merge_group`; letter A 6669982756 re-enrolled the row below).
* of the six surfaces have one; `AGENTS.md` does not, because a repo-root FILE
684
693
* has no separator to be found by — so an AGENTS.md card derived this gate not
685
694
* at all, while that surface is the one carrying `mustName` for every
686
-
* required context (widened 2→6 by #9677, 6→7 by #17798, 7→5 by #22998, 5→7 by #25853, 7→8, 8→9 by #26460, 9→10 by #27154). Editing the merge-queue
695
+
* required context (widened 2→6 by #9677, 6→7 by #17798, 7→5 by #22998, 5→7 by #25853, 7→8, 8→9 by #26460, 9→10 by #27154, 10→11 by #30461). Editing the merge-queue
687
696
* paragraph there is precisely how this gate goes red, and it was reachable
688
697
* only by judgment.
689
698
*
@@ -2004,6 +2013,15 @@ async function selfTest() {
0 commit comments