Add ability to use init.sh as a global hook script
#1526
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is a simple workaround for all the users who have a global set of hooks that get clobbered by changing
core.hooksPath. E.g. if I havecore.hooksPathset globally to run hooks I want run on all repositories, Husky will change that location per-repo. With this change in place, I can at least create aninit.shscript to read the hook that is getting executed by Husky, and run my global hook manually first, followed by any Husky hooks.There may be a different or more robust way the team would like this done, if so feel free to reject this PR or make further suggestions.