ci: describe the runner the workflows expect

- ci.yaml asks for a docker-labelled runner and runs jobs in the named containers
- e2e.yaml says what it needs from a runner and that it has not been run on one
This commit is contained in:
tgiachi 2026-11-10 15:54:29 +01:00
commit 1d68f9506b
2 changed files with 6 additions and 3 deletions

View file

@ -1,5 +1,5 @@
# Runs on Forgejo Actions (Codeberg). Enable Actions in the repository settings and make sure
# a runner with the `docker` label is available; change `runs-on` if yours is named differently.
# Runs on Forgejo Actions. The jobs ask for a runner labelled `docker` that runs each job in the
# container named below; change `runs-on` if your runner is labelled differently.
name: ci
on:

View file

@ -1,5 +1,8 @@
# The end-to-end test starts Postfix and parsimony in Docker, so it needs a runner that can run
# Docker itself. Start it by hand from the Actions tab (or run `make e2e` locally).
# Docker itself, with the job on the host network (it talks to published ports on 127.0.0.1 and
# mounts temporary directories). A plain `docker` runner does not give a job a Docker daemon, and
# I have not run this workflow on a runner: use `make e2e` locally. Start it by hand from the
# Actions tab only once you have such a runner.
name: e2e
on: