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:27:08 -07:00
co-authored by Hanzo Dev
parent 83b3510b51
commit 25321627cc
2 changed files with 25 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
+10
View File
@@ -0,0 +1,10 @@
# Go client library for the CosyVoice TTS websocket API. The repo's own gate
# (Makefile `test`) is the suite; vet is added because it compiles the same
# packages and catches what the suite cannot reach.
#
# The live-API tests skip themselves without COSYVOICE_API_KEY, so what this
# proves on every push is that the client compiles and its offline assertions
# hold — it goes red on a broken protocol type or a bad frame encoder.
test:
- name: test
run: go vet ./... && go test -race ./...