… where modified to be over the 32727 command line length
When git-secrets is run, for all filepaths that are part of the staged list of changes they get passed into an invocation of git grep
If there is a large number of staged files, depending on the length of each file path from the git repo root, it could result in an extremely long line being supplied to git grep
For example if the git structure is as below
It would take around changes to 900 Include/TestLibrary/MyTestComponentNNNN.h files within the repo to cause the git grep to be passed an argument list that is too long
Issue #192, if available:
Description of changes:
Fixed issue where git secrets could fail if the bash invocation of git grep within the git-secrets shell script passed enough file paths that caused the command line invocation for git grep to be over 32767 characters
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
… where modified to be over the 32727 command line length
When git-secrets is run, for all filepaths that are part of the staged list of changes they get passed into an invocation of
git grep
If there is a large number of staged files, depending on the length of each file path from the git repo root, it could result in an extremely long line being supplied togit grep
For example if the git structure is as belowIt would take around changes to 900
Include/TestLibrary/MyTestComponentNNNN.h
files within the repo to cause thegit grep
to be passed an argument list that is too longIssue #192, if available:
Description of changes: Fixed issue where git secrets could fail if the bash invocation of
git grep
within the git-secrets shell script passed enough file paths that caused the command line invocation forgit grep
to be over 32767 charactersBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.