pre-commit hooks interfere with in-progress commit dev workflows

Observed behavior

When working locally, git is a powerful tool for storing in-progress work. It’s often desirable to commit changes that are not yet complete, even if there are bugs or formatting issues.

Pre-commit hooks impede a developer’s ability to use git as a way to save in-progress work.

It’s possible to do with git commit --no-verify, but this is a hard command to remember and again impedes the flow of the developer’s work, especially because it’s not available from most git GUIs.

Expected behavior

Pre-commit should not get in the way of developer’s workflow.

The developer, and not the linter, ought to be in control of what is allowed to be committed in local, unshared working branches.

User-facing consequences

Certain kinds of dev workflows are impeded

Context

0.13.1

[indirectlylit]

If that works for you then that’s fine, but there are more effective strategies for saving in-progress work using git

[benjaoming]

pre-commit inherently works against this

You can install it as pre-push or whichever local hook of your preference.

https://pre-commit.com/#pre-commit-install

Best practice in git is to commit early and often

I don’t do that? I use stashing quite a lot, though.