ci: add gitleaks secret scanning on pull requests - #1
Merged
Merged
Conversation
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.
Adds PR-gated secret scanning, matching what already runs in
valleywide-buildersandULFBUILT..github/workflows/gitleaks.yml— scans only the commits a PR introduces, so it blocks new secrets without failing on pre-existing history.gitleaks.toml— extends the default ruleset; allowlists.env.exampleandREADME.mdworkflow_dispatchis wired for an on-demand full-history audit.Prompted by an R2 credential that reached
riguchi2's history with no CI able to catch it. That key has since been rotated.🤖 Generated with Claude Code