coily assumes single-org coilysiren/* in several places (dispatch guard, create redirect) - accept canonical owners post org-split #162
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?
coily hardcodes the
coilysirenowner in several places. Post org-split (active repos now live undercoilyco-bridgeandcoilyco-flight-deck), these refuse or silently mishandle canonical-owner references. Tracking the audit + a shared fix here.Concrete: dispatch org guard
coily dispatch headlessrefuses any owner outsidecoilysiren/*:The
coilysiren/<repo>#Nalias form sometimes resolves (it worked forcoilysiren/agentic-os-kai#553), but a fully-qualified canonical URL is rejected outright. So the unambiguous reference form can't be dispatched.Other single-org sites (audit)
ops forgejo issue createsilently no-ops on a redirecting (moved) repo - POST gets 301'd to GET (a list), reads as HTTP 200 success, creates nothing. Already filed as coily #160 / agentic-os-kai issues/549. Same root: thecoilysiren/path redirects.apply-agentic-os-hookshad a hardcodedOWNER = "coilysiren"(fixed in agentic-os 7ac1f28 by driving off the on-disk set); worth grepping coily for the same pattern.Suggested fix
One shared owner-resolution helper used by every verb that takes a repo ref: a
KNOWN_ORGS = {coilysiren, coilyco-bridge, coilyco-flight-deck}allowlist plus thecoilysiren -> canonicalalias map, applied uniformly so dispatch, create, labels, etc. all accept either the alias or the canonical owner. Replace the literalcoilysiren/*guard in dispatch with that allowlist.Relates to the org-split repoint hub (agentic-os-kai issues/551).