![]() ![]() ![]() Only team permissions (not individual permissions) are inherited by private forks. For example, if the upstream repository is private and gives read/write access to a team, then the same team will have read/write access to any forks of the private upstream repository. This helps owners of private repositories maintain control over their code. Private forks inherit the permissions structure of the upstream repository. All other repositories are forked off of this new upstream and subsequent pull requests go to this new upstream repository. When you delete a public repository, one of the existing public forks is chosen to be the new upstream repository. When you delete a private repository, all of its private forks are also deleted. For more information, see " Managing the forking policy for your organization" and " Managing the forking policy for your repository." People with admin permissions to a private repository can disallow forking of that repository, and organization owners can disallow forking of any private repository in an organization. You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. If a team's access to a private repository is revoked or a team with access to a private repository is deleted, and team members do not have access to the repository through another team, private forks of the repository will be deleted. Local clones of the private repository are retained. If you remove a person’s access to a private repository, any of their forks of that private repository are deleted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |