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]>
This commit is contained in:
2026-08-06 02:36:33 -07:00
co-authored by Hanzo Dev
parent bbe038af9d
commit 95bf3c587a
2 changed files with 52 additions and 0 deletions
+15
View File
@@ -0,0 +1,15 @@
# Canonical caller — every knob lives in /hanzo.yml, none here.
# Runs on the git-runner fleet at git.hanzo.ai, the only pool serving these
# labels. github.com resolves only .github/workflows and has no runner for
# them, so a caller placed there is a gate that cannot be scheduled.
name: CI/CD
on:
push:
branches: [main]
tags: ['v*']
pull_request:
workflow_dispatch:
jobs:
cicd:
uses: hanzoai/ci/.hanzo/workflows/build.yml@v1
secrets: inherit
+37
View File
@@ -0,0 +1,37 @@
# hanzoai/agent — the agent runtime: a Go module at the root and a Python SDK
# (uv) beside it.
#
# Gate only, no `images:`. ghcr.io/hanzoai/agent is built by
# .hanzo/workflows/deploy.yml from Dockerfile.sdk — the sole producer of that
# image, restored there for exactly that reason. Declaring `images:` here would
# make it the second.
#
# The Go half only. That is measured, not assumed: on this tree `go build`,
# `go vet` and `go test ./...` all pass, while `make sync` cannot resolve
# (requires-python >=3.9 against a transitive numpy needing >=3.10), `make lint`
# reports 2337 ruff errors and `make tests` dies at collection because a test
# module sys.exit(1)s on import without a provider key. Those three are recorded
# in LLM.md as work; a gate that is red on arrival for reasons no commit can fix
# gets read as broken CI rather than as broken code. The Python lane that DOES
# hold today — `uv sync --frozen` plus an import of the package — already runs
# natively in .hanzo/workflows/ci.yml.
#
# gofmt is checked by hand because gofmt reports on stdout and exits 0: the file
# list is the verdict, so an unchecked `gofmt -l` is a gate that cannot fail.
test:
- name: gofmt
run: |
set -euo pipefail
unformatted="$(gofmt -l .)"
if [ -n "$unformatted" ]; then
echo "::error::gofmt would rewrite these files:"
echo "$unformatted"
exit 1
fi
echo "gofmt: clean"
- name: build-vet-test
run: |
set -e
go build ./...
go vet ./...
go test -count=1 ./...