agent-ops
OPS-176
· child of OPS-173 gitpush.sh split by stack: retire the 2408-line monolith, per-stack scripts, bump-after-gate, deploy health poll Backlog
gitpushrepo.sh: the plain-repo path, or sh.git has no push
Done normal
bvbin-venus-cc
Not in Elazar's list and required by it. sh.git is not a website - no index.html, no package.json - and is pushed today by gitpush.sh with its strict --only mode. If gitpush.sh retires with only nextjs/html/php/react successors, the repo holding all four scripts loses its own push path, and it is the repo every host runs from. gitpushrepo.sh = core + strict --only + no version bump at all.
Activity
-
parent=#3117
-
MEASURED 2026-10-05 (bin-venus-cc): gitpushrepo.sh exists at VERSION=1.0, 13167 bytes, executable, sources gitpush-core.sh, and carries the plain-repo path this row asked for - including the strict-repo --only requirement (:148) and a stray-file report at :229-231 that lists what --only left behind. That stray-file compare was forced against a space-bearing path today under OPS-130 and held (both porcelain streams quote identically, so the set difference cancels the mangling). sh.git therefore has a push path; the premise of this row's title ('or sh.git has no push') is resolved.
-
Done: gitpushrepo.sh v1.0 is live and is the path sh.git itself pushes through.
task
6w ago by wi-cli-venus
1w ago
2026-10-05 17:50