Repository navigation
ci(ci-gate): pull_request start and tamper guard (stacked on the CI/gate PR) - #49
hyperpolymath wants to merge 13 commits into
Conversation
Thin caller of the reusable ci-gate workflow in proven-cicd-and-workflows. It runs from the default branch via workflow_run (completed and in_progress, so a rerun flips the status to pending) and posts the commit status CI/gate, which the Branch-Floor ruleset requires. The required-check list lives in the suite profile at the pinned SHA, not in this repository. The caller is onboarded in actions.lock (workflow key plus a leaf dependency record, ref main) as the lock-sync gate requires. The pin is the placeholder __CICD_SUITE_SHA__ until the suite SHA is known. Rename the in-workflow job CI/gate to "Proofs verdict" (CI/gate now belongs to the suite publisher). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDg8YzLVHtwwDfcY3J9
Supersedes 7a5713b: profile schema v2 (typed workflow and job entries) and the settled rule extended to superseded runs. Updates the ci-gate.yml pin, the actions.lock workflow key, dependency key and commit, and any test row or text naming the old SHA. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDg8YzLVHtwwDfcY3J9
The suite reusable now re-fetches before every status write, so per-SHA serialisation only delayed the in_progress pending status. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDg8YzLVHtwwDfcY3J9
Replaces the 1d657fe pin in the ci-gate.yml caller, the actions.lock workflow key, dependency key and commit, and resource-algebra's lock case-table row. The suite profile for this repository is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDg8YzLVHtwwDfcY3J9
Replaces the c77a66d pin in the ci-gate.yml caller, the actions.lock workflow key, dependency key and commit, and resource-algebra's lock case-table row. The suite profile for this repository is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDg8YzLVHtwwDfcY3J9
Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
…e checker The CI gate caller gains a 15-minute schedule and workflow_dispatch, which bounds (does not eliminate) a stale CI/gate status. It needs pull-requests: read to list open PRs. scripts/check-required-contexts.sh learns `<context> => status:<workflow>`: the publisher must exist, trigger on workflow_run with a completed type, call the suite ci-gate reusable at a 40-hex pin (or the local copy) and pass with.context equal to the context. A plain mapping keeps its semantics. Positive and negative tests are in tests/workflows/squabble_gate_test.sh. The CI/gate job-name negative in tests/workflows/ci_gate_test.sh now reads parsed job names with yq v4, so plain, double-quoted and single-quoted spellings all count, with planted controls for each. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDg8YzLVHtwwDfcY3J9
Map CI/gate => status:.github/workflows/ci-gate.yml in the required-contexts allow-file so the checker verifies the publisher here, not only where a repo-local ruleset JSON lists the context. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDg8YzLVHtwwDfcY3J9
…YAML The typed `status:` mapping spawned mikefarah yq once per mapping. That doubled the checker's run time and failed the Six-Sigma benchmark regression gate on resource-algebra#43 (required_contexts at 2.025x against a 2.0x limit). The checker already parses pull_request producers with Bun.YAML.parse, so the status path now does the same, with the same `on` -> `true` YAML 1.1 fallback, and yq is no longer needed. Median of 15 runs on resource-algebra: 25 ms with the yq spawn, 12 ms now, and 12 ms for the checker on main. The checker passes on the repo itself, and squabble_gate_test.sh passes with unchanged counts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDg8YzLVHtwwDfcY3J9
…rename The CHANGELOG entry for this PR was lost when main was merged into the branch, and the branch's CHANGELOG.adoc was identical to main's. Restore it: the suite publisher of CI/gate (with its sweep and its stated last-writer-wins limit), the rename of the in-workflow job to `Proofs verdict`, and the typed `status:` mapping in the required-contexts checker. Documentation only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDg8YzLVHtwwDfcY3J9
…mmit that has both actions.lock NOT regenerated: no lock-sync-fix tool in this repo and gh actions-lock is not installed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDj7XpKyxE4WbsgTsTh
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 54 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
… fix Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDj7XpKyxE4WbsgTsTh
|
|
Superseded by hyperpolymath/proven-cicd-and-workflows#139, which merged as 4e9e680 and carries this work. Closing on the owner's instruction (17 Nov: close the superseded gate PRs after #139 lands). The branch is left in place. 🤖 Generated with Claude Code Generated by Claude Code |



What
Stacked on #43 (this branch descends from that PR's head, so its content is included). It adds, on top:
pull_requestworkflow as well asworkflow_run; the head SHA comes from whichever fired, any other event is refused. A pull_request run evaluates once, so it polls (bounded,wait_minutesdefault 30) while the verdict only means "not finished" (pending, never reported, never completed) and then gives the unchanged verdict; on timeout it fails naming what is missing. Same-repo branches only; fork and Dependabot PRs stay on theworkflow_runjob. No trust decision usesgithub.actor(Sonar S8232).pull_request_targetworkflow (runs from the default branch, never checks out or runs PR code,pull-requests: read+contents: read, no secrets) fails a PR that touches gate files unless the owner applied the labelgate-change-approvedafter the newest commit. Agents must never apply that label.Limits, stated plainly
never reportedon its own introduction). List{job: "guard / check", workflow: ".github/workflows/ci-gate-tamper-guard.yml"}once it is on main and one later PR shows its run underactions/runs?head_sha=<head>. Whether a pull_request_target run's head_sha is the PR head is unverified.gh actions-lockis not installed.What the owner must do once per repo
gate-change-approvedto any PR that touches gate files, after its newest commit, once you have read the change.guard / checkappears on a later PR, then add the profile entry above.Newly adopting repo: add its profile to the suite, copy
templates/ci-gate-caller.ymlandtemplates/ci-gate-tamper-guard-caller.ymlwith the suite SHA, and open that PR from a same-repo branch.Branches here are NEW (the existing PR branches have auto-merge on with merge method squash, while the suite PR asks for a merge commit; pushing to them could have merged them unseen). If you want these commits on the existing branches, they are fast-forwards of them.
Generated by Claude Code