Skip to content

Document how to detach a fork before making it private #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Codex wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Document how to detach a fork before making it private #3

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c43551
Initial plan
Codex Mar 2, 2026
3840134
docs: add fork detachment guidance
Codex Mar 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/advanced-usage/repository-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,3 +35,13 @@ Building containers with buildpacks currently results in a persistent `cache` di
```shell
dokku repo:purge-cache node-js-app
```

## Detaching a fork to make a repository private

GitHub requires forks to stay public. To make a forked repository private, first detach it from the upstream:

1. In **Settings → Danger Zone**, use **Leave fork network** (if available) to detach while retaining stars, issues, and pull requests.
2. If the UI option is unavailable, submit the [GitHub fork detach request form](https://support.github.com/request/fork) and wait for the repository to be disconnected.
3. As a last resort, mirror-push the fork to a new repository and delete the original fork—this severs the fork relationship but also drops issues and pull requests.

After detaching, change the repository visibility to **Private** in the repository settings.