getGitHooksPath helper function
#177
Merged
Conversation
This file contains 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
|
@DmitryTsepelev thanks for pointing out that formatting issues. I applied |
Envek
reviewed
May 5, 2021
Envek
approved these changes
May 5, 2021
skryukov
approved these changes
May 5, 2021
|
Released in 0.7.5. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #170
This PR adds
getGitHooksPath()helper as a source of truth about where git hooks are storedIt uses
git rev-parse --git-path hookscommand under the hood (kudos to @stevelacy for the hint!), so it considers possible overriding default.git/hookstooThis is my first PR to the repo, so please, let me know, if I can improve it in any way