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:40:37 -07:00
co-authored by Hanzo Dev
parent d97c871aa7
commit a642484ed3
2 changed files with 37 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
+22
View File
@@ -0,0 +1,22 @@
# Canonical CI/CD config for hanzoai/husky — read by the hanzoai/ci reusable
# workflow (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
#
# LIBRARY: native git hooks for npm projects. No image, no deploy — it ships
# from a tag. package.json declares no scripts at all; test.sh IS the suite.
#
# And it is a good one, which is why it is the gate. test.sh packs the package
# with `npm pack` and then installs THAT TARBALL into twelve throwaway git
# repos, asserting the real behaviour each time: core.hooksPath is set, a
# failing pre-commit blocks the commit, install from a subdirectory works,
# a non-git directory is tolerated, HUSKY=0 skips, `set -u` scripts survive,
# `husky init` does what it says. Nothing here is mocked — it packs, installs
# and commits — so it fails on exactly what a user would hit.
#
# GIT_CONFIG_GLOBAL=/dev/null because the suite asserts on `git config
# core.hooksPath`, and a runner (or a developer) that has a global hooksPath of
# its own makes those assertions read the machine instead of the package. Test
# 9 fails that way on any box with global hooks configured. The per-repo config
# the suite sets up itself is untouched.
test:
- name: test
run: GIT_CONFIG_GLOBAL=/dev/null sh test.sh