Skip to content

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

Merged
hyperpolymath merged 2 commits into
mainfrom
fix/restore-reachable-standards-pin
Sep 8, 2026
Merged

hyperpolymath merged 2 commits 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: Advanced

Run ID: 14bcdb0b-1eaf-47e3-b209-964be056e002

📥 Commits

Reviewing files that changed from the base of the PR and between 3f93111 and 012e27d.

📒 Files selected for processing (2)
  • .github/workflows/mirror.yml
  • .github/workflows/scorecard.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. (1)
  • GitHub Check: Burrower proof safety
🔇 Additional comments (3)
.github/workflows/mirror.yml (2)

2-2: LGTM!


13-13: 🗄️ Data Integrity & Integration

No change required. fad242d35291de1898242d6737ba02b74a59a2f2 is four commits ahead of 092dedada188f56c5915f74a5fd40aac093742c3 and contains both reusable workflow files.

.github/workflows/scorecard.yml (1)

2-2: LGTM!


📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the pinned versions of the reusable mirroring and security scoring workflows.
    • Workflow permissions, job structure, and behaviour remain unchanged.

Walkthrough

The pull request updates the pinned commit for the reusable mirror and Scorecard workflows. No workflow structure, permissions, or job behaviour changed.

Changes

Workflow pin updates

Layer / File(s) Summary
Update reusable workflow references
.github/workflows/mirror.yml, .github/workflows/scorecard.yml
The mirror and Scorecard jobs now reference commit fad242d35291de1898242d6737ba02b74a59a2f2 of the standards repository.

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

Merge Risk: 🟡 Moderate · up to 012e2

The mirror and Scorecard workflows now use a new pinned standards commit, but the selected pin differs from the stated remediation target. If it is not reachable or lacks the intended reusable workflows, CI and security reporting workflows may remain unable to start.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description explains the purpose and incident context, but it does not follow the required template. It omits the Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections. It als… Rewrite the description using all required template sections. List the workflow changes, record testing results, complete the applicable checklist items, and state whether screenshots or terminal output apply. Resolve the discrepancy betwee…
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the primary change: restoring reachable, pinned standards workflow references.
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.
Full details: Description check

Explanation

The description explains the purpose and incident context, but it does not follow the required template. It omits the Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections. It also references SHA 092dedada188f56c5915f74a5fd40aac093742c3, while the file summary reports SHA fad242d35291de1898242d6737ba02b74a59a2f2.

Resolution

Rewrite the description using all required template sections. List the workflow changes, record testing results, complete the applicable checklist items, and state whether screenshots or terminal output apply. Resolve the discrepancy between the SHA in the description and the SHA reported in the file changes before merging.

  • Fix all pre-merge checks with AI

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

A rabbit checks each workflow pin,
Two paths use newer code.
The mirror hops, Scorecard grins,
No job structure bears a load.
One commit keeps the burrow bright.

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

coderabbitai[bot]
coderabbitai Bot previously approved these changes Sep 4, 2026
…s main HEAD

The previous target 092dedad is 4 commits behind standards main and would
reintroduce bugs fixed there; main had meanwhile moved scorecard to 571cc734
(39 behind). Both callers now pin fad242d35291 (standards main HEAD,
2026-09-07). mirror.yml already grants actions: read, which mirror-reusable
at HEAD requests; scorecard-reusable at HEAD requests no new permission.
@hyperpolymath
hyperpolymath merged commit c7604bf into main Sep 8, 2026
51 checks passed
@hyperpolymath
hyperpolymath deleted the fix/restore-reachable-standards-pin branch September 8, 2026 04:09
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