Hook currently fails to interpret filenames with spaces #470
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.
I noticed that
detect-secrets-hook -v --baseline .secrets.baseline $(git ls-files)
interprets filenames containing spaces as separate arguments, preventing them from being scanned. It seems like with the current README.md command it is possible to evade secrets detection by naming files in this way.To prevent that, it would be better to use the
-z
argument forgit diff
andgit ls-files
, splitting by NUL instead, and passing the arglist todetect-secrets-hook
via xargs -0.I'm not sure if the change needs to be made elsewhere as well, possibly in the .pre-commit hook?
Thanks!