Skip to content

feat(workflows): add reusable pinned gitleaks secret scan - #8

Merged
itstimwhite merged 2 commits into
mainfrom
feat/reusable-secret-scan
Oct 12, 2026
Merged

itstimwhite merged 2 commits into
mainfrom
feat/reusable-secret-scan

Conversation

@itstimwhite

Copy link
Copy Markdown
Contributor

Adds .github/workflows/secret-scan.yml, a workflow_call secret scan that JovieInc repos can share instead of each keeping its own inline gitleaks steps.

  • Pinned gitleaks v8.30.1 with a sha256 check (the same pin LogYourBody uses today).
  • Scans before..sha on push, base..head on pull_request and merge_group, and everything reachable when no base is trustworthy (new branch, force push, schedule). Set full-history: true to scan all refs.
  • Uses the consumer's .gitleaks.toml when present.
  • fail-on-findings: false gives shadow mode for qualification (AGENTS.md: new fleet checks qualify in shadow first).
  • Least privilege: permissions: {} at the top, contents: read on the job, persist-credentials: false.

secret-scan-self.yml qualifies it here. It runs the behavioral tests (tests/test_secret_scan_workflow.py, which parses the YAML and runs the step scripts against a temp git repo and a fake gitleaks) and calls the workflow on this repo.

Local: 7/7 tests pass, actionlint is clean, and gitleaks reports no leaks on this repo.

Consumers adopt it in separate PRs pinned to the merge SHA (JOV-6555).

🤖 Generated with Claude Code

Callable workflow for every JovieInc repo: pinned, checksum-verified gitleaks,
range-scoped on push/PR/merge_group, full-history and shadow-mode inputs, and
behavioral tests that parse the YAML and run the step scripts.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Comment thread .github/workflows/secret-scan.yml
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@itstimwhite
itstimwhite merged commit 8a162bd into main Oct 12, 2026
3 checks passed
@itstimwhite
itstimwhite deleted the feat/reusable-secret-scan branch October 12, 2026 21:15
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