What
In a repo like:
.
├── .pre-commit-config.yaml
├── proj-a/
│ └── ...
└── proj-b/
├── .pre-commit-config.yaml
└── ...
If I only update a file proj-a/.
Don't download the hooks of proj-b on commit (and on prek run ?).
Why
For speed and so one project's pre-commit config doesn't impact development on another project.
Bonus: generalize
Don't download hooks if no file matches in the steps (due to files/exclude regexes).
I can see how that's harder to implement !
Is that feasible ? Hard to implement because of the current architecture ?
Is that something that would be welcome to the project ?
What
In a repo like:
If I only update a file
proj-a/.Don't download the hooks of
proj-bon commit (and onprek run?).Why
For speed and so one project's pre-commit config doesn't impact development on another project.
Bonus: generalize
Don't download hooks if no file matches in the steps (due to
files/excluderegexes).I can see how that's harder to implement !
Is that feasible ? Hard to implement because of the current architecture ?
Is that something that would be welcome to the project ?