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:34:17 -07:00
co-authored by Hanzo Dev
parent cda41ea6a7
commit 6bd0c3810b
2 changed files with 24 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: [master]
tags: ['v*']
pull_request:
workflow_dispatch:
jobs:
cicd:
uses: hanzoai/ci/.hanzo/workflows/build.yml@v1
secrets: inherit
+9
View File
@@ -0,0 +1,9 @@
# passport-apple — upstream ships no tests (`npm test` is the npm-init stub that
# exits 1), so the gate is the honest one available: install the dependency tree
# from the lockfile and load the strategy. It goes red on a syntax error, a bad
# export, or a dependency that no longer resolves.
test:
- name: load
run: |
npm ci --no-audit --no-fund
node -e 'const S=require("./src/strategy.js"); if (typeof S!=="function") throw new Error("src/strategy.js does not export a constructor")'