Keep deploy pushes canonical to Forgejo only #671

Open
opened 2026-07-28 20:59:36 +00:00 by coilyco-ops · 0 comments
Owner

Evidence

While landing coilyco-bridge/deploy#230, ward git push origin HEAD:main reported successful writes to both the canonical Forgejo remote and the GitHub mirror. The repository policy says canonical history lives on Forgejo and the GitHub mirror remains PR-gated.

Outcome

Host convergence gives the deploy checkout one canonical push destination on Forgejo. GitHub synchronization follows the intended PR-gated mirror path and cannot be updated as an incidental second push URL.

Acceptance

  • Identify the source that adds multiple origin push URLs to the deploy checkout.
  • Converge the canonical push URL to Forgejo only without changing fetch behavior unnecessarily.
  • Verify ward git push origin updates Forgejo and does not directly update GitHub.
  • Audit other managed checkouts for the same remote configuration drift.

The Ollama deployment landed successfully. This issue tracks only the remote-policy mismatch discovered during that landing.

## Evidence While landing `coilyco-bridge/deploy#230`, `ward git push origin HEAD:main` reported successful writes to both the canonical Forgejo remote and the GitHub mirror. The repository policy says canonical history lives on Forgejo and the GitHub mirror remains PR-gated. ## Outcome Host convergence gives the deploy checkout one canonical push destination on Forgejo. GitHub synchronization follows the intended PR-gated mirror path and cannot be updated as an incidental second push URL. ## Acceptance * Identify the source that adds multiple `origin` push URLs to the deploy checkout. * Converge the canonical push URL to Forgejo only without changing fetch behavior unnecessarily. * Verify `ward git push origin` updates Forgejo and does not directly update GitHub. * Audit other managed checkouts for the same remote configuration drift. The Ollama deployment landed successfully. This issue tracks only the remote-policy mismatch discovered during that landing.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/infrastructure#671
No description provided.