We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A simple one, but a lot of what is in husky v9 has thrown me ... I'm coming from v8 but some things aren't clear.
When running npx husky init, it seems like we get a .husky/_/** with everything ignored in git history.
npx husky init
.husky/_/**
I have moved a precommit hook outside to the root of .husky, but the script isn't executed ... I move it inside, and it is...
.husky
Yet all the documentation states otherwise.
I'm left scratching my head ... what do we do after npx husky init ... ?
Also, subsequent usage of npx husky init overwrites what is already in that directory, so ... I guess we no longer use the install hook.
Just left very confused from referencing v8, and the docs.
The text was updated successfully, but these errors were encountered:
Have you checked out the release note? https://github.com/typicode/husky/releases/tag/v9.0.1 I think the migration guide there is clear.
Sorry, something went wrong.
No branches or pull requests
A simple one, but a lot of what is in husky v9 has thrown me ... I'm coming from v8 but some things aren't clear.
When running
npx husky init
, it seems like we get a.husky/_/**
with everything ignored in git history.I have moved a precommit hook outside to the root of
.husky
, but the script isn't executed ... I move it inside, and it is...Yet all the documentation states otherwise.
I'm left scratching my head ... what do we do after
npx husky init
... ?Also, subsequent usage of
npx husky init
overwrites what is already in that directory, so ... I guess we no longer use the install hook.Just left very confused from referencing v8, and the docs.
The text was updated successfully, but these errors were encountered: