Repository navigation
task(owner): leave the fork network (Settings - Danger Zone), no API exists for this #161
Description
Parent: #158. Owner action — cannot be automated.
GitHub has no REST endpoint to leave a fork network [api: repos reference, 2026-10-03]. This is done in the web UI:
https://github.com/OKI-Mesh/CoreScope/settings → General → scroll to Danger Zone → Leave fork network
It is self-serve and does not require GitHub Support.
Preconditions
- The pre-detach snapshot child is complete and posted.
- The DIAGNOSE child has answered the irreversibility question.
- No PR is mid-merge.
What to expect
The confirmation dialog will state what is being severed. Record what it says, verbatim, in a comment here — it is the only description GitHub gives of the operation, and the next person doing this on another repo will want it.
Done when
gh api repos/OKI-Mesh/CoreScope -q .fork returns false, and the dialog text is recorded here.
Activity
diffwireauto commentedon Oct 3, 2026
Done — detached by the owner 2026-10-03
[verified: api 2026-10-03T03:05:17Z]forktruefalseparentKpa-clawbot/CoreScopeNONEsourceKpa-clawbot/CoreScopeNONEnetwork_count670Elapsed roughly 60 seconds from the click.
forkstayedtruefor the first minute, which is the documented asynchronous behaviour and not a failed detach — worth knowing for the next repo.Performed by the owner in the web UI.
Agentishumanon this one: no session can do it, since GitHub exposes no REST endpoint for leaving a fork network[verified: docs 2026-10-03].The preconditions recorded in #160 held: public, 109 MB against the 1 GB cap, zero child forks.
Full post-detach verification is in #162 — 34 of 34 checks. Nothing was lost: 124 issues, 33 PRs, the
Protect Mainruleset with its bypass actors, both self-hosted runners,ENABLE_STAGING_DEPLOY, labels, board link, stars and watchers all survived, andmasteris unchanged atff5e338f8c2bb612477e2a1bbb75040d0a9c567b.The Sync fork network button is gone. That was the point: no future one-click merge of upstream can undo the deletions #144 is making.
One thing this does not do, by design and accepted by the owner: commits pushed while CoreScope was a fork stay readable under
Kpa-clawbot/CoreScopeforever. Only commits pushed after the detach are private to us — proved both ways in #162.Not captured: the confirmation dialog text this issue asked for. The owner detached without recording it. Low value now that the operation is done and its behaviour is measured; left unrecorded rather than guessed at.
docs(#163): how we take upstream changes now the fork link is gone
docs(#163): how we take upstream changes now the fork link is gone