Possible way to set up cargo-husky git hooks with cargo-nextest?

[lmmx]

I was just working on a new project and in a case of RTFM, hadn't realised cargo test was required to set up git hooks when using cargo husky as a dev dep. I always use cargo nextest run so it hadn't installed

I asked Claude why this happens and it said

Cargo-husky installs git hooks during the build phase of your crate (via build.rs), not during test execution. The hooks get installed when:

• The crate is built for the first time
• Any dependency changes trigger a rebuild
• The build script itself changes

Since cargo nextest run likely uses cached build artifacts and doesn't rebuild your crate, the build.rs script never runs, so the hooks never get installed.

Not sure if this is correct (and don't want to get too side-tracked verifying!), but am wondering if there's any workaround that would be possible or whether it's somehow infeasible due to how nextest works 🤔 Any clues welcome

[sunshowers]

Thanks for the issue. Nextest doesn't alter the build process at all (deliberately so to reuse caches) so I'm not sure what's going on. Could you provide a minimized reproduction?

[lmmx]

Well, I made a minimal repro only to find that it did not reproduce, cargo nextest run set up the git hooks from the .cargo-husky hooks dir as expected. Not sure why it looked like it wasn't working in that case! Sorry for the false alarm.