mirror of
https://github.com/hanzoai/team.git
synced 2026-09-30 01:57:35 +00:00
zeekayandHanzo Dev
a4ccd48437
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]>
29 lines
1.1 KiB
YAML
29 lines
1.1 KiB
YAML
# ~7-line canonical caller — all real config lives in /hanzo.yml, which
|
|
# platform.hanzo.ai reads too. The pipeline itself lives in hanzoai/ci and only
|
|
# there; naming a forwarder makes git.hanzo.ai take a second hop it cannot take.
|
|
#
|
|
# It does NOT roll out: app.hanzo.team is pinned to an explicit tag in the
|
|
# universe values file, rolled by a reviewed change there.
|
|
#
|
|
# master, not main: this is a fork of a master-based upstream, and renaming the
|
|
# branch would only make every comparison with upstream need a translation.
|
|
name: CI/CD
|
|
on:
|
|
push:
|
|
branches: [master]
|
|
tags: ['v*']
|
|
pull_request:
|
|
workflow_dispatch:
|
|
jobs:
|
|
cicd:
|
|
# 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
|