Support for Configuration File #655
Labels
good first issue
The issue can be tackled by someone who has little to no knowledge about the project.
help wanted
Indicates that we would like someone that’s not a maintainer to work on the issue.
P4
Future work. E.g. something we might to get on in the future. Might be used for future ideas too.
request
The issue is a request for a new feature or plugin.
triaged
The issue has been reviewed but has not been solved yet.
I'm submitting a ...
What is the current behavior?
Detect secrets only accepts command line options for configuration
What is the expected behavior?
I'd like detect secrets to be able to take a configuration file where the common options can be set for use both by the command line and in a pre-commit hook.
This makes it easier / simpler to consistently use filter lists and get the same behaviour in a pre-commit hook and by the command line.
What is the motivation / use case for changing the behavior?
Simpler command line usage in concert with pre-commit hook usage.
It's certainly possible to do this with a shell script wrapper but that changes the invocation in pre-commit. It's pretty common
for tools of this nature to support a configuration file (e.g. yamllint, eslint etc.) for exactly this reason
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: