Greater control over forks of your private repositories
Blog post from GitHub
GitHub has updated its policy regarding collaborator permissions on private repositories under personal accounts. Previously, when a collaborator's permissions were revoked, they retained their fork of the repository. Now, in line with the existing policy for organization-owned repositories, the collaborator's fork will be deleted upon permission removal. This change aims to provide users with greater control over access to their private code.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.