mirror of
https://github.com/hanzoai/attendant.git
synced 2026-11-02 20:00:51 +00:00
zeekayandHanzo Dev
f0d0f44ee8
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]>
20 lines
611 B
YAML
20 lines
611 B
YAML
# The canonical caller. All real config lives in /hanzo.yml, which
|
|
# platform.hanzo.ai reads too.
|
|
#
|
|
# It does NOT roll out: the attendant is pinned to an explicit tag in
|
|
# hanzo/universe (charts/app/values/hanzo/attendant.yaml), rolled by a reviewed
|
|
# change there. That is what hanzo.yml means by having no `deploy:` section — a
|
|
# patch from CI would be restored from the universe pin on cd.hanzo.ai's next
|
|
# poll anyway.
|
|
name: CI/CD
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
tags: ['v*']
|
|
pull_request:
|
|
workflow_dispatch:
|
|
jobs:
|
|
cicd:
|
|
uses: hanzoai/ci/.github/workflows/build.yml@v1
|
|
secrets: inherit
|