Skip to content

fix(ci): restore reachable standards workflow pins - #85

Closed
hyperpolymath wants to merge 1 commit into
mainfrom
fix/restore-reachable-standards-pin
Closed

hyperpolymath wants to merge 1 commit into
mainfrom
fix/restore-reachable-standards-pin

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Replace the unreachable standards reusable-workflow commit 7fdc2705df74b4e352d2a1cde3e87a5923fdf329 with reachable standards main commit 092dedada188f56c5915f74a5fd40aac093742c3. The old SHA is an intermediate commit from squash-merged standards PR #596: it exists, but GitHub rejects it for cross-repository reusable workflows before creating jobs. This restores Hypatia/SARIF and the other affected workflows without weakening SHA pinning or branch protection. Estate incident: 251 active workflow files across 70 repositories in hyperpolymath and metadatastician.

@coderabbitai

coderabbitai Bot commented Sep 4, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: 1b5dbff3-5314-4317-9ccf-461e67e1ee2c

📥 Commits

Reviewing files that changed from the base of the PR and between 515ee45 and 4266a26.

📒 Files selected for processing (5)
  • .github/workflows/governance.yml
  • .github/workflows/hypatia-scan.yml
  • .github/workflows/mirror.yml
  • .github/workflows/scorecard.yml
  • .github/workflows/secret-scanner.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (13)
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: Validate A2ML manifests
  • GitHub Check: Groove manifest check
  • GitHub Check: Validate K9 contracts
  • GitHub Check: scan / gitleaks
  • GitHub Check: scan / rust-secrets
  • GitHub Check: scan / shell-secrets
  • GitHub Check: trufflehog
  • GitHub Check: Test (Elixir 1.16 / OTP 26)
  • GitHub Check: analyze (actions, none)
  • GitHub Check: Test (Elixir 1.15 / OTP 26)
  • GitHub Check: Test (Elixir 1.17 / OTP 26)
  • GitHub Check: Dialyzer
🔇 Additional comments (5)
.github/workflows/governance.yml (1)

16-16: LGTM!

.github/workflows/hypatia-scan.yml (1)

19-19: LGTM!

.github/workflows/mirror.yml (1)

11-11: LGTM!

.github/workflows/scorecard.yml (1)

16-16: LGTM!

.github/workflows/secret-scanner.yml (1)

16-16: LGTM!


📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the project’s automated governance, security scanning, scorecard, secret-scanning and mirroring workflows.
    • These workflows now use refreshed, securely pinned workflow revisions, maintaining consistent automated checks and repository synchronisation.

Walkthrough

Five GitHub Actions workflows now pin their reusable workflow references to commit 092dedada188f56c5915f74a5fd40aac093742c3.

Changes

Reusable workflow pin updates

Layer / File(s) Summary
Update reusable workflow pins
.github/workflows/governance.yml, .github/workflows/hypatia-scan.yml, .github/workflows/mirror.yml, .github/workflows/scorecard.yml, .github/workflows/secret-scanner.yml
The workflows now reference the new pinned commit SHA. No job definitions or permissions changed.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to 4266a

This restores the five reusable CI workflow pins to the intended reachable revision while retaining immutable SHA pinning. No current merge-blocking risk remains.

Poem

A rabbit checks each workflow line
Five pins now point to one design
Governance hops, scans follow too
Mirror and scorecard join the queue
Secret scanner rests secure
The YAML trail is neat and pure

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the CI change: restoring reachable reusable workflow pins. It is concise and directly matches the changeset.
Description check ✅ Passed The description accurately explains the replacement of the unreachable workflow commit and the effect on affected workflows. It is directly related to the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@hyperpolymath

Copy link
Copy Markdown
Owner Author

Superseded by #88, which moves all five standards reusable pins to standards main HEAD (fad242d3) and pins the secret scanner's checkout@v7 to a sha. Closing so the two branches do not collide.

hyperpolymath added a commit that referenced this pull request Sep 8, 2026
…ut (#88)

Moves all five `hyperpolymath/standards` reusable-workflow pins
(governance, hypatia-scan, mirror, scorecard, secret-scanner) from
`7fdc2705`, which is not on standards `main`, to
`fad242d35291de1898242d6737ba02b74a59a2f2`, the current standards `main`
HEAD. Pins `actions/checkout@v7` in `secret-scanner.yml` to the `v7.0.1`
sha already used by the other workflows, because `sha_pinning_required`
rejects bare major tags at startup.

**Root cause of the startup failures (second commit).** The pin bump
alone still failed at startup for Governance and Hypatia, exactly as #86
did. At standards HEAD the governance, hypatia-scan and mirror reusables
request `actions: read` at workflow level (hypatia since 2026-06-02,
governance and mirror since 2026-07-26). A called workflow cannot
request more than its caller grants, and this repo's callers granted
only `contents: read`, so GitHub rejected each call before any job ran
and reported no check. The secret-scanner reusable requests only
`contents: read`, which is why it started and its three inner jobs went
green under the same pin. The second commit grants `actions: read` on
the three callers and adds `secrets: inherit` on governance, matching
standards' own caller.

Supersedes #85 (moves to the non-HEAD sha `092dedad`, which still
carries the trufflehog repeated-`fail`-flag bug) and #86 (governance
only).

Remaining red after this: the repo's own `trufflehog` job in
`secret-scanner.yml` (`flag 'fail' cannot be repeated`) is a separate
defect in the caller-side step, not the reusable, and is left for its
own PR.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@hyperpolymath
hyperpolymath deleted the fix/restore-reachable-standards-pin branch September 18, 2026 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant