ci: add a static-named Verify gate job for the required check - #549
Conversation
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
commit: |
…ue readiness audit (#557) The Verify matrix comment in ci.yml still named "Verify (Node 24)" as the required check on main; #549 replaced it with the static "Verify gate" job. Audit of every required-check workflow for merge_group readiness (#536) found no other gap; findings and the settings commands live in the PR body.
Summary
Adds a
verify-gatejob ("Verify gate") toci.ymlthat always runs after the Verify matrix and passes when every leg passed or the matrix was skipped, fails when a leg failed or was cancelled.Why: the new
mainbranch protection (#536) requiresVerify (Node 24). On docs-only PRs the Verify matrix job is skipped, and GitHub reports a skipped matrix job under its unexpanded name —Verify (Node ${{ matrix.node-version }})— so the required context never appears and the PR is blocked indefinitely (observed on #548). A static-named gate job is the standard fix; once this lands, the protection's required context switches fromVerify (Node 24)toVerify gate.CI-only:
skip-changeset. Validated withactionlint.