fix: fix execute permission not applied to hooks on linux machines #25
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.
During an install on a linux system a
chmod +x
command needs to be applied to each hook by theSetExecutablePermission
method.The call to
Directory.GetFiles(path).Where(f => !f.Contains("."))
was ignoring any hooks in the husky dir as it was getting the full path and file name for each file. The full path included a dot in the parent folder name/.husky
causing the file to be skipped. This change inspects only the file name to ensure the hooks are included in the call to SetExecutablePermission.Type of change