What kind of feature are you missing? Where do you notice a shortcoming of PTB?
Recently I've been using prek in my projects instead of pre-commit. Prek is a much faster, drop in replacement for pre-commit, which takes half the disk space.
I didn't find any downsides to it during my testing, and it also runs hooks in parallel, which speeds up development (specially for us since pylint and mypy both take a while)
Describe the solution you'd like
Use prek. The config file doesn't need to change at all. In fact, we can remove the ci: section in there, and replace that with this github action https://prek.j178.dev/integrations/#github-actions. This way the pre-commit.ci bot will not make any unnecessary pull requests for auto updates anymore.
Describe alternatives you've considered
Stick to using pre-commit, but since this is a drop in replacement, we should switch over.
Additional context
No response
What kind of feature are you missing? Where do you notice a shortcoming of PTB?
Recently I've been using
prekin my projects instead ofpre-commit. Prek is a much faster, drop in replacement for pre-commit, which takes half the disk space.I didn't find any downsides to it during my testing, and it also runs hooks in parallel, which speeds up development (specially for us since pylint and mypy both take a while)
Describe the solution you'd like
Use prek. The config file doesn't need to change at all. In fact, we can remove the
ci:section in there, and replace that with this github action https://prek.j178.dev/integrations/#github-actions. This way the pre-commit.ci bot will not make any unnecessary pull requests for auto updates anymore.Describe alternatives you've considered
Stick to using pre-commit, but since this is a drop in replacement, we should switch over.
Additional context
No response