Integrations¶

This page documents common ways to integrate prek into CI and container workflows.

Docker¶

prek is published as a distroless container image at:

• ghcr.io/j178/prek

The image is based on scratch (no shell, no package manager). It contains the prek binary at /prek.

A common pattern is to copy the binary into your own image:

FROM debian:bookworm-slim
COPY --from=ghcr.io/j178/prek:v0.3.2 /prek /usr/local/bin/prek

If you prefer, you can also run the distroless image directly:

docker run --rm ghcr.io/j178/prek:v0.3.2 --version

Verifying Images¶

Docker images are signed with GitHub Attestations to verify they were built by official prek workflows. Verify using the GitHub CLI:

$ gh attestation verify --owner j178 oci://ghcr.io/j178/prek:latest
Loaded digest sha256:xxxx... for oci://ghcr.io/j178/prek:latest
Loaded 1 attestation from GitHub API
✓ Verification succeeded!

- Attestation #1
  - Build repo:..... j178/prek
  - Build workflow:. .github/workflows/build-docker.yml@refs/tags/vX.Y.Z

GitHub Actions¶

prek can be used in GitHub Actions via the j178/prek-action repository.

Example workflow:

name: Prek checks
on: [push, pull_request]

jobs:
  prek:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - uses: j178/prek-action@v1

This action installs prek and runs prek run --all-files on your repository.

prek is also available via taiki-e/install-action for installing various tools.