Skip to content

ci(secret-scan): rename caller job key secret-scan -> scan (D243) - #19

Merged
hyperpolymath merged 1 commit into
mainfrom
ci/secret-scan-floor-key
Oct 1, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
ci/secret-scan-floor-key

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

What

Rename the secret-scanner caller job key secret-scan → scan in .github/workflows/secret-scanner.yml, so the check context becomes scan / gitleaks — the context the estate Secret-Scan-Floor ruleset (D243/D244) requires. One-line change; reusable pin, triggers and permissions unchanged. actionlint output is identical before and after.

Commit created via GraphQL createCommitOnBranch (GitHub-signed, signature valid: true).

🤖 Generated with Claude Code

https://claude.ai/code/session_0136eszqrQ53Kj7aBH1D4rXK

Secret-Scan-Floor (D243/D244) requires the context `scan / gitleaks` estate-wide. The caller job key here was `secret-scan`, which emits `secret-scan / gitleaks` and can never satisfy the floor. Rename only; the reusable pin and permissions are unchanged.

actionlint output identical before and after.

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

coderabbitai Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

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: 4ff68420-ffb9-459c-a5a7-6721edf3bde7

📥 Commits

Reviewing files that changed from the base of the PR and between ef8b483 and ef0cc4e.

📒 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. (6)
  • GitHub Check: scan / gitleaks
  • GitHub Check: scan / rust-secrets
  • GitHub Check: scan / shell-secrets
  • GitHub Check: documentation
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: documentation
🔇 Additional comments (1)
.github/workflows/secret-scanner.yml (1)

21-21: LGTM!


📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the name used for an automated check. Its configuration and operation remain unchanged, with no changes to product functionality or the experience in the app. This maintenance update does not add, remove, or change any features available to users.

Walkthrough

The secret scanner workflow job key changed from secret-scan to scan. The reusable workflow reference and secrets: inherit setting remain unchanged.

Changes

Secret scanner workflow

Layer / File(s) Summary
Rename the workflow job key
.github/workflows/secret-scanner.yml
The job key changed from secret-scan to scan. The reusable workflow reference and inherited secrets setting did not change.

Priority: ⬇️ Low

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

Change: Bug fix

Merge Risk: ⚪ Minimal · up to ef0cc

The scanner check now uses the intended scan / gitleaks context, with no in-repository dependency on the old name found. No concrete merge-blocking issue is evidenced; the external branch-protection list could not be confirmed.

Architecture Summary

Architecture risk: 🔵 Low · up to ef0cc

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 job key changed from secret-scan to scan; the reusable workflow reference and secrets: inherit setting remain unchanged.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description check ✅ Passed The description clearly explains the job-key rename and its required check context. It directly matches the changeset and objectives.
Title check ✅ Passed The title clearly and concisely identifies the CI job-key rename from secret-scan to scan. It matches the main change.
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.
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


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

I’m a rabbit, swift and bright,
I watched the job name change tonight.
scan now hops into the queue,
The workflow stays the same through and through.
I nibble clover, pleased and neat.

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

@hyperpolymath
hyperpolymath merged commit 9cb70d8 into main Oct 1, 2026
9 checks passed
@hyperpolymath
hyperpolymath deleted the ci/secret-scan-floor-key branch October 1, 2026 12:35
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