Name the reusable at the path hanzoai/ci holds

The forge resolves a caller's uses: while it inserts the run, so a path
that does not exist aborts InsertRun and the push creates no run at all
-- five pushes, zero runs, and no error on any surface. hanzoai/ci@v1
carries build.yml under .github/workflows and nothing under
.hanzo/workflows, which is the address github.com can also resolve.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
2026-09-08 18:25:57 -07:00
co-authored by Hanzo Dev
parent eeaeaa31be
commit a4ccd48437
+9 -1
View File
@@ -16,5 +16,13 @@ on:
workflow_dispatch:
jobs:
cicd:
uses: hanzoai/ci/.hanzo/workflows/build.yml@v1
# The pipeline's one address. hanzoai/ci keeps it under .github/workflows
# because github.com resolves a reusable workflow out of that path alone and
# the forge reads it there too, so one file serves both planes.
uses: hanzoai/ci/.github/workflows/build.yml@v2
# The git-runner image ships the docker CLI and no daemon on purpose, so an
# image is built by the door in-cluster, never on the runner. The gate runs
# ahead of this either way.
with:
mode: delegate
secrets: inherit