-
-
Notifications
You must be signed in to change notification settings - Fork 177
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The one change needed to support Husky v9 is to stop follow the configured git hook path and always check in `.husky`, the rest of the logic in #500 causes issues rather than helps. I simply reverted the plugin to the implementation prior to #500 and simply added the `false` to `getGitHookPaths('.husky', false)` and that makes all tests pass – both Husky v8 and Husky v9 – and works in both kinds of projects for me. Side note: Husky v9 is backwards compatible with Husky v8 and says that one shouldn't have to do anything when upgrading for it to work.
- Loading branch information
Showing
3 changed files
with
4 additions
and
28 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters