Detach a fork from its parent
A fork borrows its parent's objects through git alternates, and the forge shows how far it stands from that parent. When the parent is put away for good, the fork can stand alone.
- Archived parent. When a fork's parent is archived, the fork's page shows one quiet line, "forked from owner/name (archived)", in place of the Following card. There is no ahead/behind count, nothing to take, and no Propose upstream. The archived repository's forks page lists its forks by name, with no count against them.
- Detach. A repository admin opens Settings › Danger zone › Detach from parent. From an archived parent's quiet line it is the "detach from it" link. The card names the parent only to an admin who may still read it. The
repo.detachedevent carries the parent's id, never its name. The detach repacks the fork so it owns every object it borrowed (detachFork, the same step deleting a parent takes), drops the alternates link, then forgets the parent. The repack runs in the background, and the card says it is running and since when. If it fails, git's line stays on the card and nothing changes. There is no undo. - Terminal. On a fork's About card (
I), an admin pressesx. The terminal shows the plan, and the detach starts only after it is confirmed. Adetachrow shows the phase, as the card does. - MCP.
detach { repo }returns the plan: the parent, and whether the fork still borrows objects.detach { repo, dryRun: false }starts the detach, and needs an admin token. Calling it again shows thephaseuntil the fork has noparent. An agent is refused, as witharchive. - What it says. Every door (the confirm page, the Danger zone section, the terminal's plan, the MCP dry run) says the same two lines from
actions/detach_words.ts: the code and its history stay, with the branches, issues and pulls; updates from the parent and offers to it stop. There is no undo, but the severed repository can follow the upstream's address again: its admin opens Settings › Follow upstream (the Following card is on forks only, so it is not there). That follows by address, as for any repository; it does not restore the fork link. In the fork tree the severed repository's own row readssevered; its former parent's tree does not list it. - Receipt. When the detach lands, the repository's history gets a
repo.detachedrow: "severed a fork from its upstream: code and history kept, updates and offers stopped", with who and when. After confirming, the page's flash says the repack runs on its own and the history records it when it lands.