Keep deploy pushes canonical to Forgejo only #671
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#671
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Evidence
While landing
coilyco-bridge/deploy#230,ward git push origin HEAD:mainreported 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
originpush URLs to the deploy checkout.ward git push originupdates Forgejo and does not directly update GitHub.The Ollama deployment landed successfully. This issue tracks only the remote-policy mismatch discovered during that landing.