Skip to content

fix(ci): call the secret scanner from proven-cicd-and-workflows - #43

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/secret-scanner-caller
Nov 10, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
claude/secret-scanner-caller

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Why

secret-scanner.yml called metadatastician/standards/.github/workflows/secret-scanner-reusable.yml. This repository's Actions settings do not allow reusable workflows from that owner, so every run failed at startup with 0 jobs. scan / gitleaks was never reported, and each push sent a "Run failed" email.

What

The caller now uses the published cicd-suite scanner owned by hyperpolymath, at the pin that gitbot-fleet and contractiles (hyperpolymath/contractiles#75) use:

  • hyperpolymath/proven-cicd-and-workflows/.github/workflows/secret-scanner-reusable.yml@1fd5e6371a50f0fc3687206a5adca0cdf7b39aa6
  • fast-pr: false, contents: read only, and no secrets: inherit.

actions.lock is unchanged: its entry for this workflow is already [].

Testing

In contractiles the same caller reported scan / gitleaks, scan / rust-secrets and scan / shell-secrets as success on its PR and on main. This PR's own run is the test here.


Generated by Claude Code

The caller used metadatastician/standards, which this repository's Actions
settings do not allow, so every run failed at startup with zero jobs and the
scan / gitleaks context was never reported. Call the published cicd-suite
scanner at the pin gitbot-fleet and contractiles use (1fd5e63), with
fast-pr false, contents: read only, and no `secrets: inherit`.

actions.lock is left as it is: regenerating it here would also prune the
reusable-workflow entries of other workflows.

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

coderabbitai Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 5 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

Commits

Reviewing files that changed from the base of the PR and between 39b4b1c and 600d34e.

Files selected for processing: 1

  • .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

@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 10, 2026 21:45
@hyperpolymath
hyperpolymath merged commit 96ff750 into main Nov 10, 2026
12 checks passed
@chatgpt-codex-connector

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

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

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-10T21:45:03.562683Z
We couldn’t complete this review. Comment @codex review to try again.
600d34e 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.

@hyperpolymath
hyperpolymath deleted the claude/secret-scanner-caller branch November 10, 2026 21:45
@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.

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.

3 participants