Adopt pre-commit.ci?
Open
Nobody has claimed this yet.
infrastructure
question
- Dominant language
- Python
- Stars
- 751
- Forks
- 324
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 3
Description
It's generally a much better experience around pre-commit and we'll get automated PRs for updates.
Thoughts?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Evaluate the proposed adoption of pre-commit.ci and how it would fit the repository's existing checks. Define the intended automated update workflow and acceptance criteria before making a change; the issue does not name files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100