Migrate to prek

[ulgens]

pre-commit development was stagnant for a while and now there is a strong alternative that's been writen with Rust: https://github.com/j178/prek

prek's readme list its features as

🚀 A single binary with no dependencies, does not require Python or any other runtime.
⚡ About 10x faster than pre-commit and uses only half the disk space.
🔄 Fully compatible with the original pre-commit configurations and hooks.
🏗️ Built-in support for monorepos (i.e. workspace mode).
🐍 Integration with uv for managing Python virtual environments and dependencies.
🛠️ Improved toolchain installations for Python, Node.js, Go, Rust and Ruby, shared between hooks.
📦 Built-in Rust-native implementation of some common hooks.

I tested it with the projects I'm working on and things are working fine, and even better because prek is faster while installing and running the hook dependencies.

We had a small discussion about the issues with pre-commit's maintenance and agreed to give a chance to prek, on Slack.

I tried to implement the simplest config for CI. We can also implement an optimized workflow with UV, similar to this one and shave off a couple more seconds from the runtime but I'm not sure that is necessary.

[Copilot]

Pull Request Overview

This PR migrates from pre-commit to prek, a Rust-based alternative that promises better performance and compatibility. The migration replaces the Python-based pre-commit tool with prek while maintaining the same functionality for code quality checks.

Key changes:

• Updates dependency from pre-commit to prek in development requirements
• Replaces GitHub Actions workflow to use prek-action instead of pre-commit
• Updates documentation to reflect the new tool and installation instructions

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
requirements/dev.txt	Replaces pre-commit dependency with prek
README.rst	Updates documentation section from "Pre-commit checks" to "prek checks" with new installation instructions
.github/workflows/prek.yml	Adds new GitHub Actions workflow for prek
.github/workflows/pre-commit.yml	Removes old pre-commit workflow

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

This line describes pre-commit but appears in a section about prek. The description should be updated to describe prek instead.

Suggested change

	`pre-commit <https://pre-commit.com>`_ is a framework to run hooks written in many languages, and it manages the language toolchain and dependencies for running the hooks.
	`prek <https://prek.j178.dev/>`_ is a tool for running git hooks, similar to pre-commit, but designed to be faster and dependency-free.

[ulgens]

This is intentional.

[pauloxnet]

I understand you intentionally left pre-commit sentence here. What's your goal in doing that?

[ulgens]

@pauloxnet That text is from prek's readme. I didn't leave it there, I copied it from https://github.com/j178/prek/blob/ee7110b49bb1aa8d7b3ccee51c5241550cb0aec2/README.md . If this is somehow confusing, I'm open for recommendations.

[ulgens]

Apart from this PRs merge status, we can disable pre-commit.ci integration, we have the related workflow already in the repo.

[pauloxnet]

I added a couple of minor comments.

Thanks for the PR. I approved it.

[pauloxnet]

I understand you intentionally left pre-commit sentence here. What's your goal in doing that?

[ulgens]

Rebased and resolved the conflicts. Do we have any concerns about this change? What is needed for the next step?

[pauloxnet]

Rebased and resolved the conflicts? Do we have any concerns about this change? What is needed for the next step?

I approved. I hope other can test it and approve it too.

[ulgens]

FastAPI migrated to prek from pre-commit just yesterday: fastapi/fastapi#14572 I think we can follow their example.

[pauloxnet]

I think we started this a long time ago. What's the blockers?

[ulgens]

@pauloxnet None, just waiting for the merge.

I rebased the PR and updated version references - it's good as new now.

[pauloxnet]

@pauloxnet None, just waiting for the merge.

I rebased the PR and updated version references - it's good as new now.

I reviewed and approved again. Let's merge this.

[ulgens]

@django/django-website-mergers 🍹

[SaptakS]

I am mostly fine with this. I do find prek to be a slightly new project (latest release being 0.2.23 which kind of indicates the maintainer considers this project still in development). But if everyone else is okay with that, I am fine.

[pauloxnet]

I am mostly fine with this. I do find prek to be a slightly new project (latest release being 0.2.23 which kind of indicates the maintainer considers this project still in development). But if everyone else is okay with that, I am fine.

Since 3 people are in favor of this PR, and others haven't commented at all, I assume they are not against it or don't have an opinion on it.

Other big projects like FastAPI just moved to prek.

Based on that I propose to merge.

[pauloxnet]

BTW other projects are migrating too from pre-commit to prek
python-humanize/humanize#276