Repository navigation
ci(ci-gate): re-pin the cicd-suite gate to 09878f2 (emoji-safe status descriptions) - #54
hyperpolymath wants to merge 1 commit into
Conversation
… descriptions) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDiRggj6apeRQKPpAVR
|
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 21 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. |
|
|
Two checks failed on 78c6920:
The limit belongs to the GitHub App installation and resets on GitHub's hourly window. Several CI gates were polling across the estate at the same time, which probably used it up. I'll re-run the failed jobs once after the reset and nothing more. Generated by Claude Code |



Summary
Re-pins the CI gate reusable workflow from
d2140a5a789e4ebec52f1bab0074181012660c3bto09878f2a2c0a8907cc69fe48973ea604753ecab1(hyperpolymath/proven-cicd-and-workflows#144). The old pin postsCI/gate = failurefalsely when a workflow name contains an emoji, because GitHub rejects 4-byte UTF-8 in a status description. That false red was seen on #48. Between the two pins the tamper guard workflow changed by one line, andci-gate.ymlgained the emoji-safe description handling.09878f2is a commit on an UNMERGED suite branch (#144 is stacked on #139), asd2140a5was. A second re-pin therefore follows #139's squash merge.This PR touches gate files (
ci-gate.yml,ci-gate-tamper-guard-caller.yml), so the tamper guard may failguard / checkuntil an admin applies thegate-change-approvedlabel. Agents do not apply it.Changes
.github/workflows/ci-gate.yml(2uses:lines) and.github/workflows/ci-gate-tamper-guard-caller.yml(1 line): new SHA; the# cicd-suite ...trailing comments are kept..github/workflows/actions.lock: both workflow entries, the dependency key and itscommit: sha1-...record. owner_id, repo_id andrefare unchanged.tests/workflows/actions_lock_sha_refs_test.sh(case table row) andtests/workflows/squabble_gate_test.sh(SUITE_PIN): they assert the live pin.CHANGELOG.adoc: new entry. The older entry that mentionsd2140a5is history and is untouched.RSR Quality Checklist
Required
just fmtor equivalent): not run, no formatted source changedunsafeblocks without// SAFETY:comments (none added).envfiles includedAs Applicable
CHANGELOGor release notes updatedTesting
Run locally on this branch, all exit 0:
scripts/check-lock-sync.sh: in sync and transitively closed.tests/workflows/squabble_gate_test.sh: 144 passed, 0 failed.tests/workflows/actions_lock_sha_refs_test.sh: 27 PASS lines.tests/workflows/check_lock_sync_test.sh: 26 PASS lines.tests/workflows/ci_gate_test.shandtests/workflows/validate_workflows_test.sh: exit 0.What is NOT proven
CI/gateruns on this PR.09878f2will survive the squash merge of #139: it is not on a protected branch.actionlintandjust test && just qualitywere not run.gh actions-lockcannot lock cross-repository reusables), socheck-lock-sync.shis its only authority.Screenshots
N/A
Generated by Claude Code