CI: gitleaks secret scanning on every push/PR - #4
Merged
Conversation
Generic gitleaks rules only — deliberately no org-specific patterns, since this workflow file is public. Full-history scan (fetch-depth 0), --redact so hits never print into public CI logs. Pinned to v8.30.1. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TrMEKd8TZniXL9v3PvVHP2
![baz-reviewer[bot]](https://avatars.githubusercontent.com/in/933528?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User description
What changed
Adds
.github/workflows/gitleaks.yml— full-history secret scan on every push and PR.Part of the public-repo hardening set (the other two are repo settings, already enabled):
protect-mainruleset (PRs required, no force-push/delete on main)Design notes:
--redact— a hit prints that a secret was found, never the secret itself (public CI logs).Testing
🤖 Generated with Claude Code
https://claude.ai/code/session_01TrMEKd8TZniXL9v3PvVHP2
Generated description
Below is a concise technical summary of the changes proposed in this PR:
Add a GitHub Actions workflow that runs the pinned gitleaks scanner on every push and PR to serve as a defense-in-depth layer while keeping hits redacted. Document that this workflow complements existing GitHub secret scanning and push protection safeguards.
Latest Contributors(1)