Skip to content

ci: drop secrets: inherit from the secret scanner - #43

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

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

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

secret-scanner.yml forwards every repository secret to the reusable scanner with secrets: inherit. The reusable (standards@75bd5994) declares no workflow_call secrets and reads none: its gitleaks is a pinned local binary, and the GITHUB_TOKEN its jobs run under is governed by permissions:. The header claiming inherit was REQUIRED described an older gitleaks action that is gone. Raised by CodeRabbit on #42 (already merged) and verified against the callee.

Changes

  • .github/workflows/secret-scanner.yml: remove secrets: inherit and replace the stale "REQUIRED" comment with the reason it is absent. Nothing else changes; the uses: pin and actions.lock are untouched.

Testing

The file parses and check-lock-sync.sh passes. The real test is the scan jobs still passing on this PR; choreographic-types already runs the same scanner with no secrets: line.


Generated by Claude Code

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.

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
Contributor

Review in 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: 3da264cf-ad46-425c-8972-da73e857d161
📥 Commits

Reviewing files that changed from the base of the PR and between f341cd6 and e0bdd60.

📒 Files selected for processing: 1
  • .github/workflows/secret-scanner.yml

Included review availability: This review used your included allowance. 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: 27
  • GitHub Check: governance / JS runtimes — deno
  • GitHub Check: governance / JS runtimes — pnpm
  • GitHub Check: governance / Live Actions policy (credentialed advisory)
  • GitHub Check: governance / Allowlist Preflight
  • GitHub Check: governance / JS runtimes — environment provisions Bun first
  • GitHub Check: governance / JS runtimes — bun
  • GitHub Check: governance / Actions lockfile verify
  • GitHub Check: governance / Security policy checks
  • GitHub Check: governance / Exemption ratchet
  • GitHub Check: governance / Debt ratchet
  • GitHub Check: governance / Language / package anti-pattern policy
  • GitHub Check: governance / Licence consistency
  • GitHub Check: scan / shell-secrets
  • GitHub Check: governance / Guix packaging policy (Nix retired)
  • GitHub Check: scan / gitleaks
  • GitHub Check: governance / UUID v7 conformance
  • GitHub Check: governance / UUID v8 conformance
  • GitHub Check: governance / Trusted-base reduction policy
  • GitHub Check: governance / Check Workflow Staleness
  • GitHub Check: governance / Workflow security linter
  • GitHub Check: governance / Code quality + docs
  • GitHub Check: governance / Well-Known (RFC 9116 + RSR)
  • GitHub Check: scan / rust-secrets
  • GitHub Check: Canonical Echo correspondence
  • GitHub Check: analyze (actions, none)
  • GitHub Check: Proof core and rejection controls
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments: 1
.github/workflows/secret-scanner.yml: 1

6-9: LGTM!

Also applies to: 23-23

📝 Summary

Summary by CodeRabbit

  • Security
    • The secret-scanning workflow no longer forwards repository secrets to the reusable scanner.

The secret scanner workflow comments now describe secret handling and GITHUB_TOKEN permissions. The reusable workflow call no longer forwards repository secrets.

Changes: Secret scanner workflow

Layer / File(s) Summary
Document and remove secret forwarding
.github/workflows/secret-scanner.yml
The comments state that the reusable workflow reads no secrets and that GITHUB_TOKEN is controlled by permissions:. The call no longer uses secrets: inherit.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to e0bdd

The scanner no longer receives unnecessary repository secrets, while its scan behavior and required token permissions remain intact. No actionable merge-blocking risk is established.

### Architecture Summary

Architecture risk: 🔵 Low · up to e0bdd

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

  • observed — Modified behavior in .github/workflows/secret-scanner.yml: The comments now state that the reusable workflow reads no secrets and that its GITHUB_TOKEN is controlled by permissions:; they replace the claim that secrets: inherit is required to prevent a degraded scan.
  • observed — Modified behavior in .github/workflows/secret-scanner.yml: The secrets: inherit setting was removed from the reusable workflow call, so it no longer forwards repository secrets.
Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly identifies the main change: removing secrets: inherit from the secret scanner workflow.
Description check Passed The description directly explains the removal of secrets: inherit, the updated comment, the scanner configuration, and the reported checks.
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: Docstring Coverage

Explanation

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 files. (1 skipped: 1 unsupported.)

  • 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:30.315392Z e0bdd60 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 enabled auto-merge (squash) October 19, 2026 22:41
@hyperpolymath
hyperpolymath enabled auto-merge (squash) October 20, 2026 13:14
@hyperpolymath
hyperpolymath merged commit d342333 into main Oct 20, 2026
31 checks passed
@hyperpolymath
hyperpolymath deleted the fix/drop-secrets-inherit branch October 20, 2026 13:31
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