Migrate to prek

# Conflicts:
#	README.rst

Author: ulgens

.github/workflows/pre-commit.yml

@@ -0,0 +1,13 @@
+name: prek checks
+
+on:
+    pull_request:
+    push:
+        branches: [main]
+
+jobs:
+    prek:
+        runs-on: ubuntu-latest
+        steps:
+            - uses: actions/[email protected]
+            - uses: j178/[email protected]

.github/workflows/prek.yml

@@ -370,26 +370,20 @@ Running Locally with Docker
 
 7. View the docs at http://docs.djangoproject.localhost:8000/.
 
-Pre-commit checks
------------------
+git hooks
+---------
+    `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.
 
-`pre-commit <https://pre-commit.com>`_ is a framework for managing pre-commit
-hooks. These hooks help to identify simple issues before committing code for
-review. By checking for these issues before code review it allows the reviewer
-to focus on the change itself, and it can also help to reduce the number of CI
-runs.
+    prek is a reimagined version of pre-commit, built in Rust. It is designed to be a faster, dependency-free and drop-in alternative for it, while also providing some additional long-requested features.
 
-To use the tool, first install ``pre-commit`` and then the git hooks
+\- quoted from `prek's README.md <https://github.com/j178/prek/blob/ee7110b49bb1aa8d7b3ccee51c5241550cb0aec2/README.md>`_
 
-.. code-block:: console
+To use git hooks locally, first install ``prek`` and then the git hooks:
 
-    $ python3 -m pip install pre-commit
-    $ python3 -m pre_commit install
+* Depending on your choice of platform and tooling, you can use the related installation instructions from https://prek.j178.dev/installation/
+* Install git hooks using ``prek install`` command: https://prek.j178.dev/cli/#prek-install
 
-On the first commit ``pre-commit`` will install the hooks, these are
-installed in their own environments and will take a short while to
-install on the first run. Subsequent checks will be significantly faster.
-If the an error is found an appropriate error message will be displayed.
-If the error was with ``isort`` then the tool will go ahead and fix them for
-you. Review the changes and re-stage for commit if you are happy with
-them.
+The installed hooks will be triggered during each commit, or can be manually triggered via
+``prek run`` command: https://prek.j178.dev/cli/#prek-run If an error is found an appropriate
+error message will be displayed. If the error was with ``isort`` then the tool will go ahead
+and fix them for you. Review the changes and re-stage for commit if you are happy with them.

README.rst

@@ -1,6 +1,6 @@
 -r common.txt
 black==25.9.0  # Used by Django's find_formatters and run_formatters
 django-debug-toolbar==6.0.0
-pre-commit~=4.3.0
+prek==0.2.5
 psycopg[binary]==3.2.10
 watchdog==6.0.0