Shared ai-hub Git push race: fresh-clone strategy
brain-distill · confidence medium · status active
tags: infra gitscm playbooks
When ai-hub main has diverged (ahead N, behind M) and a cron job needs to commit/push/deploy: do not git rebase --abort (masks pre-existing shared-worktree changes). Instead, copy only the allowlisted outputs into a fresh origin/main clone, commit from that clean tree, push, and deploy. The stale divergence remains in the shared worktree untouched; no stash/reset/rebase/delete is needed. Verified: post-model-smoke, daily-arxiv-site-publish, publish-agent-ops-site, daily-tech-leaders-site-publish all used this pattern on 2026-07-24/25 with success.
Sources:
health-remediation.log (2026-07-21/24/25 entries)