We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We somewhat recently added an --exclude-lines option when scanning, that will end up in the baseline here:
--exclude-lines
"exclude": { "files": "...", "lines": "(foo)" },
We might as well not make people do e.g.
- id: detect-secrets args: ['--baseline', '.secrets.baseline', '--exclude-lines', '(foo)']
in their .pre-commit-config.yaml, if they already have a line exclude in their baseline.
.pre-commit-config.yaml
The text was updated successfully, but these errors were encountered:
This is handled in the upcoming v1 release through filters (https://github.com/Yelp/detect-secrets/blob/pre-v1-launch/docs/filters.md). Once the baseline is loaded, all settings are also configured, which carry over any line/file exclusions, as well as other filters (e.g. wordlist, verifiability, etc.)
Closing as done.
Sorry, something went wrong.
No branches or pull requests
We somewhat recently added an
--exclude-lines
option when scanning, that will end up in the baseline here:We might as well not make people do e.g.
in their
.pre-commit-config.yaml
, if they already have a line exclude in their baseline.The text was updated successfully, but these errors were encountered: