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
I propose adding a CI job, that runs using a cron job (once per month like the dependabot?), and updates the pre-commit hooks config. What do you think?
Affected
devs
Minimal functionality
The job should run
pre-commit autoupdate
check, if the .pre-commit-config.yaml changed, if yes, commit it and create a PR.
https://pre-commit.ci/ does this automatically, but I guess we don't need another service involved.
Good idea! I would also be fine with the pre-commit service, but I should only create PR to update-dependencies or somethin similar which we then merge into dev-*.
But if you prefer, we can use https://pre-commit.ci/ as well. I have not used it before, but a lot of projects use it, it is from the author of pre-commit itself. They can do the linting for us as well then. They say it is really fast.
Rationale / Begründung
I propose adding a CI job, that runs using a cron job (once per month like the dependabot?), and updates the pre-commit hooks config. What do you think?
Affected
devs
Minimal functionality
The job should run
check, if the
.pre-commit-config.yaml
changed, if yes, commit it and create a PR.https://pre-commit.ci/ does this automatically, but I guess we don't need another service involved.
References / Verweise
The text was updated successfully, but these errors were encountered: