zeekayandHanzo Dev cb5afefa7c rip(sync): hanzo.io is a pull-mirror, so this pushed against the current
The forge holds hanzo-apps/hanzo.io as a MIRROR on a 30m interval, pulling
from this very repo. A workflow that pushes refs INTO it is not a second
opinion, it is the same arrow reversed — mirror-sync would overwrite whatever
it landed at the next tick.

It never got that far. Its only run failed at "Push refs to git.hanzo.ai" on
2026-07-27: the repo had moved hanzoai -> hanzo-apps, the workflow builds its
remote from ${GITHUB_REPOSITORY}, and git.hanzo.ai/hanzoai/hanzo.io does not
exist. A red run nobody reads is worse than no workflow, because the repo
looks covered while carrying nothing.

Nothing replaces it. Mirror-sync was always the mechanism here.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-02 14:21:45 -07:00
2018-04-19 11:09:53 -05:00
2016-01-01 22:46:16 -06:00
2016-01-23 13:57:35 -06:00
2017-06-22 13:50:04 -07:00
2016-01-23 17:49:58 -06:00
2017-07-17 09:12:43 -05:00
2017-06-22 14:32:27 -07:00
2017-06-22 14:32:27 -07:00
2016-01-20 16:49:41 -06:00
2017-07-17 11:50:42 -05:00
S
Description
No description provided
Readme
56 MiB
Languages
CSS 50%
HTML 47.5%
JavaScript 2.5%