ci: add gitleaks secret scan job#4
Merged
Merged
Conversation
Run the OSS gitleaks binary on commits introduced by each PR / push. Avoids gitleaks-action@v2 which requires a paid license for GitHub org repos. Scans only the commit range new to the event (PR base..head or push before..after) so pre-existing findings outside the change aren't re-reported. First-push case falls back to the tip commit alone since there is no prior ref. `.gitleaks.toml` extends the built-in default ruleset; project-specific allowlists can be added later if false positives surface.
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.
Summary
Adds a
gitleaksjob to the CI workflow:gitleaksbinary directly (v8.18.4).gitleaks-action@v2requires a paid license for GitHub org repos, so we install the binary instead.base..head, or pushbefore..after). Scanning full history would re-report pre-existing findings that aren't the PR's problem.fetch-depth: 0keeps both ends of the range available locally.before== zero SHA) falls back to scanning the tip commit only..gitleaks.tomlthat extends the built-in default ruleset; project-specific allowlists can be layered on later if false positives surface.Test plan
base..head