Repository navigation
Add narrow secret-scan configs - #78
Merged
Merged
Conversation
Ignores only the tracked fixture directory for ggshield and gitleaks, and keeps both files out of the dist archive.
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
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 narrow secret-scan configs written by
secret_scan.py check --write:.gitguardian.yaml(ggshield) and.gitleaks.tomlignore only the tracked test-fixture directory. Nosrc/, no whole test tree, no docs, no detectors.secret_scan.py detect --ref origin/mainfound no real and no dummy credentials in this repository, so no source changes were needed.checknow returns 0.The GitGuardian GitHub App does not read
.gitguardian.yaml; to silence the PR check for these paths, mirror them into the dashboard exclusion rules (workspace Manager only).