mirror of
https://github.com/hanzoai/compute.git
synced 2026-11-02 22:00:43 +00:00
zeekayandHanzo Dev
53005ad3ae
build.yml was deleted from .github/workflows without a replacement anywhere, so the promoted and live visor App had nothing left that could build ghcr.io/hanzoai/visor — and no red run to show it, because a workflow that does not exist cannot fail. Restored byte-for-byte from history at the path the forge reads. runs-on is untouched; the forge's runner answers the same labels. Installed sync.yml, which this repo never had: without it a push reaches only GitHub and the forge never hears about the ref, which is exactly how a build lane goes quiet without anything turning red. Dropped workflow-sanity.yml. It triggers on paths .github/workflows/**, so once the workflows live under .hanzo it can never fire again. Co-authored-by: Hanzo Dev <[email protected]>
24 lines
686 B
YAML
24 lines
686 B
YAML
name: Docker
|
|
on:
|
|
workflow_dispatch:
|
|
push:
|
|
branches: [main]
|
|
tags: ['v*']
|
|
permissions:
|
|
contents: read
|
|
packages: write
|
|
id-token: write
|
|
jobs:
|
|
docker:
|
|
uses: hanzoai/.github/.github/workflows/docker-build.yml@main
|
|
with:
|
|
image: ghcr.io/hanzoai/visor
|
|
target: STANDARD
|
|
# amd64-only: DOKS has no arm64 droplets (no deploy target) and no arm64
|
|
# build runner is currently online, so a queued arm64 job would block the
|
|
# manifest/deploy jobs. Matches the cloud + kms callers. Re-add
|
|
# linux/arm64 when an arm64 target + runner exist.
|
|
platforms: linux/amd64
|
|
runner-amd64: '["hanzo-build-linux-amd64"]'
|
|
secrets: inherit
|