You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on feedback received from various users it seems that there are two parties, both big: one that likes auto-fixing code and one that doesn't like to touch the code after running.
Can we define an environment variable like PRE_COMMIT_AUTOFIX=[0|1] which could tell the hooks to touch (fix) or not to touch the source code when running?
Example hooks: end-of-file-fixer and trailing-whitespace.
The text was updated successfully, but these errors were encountered:
I don't think that would help, there are only a few executables under control of pre-commit and to be frank the party that doesn't want their code edited I believe to be in the wrong. Even if the few fixers pre-commit can influence implemented this option there's far more that would oppose implementing something like this.
what's the target workflow of one of these individuals? can they run git checkout -- . and then it's as-if the fixers never ran?
Based on feedback received from various users it seems that there are two parties, both big: one that likes auto-fixing code and one that doesn't like to touch the code after running.
Can we define an environment variable like
PRE_COMMIT_AUTOFIX=[0|1]
which could tell the hooks to touch (fix) or not to touch the source code when running?Example hooks:
end-of-file-fixer
andtrailing-whitespace
.The text was updated successfully, but these errors were encountered: