Mirror coilysiren/coilysiren into Forgejo (out-of-band, unblocks uniform-Forgejo container preclone) #352
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/infrastructure#352
Loading…
Add table
Add a link
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?
Why
The ward container preclone substrate list (
ward/cmd/ward/containerassets/preclone-repos.txt) assumes every entry is reachable via the same Forgejo token the container already configures. Eight of the nine repos are Forgejo-canonical. The ninth,coilysiren/coilysiren, is GitHub-only.A GitHub-only entry forces the container to either inject GitHub creds (widening its auth surface past Forgejo) or hit GitHub's anonymous rate limit (60 req/hr, shared across all containers on the egress IP). Either is a per-container tax.
What
Stand up a Forgejo mirror of
coilysiren/coilysirenso the preclone list is uniformly Forgejo and the container keeps its Forgejo-token-only auth posture. This is deliberately out of band from the preclone-list work - that list already assumes the mirror exists.Done when
coilysiren/coilysirenresolves onforgejo.coilysiren.me(pull mirror or push mirror, operator's call)./forgejo/api-tokencreds, no GitHub access.Refs
coilyco-flight-deck/ward/cmd/ward/containerassets/preclone-repos.txtinfrastructure/scripts/clone-coilysiren-repos.sh