Files
zeekayandHanzo Dev 7e198c5359 ci: a runner label names the platform, not the org
hanzo-build-linux-amd64, lux-build-linux-amd64, zoo-build-linux-amd64 and
every other org-prefixed spelling all meant the same machine. Which org a
job belongs to does not change which host can build it, so the org bought
one pool name per org per arch and each could go stale on its own -- the
evo host alone answered to fourteen names for one label.

One vocabulary now: linux-amd64, linux-arm64, macos-arm64, win-amd64. The
generic labels every plain workflow uses (ubuntu-latest, self-hosted) are
untouched, so naive CI keeps working.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-08 12:09:44 -07:00

57 lines
1.4 KiB
YAML

name: Docs
# Builds the docs site on the native runners (git.hanzo.ai → git-runner).
#
# This replaces .github/workflows/docs.yml, which built the site and then
# published it with actions/configure-pages + actions/upload-pages-artifact +
# actions/deploy-pages. Those three speak to the GitHub Pages API, which this
# forge does not have and is not going to grow — so the publish half cannot
# work here at all.
#
# The build half is worth keeping on its own: it fails on the commit that
# breaks the docs, path-filtered so it only runs when docs change. Publishing
# is gone until the site is served from the PaaS.
on:
push:
branches: [main]
paths:
- 'docs/**'
- '.hanzo/workflows/docs.yml'
pull_request:
paths:
- 'docs/**'
workflow_dispatch:
permissions:
contents: read
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
jobs:
build:
runs-on: [linux-amd64]
timeout-minutes: 20
steps:
- uses: actions/checkout@v4
- uses: pnpm/action-setup@v4
with:
version: 10
- uses: actions/setup-node@v4
with:
node-version: '22'
cache: 'pnpm'
cache-dependency-path: docs/pnpm-lock.yaml
- name: Install dependencies
working-directory: docs
run: pnpm install --frozen-lockfile
- name: Build docs
working-directory: docs
run: pnpm build