Hello!

Does the custom directory section of documentation match your problem?
https://typicode.github.io/husky/#/?id=custom-directory

I ran into this as well, and I was baffled to why this requires a custom directory config. This my case, and in BricePissard's case, the .git directory is not in a custom location, but rather in a perfectly reasonable and default location. It's completely normal for the .git directory to be one or more levels up.

Looking for it should be (and can be!) fully automated. In the same way that any git * command works anywhere in the dorectory structure, as long as somehwere in a parent or ancestor folder the .git directory can be found, indicating the presence of a git project.

It's on purpose because of two issues that happened:

1. Imagine you have a Python project and download a JS Open Source project as zip or tar. You proceed to run npm install, if husky recursively checks for .git then it can create issues with existing git hooks.
2. Some users also go to node_modules/some_project and run npm install inside them to quickly try things.

Also some users believe that package.json dependencies should not go below package.json root directory.

I understand it can be annoying and there's no universal solution. However the choice was made with husky 7 to lean on the side of safety and being more explicit where hooks should be installed by not allowing .. in the install path.

That said as @mateuszklinowski mentioned, you can cd .. && husky project/.husky. There's also a section for monorepos.

Hope it helps and clarifies the reasoning behind it :)

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@typicode wouldn't it be more convenient to have a flag for husky install that explicitly allows it to search for the .git directory upwards recursively? This would already be much more convenient than having to cd ../../.. to the correct level.

In my case it's even harder cause I'm integrating Husky as part of a project template, where the template cannot know where the .git directory will eventually be - it's supposed to be some levels up, but how many levels is not known beforehand.

@mateuszklinowski The link is not leading anywhere, could you update it? I believe this is the right one https://typicode.github.io/husky/guide.html#custom-directory