From 5efc5a0d3f11346cc562bf870b57fcbaf6fbf167 Mon Sep 17 00:00:00 2001 From: Rowan Date: Mon, 7 Sep 2026 09:46:36 -0400 Subject: [PATCH] docs: CONTRIBUTING names certify.yml as the inline gates' home, nightly and on demand (#686) Since #669 certify.yml has no push trigger, and the dispatch target for the inline-budget gates is certify.yml, not ci.yml. The sentence said both the old things; ci.yml's own header was corrected in #659. Closes #686 Co-Authored-By: Claude Fable 5.1 --- docs/CONTRIBUTING.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index d4de99eba..ad84f530b 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -94,10 +94,11 @@ translation unit at a time, on a pinned `windows-2025` image, with a negative control that must go red on a GNU extension. Visual C++ is a hard requirement here, so what the compiler emits is compiled with cl before a change lands. -One gate is **not** in the pull request leg, and runs on push to main, -nightly, and on `gh workflow run ci.yml --ref `: the -**inline-budget gates**, which fire on compiler-version changes by design and -cost most of the wall clock. +One gate is **not** in the pull request leg: the **inline-budget gates**, +which fire on compiler-version changes by design and cost most of the wall +clock. They live in `certify.yml`, which runs nightly and on +`gh workflow run certify.yml --ref `, never on push (the owner's +per-commit rule: a job that runs on every commit finishes in two minutes). So a change to the C++ emitters wants a dispatch run on its branch before merging, not just a green pull request.