Skip to content

ci: drop secrets: inherit from the scanner; grant actions: read on the scorecard job - #14

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/drop-secrets-inherit
Oct 19, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
fix/drop-secrets-inherit

Conversation

@hyperpolymath

Copy link
Copy Markdown
Contributor

Summary

Two small workflow fixes, both checked against the callee at the pinned standards commit (75bd5994).

  1. secret-scanner.yml forwards every repository secret with secrets: inherit, but the reusable scanner declares no secrets and reads none (its gitleaks is a pinned local binary). The "REQUIRED" header described an older gitleaks action.
  2. scorecard.yml's job-level permissions: block replaces the workflow-level one, so it dropped actions: read, which the callee's job requests. GitHub refuses a called job that asks for more than its caller grants, so the scheduled Scorecard run would fail at startup with no jobs (same cause as choreographic-types #31).

Changes

  • .github/workflows/secret-scanner.yml: remove secrets: inherit; replace the stale comment with the reason it is absent.
  • .github/workflows/scorecard.yml: add actions: read to the job-level permissions:, with a comment saying why it repeats the workflow-level grant.

RSR Quality Checklist

Required

  • No secrets, credentials, or .env files included

As Applicable

  • scripts/check-lock-sync.sh passes; scripts/check-action-pinning.js passes (no uses: changed)

Testing

Both files parse and both lock scripts pass. The scorecard change can only be proven by a scheduled or manual Scorecard run; a branch run cannot exercise it.


Generated by Claude Code

…e scorecard job

The secret-scanner reusable (standards@75bd5994) declares no secrets and reads
none; its gitleaks is a pinned local binary. The 'secrets: inherit is REQUIRED'
header predates that and forwarded every repository secret for nothing.

The scorecard caller's job-level permissions block replaces the workflow-level
one, so it dropped actions: read, which the callee's job requests; GitHub
refuses a called job that asks for more than its caller grants. Repeat
actions: read in the job block.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MF5GeeBBDF6sUzr6pZTjWV
@coderabbitai

coderabbitai Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: c1197369-b2cb-4c20-8665-8ff57e5072b7
📥 Commits

Reviewing files that changed from the base of the PR and between 86c5369 and e3dd9af.

📒 Files selected for processing: 2
  • .github/workflows/scorecard.yml
  • .github/workflows/secret-scanner.yml
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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
hyperpolymath marked this pull request as ready for review October 19, 2026 22:39
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-10-19T22:39:26.937926Z e3dd9af Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@hyperpolymath
hyperpolymath merged commit 54201e5 into main Oct 19, 2026
39 of 40 checks passed
@hyperpolymath
hyperpolymath deleted the fix/drop-secrets-inherit branch October 19, 2026 22:40
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.

2 participants