Add a git_hooks_path
config key.
#33
Open
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.
Add a
git_hooks_path
config key that allows a user to point the package to the correct path to place githooks for their project. This should be a non breaking change for existing users due to the default value provided in theconfig()
call.Motivation:
I wasn't able to get the package working as I was installing it in a git submodules setup where the Laravel project was a submodule in a large project. In that context the correct path for the git hooks is higher in the directory structure. This PR gives package users the option to configure that path so they can use it with git submodules (while keeping the existing default the same.)
CI Fix
The CI was failing already on master for Laravel 9, I've fixed this by adding an appropriate version of
orchestra/testbench
to thecomposer.json
.