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
My suggestion is to preserve the existing hooks path if it is defined in git config core.hooksPath, so this way it's not necessary to take into account this step when you're migrating from Husky, for instance. This is also an issue when you're switching branches with different git hooks setup and requires executing a script in preinstall or preparelike explained here to make it transparent for users.
What do you think?
Thanks
The text was updated successfully, but these errors were encountered:
Hi 👋,
This is a feature request more than an issue.
My suggestion is to preserve the existing hooks path if it is defined in
git config core.hooksPath
, so this way it's not necessary to take into account this step when you're migrating from Husky, for instance. This is also an issue when you're switching branches with different git hooks setup and requires executing a script inpreinstall
orprepare
like explained here to make it transparent for users.What do you think?
Thanks
The text was updated successfully, but these errors were encountered: