Deleting Forked Git Repositories
Itβs possible to delete forked Git repositories (tested on GitHub) using the following methods by the following actors:
- π€΅ Owner - GitHub code repository owner
- π§βπ€βπ§ Collaborator - GitHub user invited by the code Owner to collaborate in the repository
- π§βπ» Forker (non-Collaborator) - GitHub users with access to public GitHub repositories. They do not require a Collaborator invite by Owners
π Public Git Repository
-
No Collaborator invite
- π§βπ» Forker (non-Collaborator) forks a
"public"repo - π€΅ The Owner deletes the
publicrepo - β
Forker retains the forked
publicrepo
- π§βπ» Forker (non-Collaborator) forks a
-
With Collaborator invite
- π€΅ The Owner invites a π§βπ€βπ§ Collaborator to a
"public"repo - π§βπ€βπ§ The Collaborator forks the
publicrepo - π€΅ The Owner deletes the
publicrepo - β Forked
publicrepo disappears
- π€΅ The Owner invites a π§βπ€βπ§ Collaborator to a
π« Private Git Repository
- With Collaborator invite
- π€΅ Owner invites a π§βπ€βπ§ Collaborator to a
"private"repo - π§βπ€βπ§ Collaborator forks the
privaterepo - π€΅ Owner deletes the *
privaterepo - β Forked
privaterepo disappears
- π€΅ Owner invites a π§βπ€βπ§ Collaborator to a