git hook to track lazy-lock.json

[m-faith]

Rather than needing to have:

You likely want to remove lazy-lock.json from your fork's .gitignore file too - it's ignored in the kickstart repo to make maintenance easier, but it's recommended to track it in version control.

...in the instructions, we could have a git hook take care of this... like a pre-push (or something) hook script that rebases (or some other strategy) to remove the commit that added that line (or add a commit to delete the line, or whatever).

[feoh]

Great idea but I don't think asking our very new neovim users to install git hooks is realistic.

[m-faith]

I would recommend this for the devs/maintainers of this project. The git hook should automate the process, as part of deploy/build pipepline, so that .gitignore file is in the proper state when the new user clones the repo.

I don't know what would work best for maintainers workflow... perhaps keep lazy-lock.json ignored in a separate dev branch?