New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Using hooks at different stages #768
Comments
First: thanks for the issue! 🎉
The current suggestion is to just run
This is correct as written.
There is a bit of duplication in the configuration right now, true. I plan at some point to add something like: default_stages: [commit] to the top level so the duplication can be avoided (slightly) (though I'm still not 100% sold on this idea since it's nice and explicit right now).
pre-commit currently stores zero state about runs, I don't really want to get into the business of managing that 😆 Hope this clarifies some things :) |
Thanks for the quick reply.
|
yep, it's on my open source TODO |
This has been released as part of v1.14.0 🎉 -- thanks again! |
For example:
Am I understanding the limitations of stages correctly? Can anything be improved from the framework side to make commit and commit-msg stages not duplicate work or be more intelligent about what runs where? Maybe keep track of if a hook ran in the commit stage and avoid running it in the commit-msg stage?
The text was updated successfully, but these errors were encountered: