[CLOUD-4610] Add gitleaks secret scanning - #3
Merged
Conversation
bharathimanukonda
approved these changes
Jul 27, 2026
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
2 participants
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 gitleaks secret scanning to this repo.
.gitleaks.toml— gitleaks config; extends the default ruleset (with allowlist entries for known false positives)..pre-commit-config.yaml— adds the gitleaks hook so secrets are caught before they're committed..github/workflows/gitleaks.yml— runs gitleaks on pull requests and pushes tomainvia the gitleaks binary (the org Actions allowlist blocks third-party actions). Non-blocking for now: reports findings without failing the build, so we can clear false positives before enforcing.Part of the org-wide secret-scanning rollout (CLOUD-4610).