Files
zeekay 60925663a7 say Hanzo Git, which is what it is
"Forge" named nothing in this estate. The product is Hanzo Git, the address is
git.hanzo.ai, and the in-cluster service is hanzo-git.hanzo.svc. A generic word
invented for it sends a reader looking for a system that does not exist.

Comments only. ("unforgeable" stays — different word.)
2026-08-19 22:29:59 -07:00

27 lines
820 B
YAML

# CI/CD for hanzoai/billing — billing.hanzo.ai.
#
# This file IS the opt-in. A push to git.hanzo.ai fires ONE Hanzo Git-wide system
# webhook at platform.hanzo.ai, which reads this document at the pushed sha and
# schedules a BuildKit job per declared image. A repo WITHOUT a hanzo.yml is
# accepted and builds nothing — the delivery is green, the log says "202
# Accepted", and no image exists. That is the shape this repo was in: it shipped
# by hand, so a merged fix could sit indefinitely looking deployed.
images:
- name: billing
repo: ghcr.io/hanzoai/billing
context: .
dockerfile: ./Dockerfile
test:
- name: typecheck
run: |
pnpm install --frozen-lockfile
pnpm typecheck
- name: test
run: pnpm test
- name: build
run: pnpm build
- name: lint
run: pnpm lint