hanzoai/ci keeps the reusable at .github/workflows/build.yml — the one path
both planes resolve, since github.com reads a reusable only from there and the
forge reads it too. The v1 tag moved with it, so a caller still naming
.hanzo/workflows/build.yml asks for a blob that is not in the tree:
InsertRun: read hanzoai/ci@v1:.hanzo/workflows/build.yml: object does not exist
The caller itself stays at .hanzo/workflows/cicd.yml on purpose: github.com has
no runner for these labels, so a caller placed there could never be scheduled.
Co-authored-by: Hanzo Dev <[email protected]>
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]>
Adds the Apache/MIT section-4 style attribution this fork was missing: the
upstream project and license, the manifest revision tracked, and the fact that
components the tooling builds carry their own licenses — ROCgdb notably GPL.
This meta-repository carries AMD's MIT-licensed ROCm manifest and build tooling
unmodified; the NOTICE names the upstream, the manifest revision it tracks, and
the per-component licenses the tooling pulls in — including the GPL-licensed
ROCgdb, which is copyleft and must not be assumed MIT like the rest.
zeekayandHanzo Dev