Merge pull request 'Describe the CI runner the workflows expect' (#45) from ci/runner-notes into main
Some checks failed
ci / admin (push) Successful in 45s
ci / vuln (push) Has been cancelled
ci / go (push) Has been cancelled

This commit is contained in:
squidd 2026-11-10 16:01:35 +01:00
commit 23623c0df0
2 changed files with 12 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:
@ -12,6 +12,9 @@ jobs:
runs-on: docker
container: golang:1.27
steps:
# The checkout action runs on Node, which the golang image does not carry.
- name: Install Node
run: apt-get update -qq && apt-get install -y -qq nodejs git
- uses: actions/checkout@v4
- run: make go-ci
@ -28,5 +31,8 @@ jobs:
runs-on: docker
container: golang:1.27
steps:
# The checkout action runs on Node, which the golang image does not carry.
- name: Install Node
run: apt-get update -qq && apt-get install -y -qq nodejs git
- uses: actions/checkout@v4
- run: make vuln

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: