Git LFS and husky prepush hook?

To summarize suggestions by @jmchambers and @Fandekasp, the following works for me and keeps the hooks under version control as desired:

1. Run git lfs update --manual
2. Copy each of the scripts the above command spits out into new files under version control. NOT into the .git/hooks/ dir, but instead into a new dir in your repo at hooks/. Name them hooks/pre-push-lfs, hooks/post-checkout-lfs, etc
3. Make those hook files executable: chmod +x hooks/*-lfs
4. Point husky to the files you just saved in package.json:

  "husky": {
    "hooks": {
      ...your other hooks...
      "pre-push": "echo $HUSKY_GIT_STDIN | hooks/pre-push-lfs $HUSKY_GIT_PARAMS",
      "post-checkout": "echo $HUSKY_GIT_STDIN | hooks/post-checkout-lfs $HUSKY_GIT_PARAMS",
      "post-commit": "echo $HUSKY_GIT_STDIN | hooks/post-commit-lfs $HUSKY_GIT_PARAMS",
      "post-merge": "echo $HUSKY_GIT_STDIN | hooks/post-merge-lfs $HUSKY_GIT_PARAMS"
    }
  }

Yes, this does mean that if those hooks for LFS ever change that your hook files would need to be updated to stay in sync, but if you look at those hooks files they are pretty inert - they just call the git lfs commands that must possess the actual business logic for the hooks. So I would estimate that is a minor issue - and would be easily solved after a future breaking change by repeating the here-entailed process of saving the hooks from git lfs update --manual to files, easily enforced by noticing that running git lfs update spits out an error after said future update, just like the first time you ran into this which brought you here…

What would probably solve the issue: ability to add hooks code instead of replacing it. For example:

"postinstall": "git lfs update --force && cd ./node_modules/husky && npm run install -- --append"