Greater control over forks of your private repositories
Previously, if you removed collaborator permissions from someone contributing to a private repository on your personal account, that person would retain their fork (if they had created one). Today, we’re…
Previously, if you removed collaborator permissions from someone contributing to a private repository on your personal account, that person would retain their fork (if they had created one).
Today, we’re changing that behavior: if you remove a collaborator’s permissions from one of your private repositories, their fork will be deleted, giving you greater control over access to your private code. This matches the behavior of organization-owned forks, which hasn’t changed.
Written by
Related posts

Code. Create. Commit. Welcome to dev/core
The new GitHub Shop collection is here. We’re celebrating you.

GitHub Availability Report: April 2025
In April, we experienced three incidents that resulted in degraded performance across GitHub services.

From MCP to multi-agents: The top 10 new open source AI projects on GitHub right now and why they matter
Get insights on the latest trends from GitHub experts while catching up on these exciting new projects.