Name hanzoai/captable as the repository the forge builds
Hanzo CI/CD / cicd (push) Waiting to run
CI/CD / cicd (push) Waiting to run

git.hanzo.ai launches runners for the hanzoai namespace, so the image is
built from the hanzoai/captable mirror; hanzo-apps/captable keeps the same
commits without a build.
This commit is contained in:
zooqueen
2026-09-15 12:25:32 -07:00
parent d65dc5af98
commit e96032f0ed
+5 -5
View File
@@ -1,8 +1,8 @@
> **`hanzo-apps/captable` builds `ghcr.io/hanzoai/captable`**: git.hanzo.ai
> mirrors it and runs `.hanzo/workflows/cicd.yml` against `hanzo.yml`.
> `github.com/hanzoai/captable` holds the same commits because it is the Go module
> path the cloud binary imports. It has no forge build, so one repository
> publishes the image. Push every commit to both.
> **`hanzoai/captable` builds `ghcr.io/hanzoai/captable`**: git.hanzo.ai
> mirrors it and runs `.hanzo/workflows/cicd.yml` against `hanzo.yml`. It is also
> the Go module path the cloud binary imports. `hanzo-apps/captable` holds the
> same commits and has no forge build, so one repository publishes the image.
> Push every commit to both.
<p align="center"><img src=".github/hero.svg" alt="captable" width="880"></p>