litestar-org / litestar-org/project-template
build: evaluate migrating from pre-commit to prek
Open
Nobody has claimed this yet.
infra
question
- Dominant language
- Python
- Stars
- 13
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Context
prek is a faster, Rust-based, drop-in reimplementation of pre-commit — no Python bootstrap, single binary, reuses the existing .pre-commit-config.yaml.
This is a proposal / discussion issue, not a commitment.
Why consider it
- Faster hook runs & install, no separate Python env for the runner
- Aligns with the uv / Rust-tooling direction (#18)
- Config-compatible, so migration risk is low
Risks / open questions
- Maturity vs.
pre-commit; ecosystem familiarity for external contributors - CI action availability & caching story
- Does every current hook resolve under prek?
Proposed tasks
- Trial
prek run --all-filesagainst the current config - Compare local + CI runtime
- Decide: adopt / defer / reject (document rationale here)
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
Start with the existing .pre-commit-config.yaml and run prek run --all-files against it. Compare local and CI runtime, check whether the current hooks resolve and how CI caching would work. Done means documenting whether to adopt, defer, or reject prek and the rationale here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- build-system, ci-cd, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100