Skip to content

ci(secret-scan): rename caller job key secret-scan -> scan (D291) - #71

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

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

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Canonical estate caller key (D243/D291): the job key becomes scan, so the contexts become scan / gitleaks, scan / rust-secrets and scan / shell-secrets. Rename only; the reusable pin, triggers and permissions are unchanged. The ruleset context naming secret-scan / … is updated in step with this change.

Claude-Session: https://claude.ai/code/session_0136eszqrQ53Kj7aBH1D4rXK

Summary

Closes #

Type of change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (would change existing behaviour)
  • 🕳️ Soundness fix (fixes a checker/proof false-negative)
  • 📖 Documentation
  • 🧹 Refactor / tech debt (behaviour-preserving)
  • ⚡ Performance
  • 🔧 Build / CI / tooling

How has this been verified?

Checklist

  • My commits are signed (git commit -S).
  • I ran the project's own checks/tests locally and they pass.
  • New files carry the correct SPDX-License-Identifier (code/config MPL-2.0,
    prose CC-BY-SA-4.0); I did not relicense existing files.
  • Docs are updated, and no public claim now overstates what the code does.
  • I have not introduced a soundness hole (or I have flagged where I might have).

Notes for reviewers

Canonical estate caller key (D243/D291): the job key becomes `scan`, so the contexts become `scan / gitleaks`, `scan / rust-secrets` and `scan / shell-secrets`. Rename only; the reusable pin, triggers and permissions are unchanged. The ruleset context naming `secret-scan / …` is updated in step with this change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136eszqrQ53Kj7aBH1D4rXK
@hyperpolymath
hyperpolymath merged commit 3e69929 into main Oct 3, 2026
15 checks passed
@hyperpolymath
hyperpolymath deleted the ci/secret-scan-key-scan branch October 3, 2026 10:40
@coderabbitai

coderabbitai Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Review in Change Stack →

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

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: 01659807-0c07-4483-be3d-e38a41139807
📥 Commits

Reviewing files that changed from the base of the PR and between dfb5f2e and ef71559.

📒 Files selected for processing (1)
  • .github/workflows/secret-scanner.yml
 ________________________________
< RabbitCop: To debug and serve. >
 --------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).
  • Autopilot · 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.

@sonarqubecloud

sonarqubecloud Bot commented Oct 3, 2026

Copy link
Copy Markdown

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