coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Configure Forgejo push mirrors to GitHub fleet-wide (retire manual mirror syncs) #309

New issue
Open
opened 2026-06-12 10:23:36 +00:00 by coilysiren · 0 comments
coilysiren commented 2026-06-12 10:23:36 +00:00
Owner
Copy link

The 2026-06-12 fleet mirror sync (agentic-os-kai#662) found GitHub mirrors stale or diverged on most repos, and several fell behind again within hours of being synced. Root cause: nothing pushes Forgejo main to GitHub automatically - mirrors only advance when a human or agent pushes by hand.

Forgejo has native push mirroring (repo settings -> repository -> mirror settings, or POST /repos/{owner}/{repo}/push_mirrors with a GitHub token). Proposal: an ansible role (or a script in infrastructure) that walks the catalog and ensures every Forgejo repo with a GitHub twin has a push mirror configured, interval ~8h. That retires manual mirror syncs entirely, leaving scripts/sync-github-mirrors.sh (agentic-os-kai) for divergence repair only.

Note the interaction with GitHub rulesets: push mirroring force-pushes, so repos with non_fast_forward rules (coily, otel-a2a-relay, session-lattice, cli-guard) need the mirror token in the ruleset bypass list or the rules relaxed.

The 2026-06-12 fleet mirror sync (agentic-os-kai#662) found GitHub mirrors stale or diverged on most repos, and several fell behind again within hours of being synced. Root cause: nothing pushes Forgejo main to GitHub automatically - mirrors only advance when a human or agent pushes by hand. Forgejo has native push mirroring (repo settings -> repository -> mirror settings, or POST /repos/{owner}/{repo}/push_mirrors with a GitHub token). Proposal: an ansible role (or a script in infrastructure) that walks the catalog and ensures every Forgejo repo with a GitHub twin has a push mirror configured, interval ~8h. That retires manual mirror syncs entirely, leaving scripts/sync-github-mirrors.sh (agentic-os-kai) for divergence repair only. Note the interaction with GitHub rulesets: push mirroring force-pushes, so repos with non_fast_forward rules (coily, otel-a2a-relay, session-lattice, cli-guard) need the mirror token in the ruleset bypass list or the rules relaxed.
coilyco-ops added
P3
 and removed
P1
 labels 2026-07-09 21:57:13 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#309
No description provided.