Enable pre-commit autoupdates
- Dominant language
- No language data
- Stars
- 150
- Forks
- 38
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
The current pre-commit config depends on https://github.com/astral-sh/ruff-pre-commit/releases/v0.1.8 while the newest version is https://github.com/astral-sh/ruff-pre-commit/releases/v0.2.0 ([changelog](https://github.com/astral-sh/ruff/blob/c53aae0b6f037b0d664f2d63364adbd02fb5acbc/CHANGELOG.md#020)). While we can manually update these dependencies, there is some room for automation.
Considerable options are:
- enabling https://pre-commit.ci service for this repo,
- adopting [renovate](https://github.com/renovatebot/renovate),
- waiting as long as https://github.com/dependabot/dependabot-core/issues/1524 is open [with the possibility to supply a temporary workflow](https://github.com/astral-sh/ruff/pull/8411/files).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the current pre-commit configuration and comparing the pre-commit.ci, Renovate, and temporary workflow options described in the issue. Choose and document an automation approach, then verify that it updates the Ruff dependency without disrupting the repository's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100