hanzoai/tabs
2
0
Fork 0
mirror of https://github.com/hanzo-apps/tabs.git synced 2026-09-15 19:32:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

tabs: the CI file said this repo ships nothing, and it ships the site

Browse Source 
release.yml syncs the export to the tabs bucket on every push to main. The
header above claimed the opposite — 'published as a package rather than
deployed from this repo' — which reads as 'there is no lane here' and sends
the next reader looking for one.
This commit is contained in:
zooqueen
2026-08-11 10:18:33 -07:00
parent 4fd4a9dfc4
commit 47e6e3983d
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
hanzo.yml
+8 -2
View File
@@ -1,8 +1,14 @@
# Canonical CI/CD config for hanzoai/tabs — the one file both the hanzoai/ci
# reusable (.hanzo/workflows/cicd.yml) and platform.hanzo.ai read.
#
# @hanzo/tabs is a Next app that is published as a package rather than deployed
# from this repo, so no `images:` and no `deploy:`.
# Tabs IS deployed from this repo — `.hanzo/workflows/release.yml` syncs the
# static export to the `tabs` bucket on every push to main, and that is what
# tabs.hanzo.ai serves. There is no `images:` and no `deploy:` here because
# neither describes that: the server in front of the bucket is hanzoai/static,
# pinned in universe and released on its own cadence, so this repo builds no
# image and rolls out no workload. Read the absence as "nothing to build", not
# as "nothing ships" — it said the latter once, and cost an afternoon spent
# looking for a lane that was already there.
#
# The gate is typecheck plus the jest suite. That suite is deliberately narrow
# and says so in its own config — "pure logic only: the layout tree and the