Select the repository or repositories you'd like to remove from the team.Ībove the list of repositories, use the drop-down menu, and click Remove from team. 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. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams. You can remove a team's access to a repository if the team has direct access to a repository. Optionally, to the right of the repository name, use the drop-down menu and choose a different permission level for the team. Type the name of a repository, then click Add repository to team. On the Teams tab, click the name of the team.Ībove the list of team members, click Repositories.Ībove the list of repositories, click Add repository. Under your organization name, click Teams. In the top right corner of, click your profile photo, then click Your organizations.
For more information, see " About teams."
If the team's access to the repository is inherited from a parent team, you must change the parent team's access to the repository. You can change a team's permission level if the team has direct access to a repository.
0 kommentar(er)
