ci: add gitleaks secret-scan workflow#6
Merged
Conversation
Matches the pattern in sentrix-labs/sentrix and the other Sentriscloud repos. Uses gitleaks binary v8.30.1 directly (gitleaks-action@v2 is paid for organizations). Non-blocking; surfaces findings as PR warnings.
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 the gitleaks (secret-scan) GitHub Actions workflow used across the rest of the Sentriscloud orgs.
Detects credentials accidentally committed (API keys, signed RPC URLs, private-key fixtures, hardcoded JWTs) before they hit shared history. Uses the gitleaks binary v8.30.1 directly — gitleaks-action@v2 requires a paid org license since 2023, the binary itself is MIT.
Non-blocking on findings (
|| echo ::warning::); branch protection gates that the scan ran. Findings surface as PR check warnings + workflow summary.