lfs/hook: teach lfs.Hook
about core.hooksPath
#1409
Merged
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 commit gives the
lfs.Hook
knowledge of the newcore.hooksPath
configuration value that was introduce in Git 2.9.0.
When
core.HooksPath
is found in the Git configuration AND is supported (i.e.,installed Git binary has a version greater than or equal to "2.9.0"),
git-lfs install
will place new hooks in that directory. If thecore.hooksPath
isspecified, but the installed verison of Git does NOT support it, then it will
be ignored and installed in
.git/hooks
as per usual.To test this behavior, two new shell tests were added:
core.hooksPath
is respectedcore.hooksPath
is ignoredUnfortunately, our current testing framework does not support skipping
individual tests, only skipping entire files, so two new shell test files were
added.
Resolves #1407.
/cc @technoweenie