You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In git 2.9, a new hooksPath configuration variable was added which is a perfect companion to overcommit. It lets you keep a common directory where hooks can reside and you never have to ever worry about keeping your hooks in sync between your repositories.
It seems as though a $REPO_ROOT/.git/hooks is hard coded where overcommit's hooks look for the base overcommit script.
I'd love to see support for overcommit looking to see if git's hooksPath configuration option was set and, if so, looking for the overcommit script in that location.
The text was updated successfully, but these errors were encountered:
In git 2.9, a new
hooksPath
configuration variable was added which is a perfect companion toovercommit
. It lets you keep a common directory where hooks can reside and you never have to ever worry about keeping your hooks in sync between your repositories.It seems as though a
$REPO_ROOT/.git/hooks
is hard coded where overcommit's hooks look for the base overcommit script.I'd love to see support for overcommit looking to see if git's
hooksPath
configuration option was set and, if so, looking for the overcommit script in that location.The text was updated successfully, but these errors were encountered: