Files
zeekayandHanzo Dev a44471f5ef ci: canonical pair — hanzo.yml + forge caller
github.com has no runner for hanzo-build-linux-amd64, so a caller under
.github/workflows is a gate that can never be scheduled. This is the ~7-line
caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-06 02:29:24 -07:00

18 lines
753 B
YAML

# Canonical CI/CD config for hanzoai/doctype — the one file both the hanzoai/ci
# reusable (.hanzo/workflows/cicd.yml) and platform.hanzo.ai read.
#
# A Go module (the doctype schema: coercion, naming, permissions, secrets) that
# hanzoai/framework and hanzoai/base both compile against. It ships from a tag
# and builds no image, so there is no `images:` and no `deploy:` — only a gate.
#
# The suite is the contract every consumer depends on: coerce, naming, perm and
# secret each have a test file, and the stampfixture guard exists to keep the
# fixtures honest. `-count=1` so a green is this commit and not the test cache.
test:
- name: build
run: |
set -e
go build ./...
go vet ./...
go test -race -count=1 ./...