Skip to content

Conversation

@ccjmne
Copy link

@ccjmne ccjmne commented Nov 19, 2025

Hey guys,
I got started on some implementation so we have some base to work off.

Resolves #171, #1572, #1602.

Warning

The current implementation is likely not most adequate in all cases, considering @simon-abott 's valuable insights in #1591.

ccjmne and others added 3 commits November 19, 2025 11:50
Co-authored-by: J-Chris-Findlay-RESIDEO <[email protected]>
Suggested-by: J-Chris-Findlay-RESIDEO <[email protected]>
Ref: typicode#1602
You may choose another Git directory name, or be using worktrees; Husky
should still find the original hooks regardless.

Ref: typicode#1602
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Not clear how to use Husky with existing hooks

1 participant