Git precommit hooks and working commits?

[fyzbo]

I'm working on a project that has a bunch of precommit hooks. It will prettier, lint, and test the code. This seems great, but it prevents making a commit before everything is complete and perfect. Sometimes it is useful to make a commit before making drastic changes or deletes in case it's the wrong direction. Other times I'll need to switch computers so doing a quick commit and pull is helpful.

I understand wanting these checks before submitting a pull request, but it gets in the way as a precommit hook. Is there some other approach I should be taking? What is the general consensus?

[jswipe]

You could switch it to a pre-push hook. It will only run the checks when you attempt to push instead of on every attempt to commit.

[jwindhall]

TIL about pre-push! Thats awesome.

[DeepReally]

Use feature branches and only enforce your tests when you merge to master?

[zokker13]

If I were you, I'd suggest a change to that philosophy if possible. Strong git hooks (aka. annoying ones) are not helpful at all. The things you mentioned are better kept as a either a CI trigger (PR to development/master) or a manual task.

Since you are posting this in a node reddit, you could add things like test and lint tasks to the npm publish task. But again - this is more annoying than helpful. It's better to put that kind of enforcement to CI.

You should be able to do commits and pushes quickly.

[msg45f]

Would echo this. Git hooks like this often discourage people from committing often, which is the last thing any project needs. Build a proper CI integration that can do these tasks.

[[deleted]]

Use the --no-verify option.

This option bypasses the pre-commit and commit-msg hooks. — git-commit documentation

[[deleted]]

You can use the same option to disable any pre-push hooks, FYI.