Files
zeekayandHanzo Dev 096f96835b runs-on names a machine, not a purpose
The purpose-prefixed labels (hanzo-build-*, hanzo-deploy-*, hanzo-docs-build-*)
are retired in favour of the bare <os>-<arch> every runner already advertises.

They were not a capability, only a habit, and the habit cost builds: papers asked
for hanzo-build-linux-amd64, no online runner offered it, and two idle
linux-amd64 runners sat beside the queue while the build simply never ran. The
lux tree lost three days to lux-linux-amd64 the same way.

What a job is FOR is the workflow's name. runs-on is the machine it needs.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 11:36:52 -07:00

46 lines
975 B
YAML

name: Documentation Tests
on:
push:
branches: [master, examples]
pull_request:
branches: [master, examples]
permissions:
contents: read
jobs:
doctests:
name: doctests
runs-on: linux-amd64
services:
redis-stack:
image: redislabs/client-libs-test:8.8.0
env:
TLS_ENABLED: no
REDIS_CLUSTER: no
PORT: 6379
ports:
- 6379:6379
strategy:
fail-fast: false
matrix:
go-version: ["1.25"]
steps:
- name: Checkout code
uses: actions/checkout@v6
# After checkout, so setup-go's module cache can key off go.mod. Ahead of
# it the file is not on disk yet and the cache silently degrades to a miss.
- name: Set up ${{ matrix.go-version }}
uses: actions/setup-go@v6
with:
go-version: ${{ matrix.go-version }}
- name: Test doc examples
working-directory: ./doctests
run: make test