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
I just discovered that husky will install its git hooks at the nearest git repository. I keep my dotfiles in git and was surprised to find husky hooks in my ~/.git/hooks directory, from when I was testing an Annotator release.
Here's my comment on a husky issue:
I'd like to use husky in a project that will be distributed as a tarball. I don't want husky to install hooks when users build the project.
Would it be possible to default to the old behavior of assuming that the git directory is at the same level as package.json, install no hooks if it's not found, and add a configuration switch for setting an explicit root? That would make the default safer while allowing those with different layouts the ability to still use husky.
Create a distribution by creating a shallow git clone.
Distributing a shallow clone has several befenits:
- Join upstream development with `git fetch --unshallow`
- Husky install is contained (close#72)
- The distribution can reproduce itself
Create distribution tarballs by creating a shallow git clone.
Distributing a shallow clone has several befenits:
- Join upstream development with `git fetch --unshallow`
- Husky install is contained (close#72)
- The distribution can reproduce itself
I just discovered that husky will install its git hooks at the nearest git repository. I keep my dotfiles in git and was surprised to find husky hooks in my
~/.git/hooks
directory, from when I was testing an Annotator release.Here's my comment on a husky issue:
typicode/husky#36 (comment)
I think we need to resolve this before release because I really don't want to install hooks into unknowable locations on users' machines.
The text was updated successfully, but these errors were encountered: