Subsequent Init runs would clear Husky pre-commit

[fgrande]

Hi,

if I run "npx run init" after I've already changed pre-commit file in .husky/pre-commit, I lose my changes, it return to the "npm test"

I would suggest (going to send a PR) to create the pre-commit file only if it doesn't exists (so accidental multiple "npx run init" don't break changes).

Going to move the file creation into the try...catch, adding the flag "wx" (it raise an error if the file already exists)

regards
FabioG

[Munaf-Divan]

I have a similar requirement. I want my existing pre-commit to remain unchanged while I run npx husky init.

[kaspar-p]

+1. Deprecating install and replacing it with something that does not do what install did is annoying.

[typicode]

Init should be run only once. You can do the setup manually also.

[fgrande]

@typicode It "should" be run only once. But what if a dev runs it again, after changes on pre-commit file ? That's the meaning of my PR.

[shdq]

Removing the lines below from your hook files will solve your problems. See "How to Migrate" in the release notes.

e.g. .husky/pre-commit

- #!/usr/bin/env sh
- . "$(dirname -- "$0")/_/husky.sh"
npm run lint --fix

[DevJake]

Deprecating install and replacing it with something that does not do what install did is annoying.

Exactly this. An install command is logical, and I don't understand why it was deprecated. I cannot imagine many would want to manually install hooks either. Really, the init command should be idempotent by not overwriting file contents. @shdq I have just tested with what you suggested, with no luck... the file contents are still being overwritten :/

The documentation is rather lacking on what an alternative solution would be. There seemingly isn't a help command (I might be wrong!), so that would be beneficial to view what commands and flags are available.