-
Notifications
You must be signed in to change notification settings - Fork 10
Description
If I run a command like this I find a bunch of secrets in a git repo based solution no problem:
detect-secrets -C "C:\Source\Solution1" scan
If I run the following I don't see the same secrets found in this sub-folder:
detect-secrets -C "C:\Source\Solution1\Project1\Pages" scan
If I add --all-files I then see the secrets found
It seems as though the tool only utilises the git folders when ran against the location where the .git folder exists, is it possible for the tool to be updated to support recursively going up the directory tree to find the git repo folder and use it for the content in the sub-folder being run against.
For now I am running using --all-files along with a bunch of file exclusions to ignore content I am not interested in which is not ideal, especially given how normal git tooling handles sub folder based actions.