Run prek as a GitHub Action

[DimitriPapadopoulos]

This requires to enable GitHub Actions in this repository.

[effigies]

Can you provide a summary of what this is supposed to do?

[DimitriPapadopoulos]

prek is a drop-in replacement of pre-commit written in Rust.

Like pre-commit, prek can be run:

• by developers on their computer, typically with prek run -a or as a Git commit hook,
• during CI: an equivalent of the pre-commit.ci service is not available (yet?) but a well-maintained GitHub Action is provided, which I use here.

Because it's a drop-in replacement, developers can keep using pre-commit locally if they prefer so, while other developers and CI can switch to prek.

[DimitriPapadopoulos]

Some (non-scientific) literature on the subject:

• From pre-commit to Prek: The Evolution of Code Quality Automation
• Happier Developers, Faster Teams: Why Prek Beats Pre-commit
• Ready prek go!
• gh-143148: Replace pre-commit with prek in CI python/cpython#143149

[effigies]

I would suggest just using https://pre-commit.ci/, rather than adding a new GHA workflow.

[DimitriPapadopoulos]

The thing with pre-commit.ci, which by the way is not enabled in this repository as far as I can see, is that you give it full repository access. That's an additional operator you need to trust.

[DimitriPapadopoulos]

GitHub Actions, on the other hand, need not this additional service provider. They are run by GitHub, and you already trust GitHub services by hosting the repository on their servers.

[DimitriPapadopoulos]

The idea here was to use prek instead of pre-commit. For now prek can only be run from GHA.