Enforcing repository management policies in your enterprise

About policies for repository management in your enterprise

You can enforce policies to control how members of your enterprise on GitHub Enterprise Cloud manage repositories. You can also allow organization owners to manage policies for repository management. For more information, see "Creating and managing repositories and "Organizations and teams."

Enforcing a policy for base repository permissions

Across all organizations owned by your enterprise, you can set a base repository permission level (none, read, write, or admin) for organization members, or allow owners to administer the setting on the organization level.

1. 在 GitHub.com 的右上角，单击你的个人资料照片，然后单击“你的企业”。

2. 在企业列表中，单击您想要查看的企业。

3. 在企业边栏中，单击 “策略”。

4. 在“ 策略”下，单击“存储库”。

5. Under "Base permissions", review the information about changing the setting. （可选）若要在更改设置之前查看企业帐户中所有组织的当前配置，请单击 查看组织的当前配置。

6. Under "Base permissions", use the drop-down menu and choose a policy.

Enforcing a policy for repository creation

Across all organizations owned by your enterprise, you can allow members to create repositories, restrict repository creation to organization owners, or allow owners to administer the setting on the organization level.

If you allow members to create repositories in your organizations, you can choose which types of repositories (public, private, and internal) that members can create.

If your enterprise uses Enterprise Managed Users, you can also prevent users from creating repositories owned by their user accounts.

内部存储库是企业帐户所拥有的组织中的所有新存储库的默认设置。 For more information about internal repositories, see "Creating an internal repository."

组织所有者始终可以创建任何类型的仓库，而外部协作者永远不能创建任何类型的仓库。 有关详细信息，请参阅“关于存储库”。

1. 在 GitHub.com 的右上角，单击你的个人资料照片，然后单击“你的企业”。

2. 在企业列表中，单击您想要查看的企业。

3. 在企业边栏中，单击 “策略”。

4. 在“ 策略”下，单击“存储库”。

5. Under "Repository creation", review the information about changing the setting. （可选）若要在更改设置之前查看企业帐户中所有组织的当前配置，请单击 查看组织的当前配置。

6. Under "Repository creation", select a policy.

   

7. 如果你选择“成员可创建存储库”，请选择一个或多个存储库类型。

8. Optionally, if your enterprise uses Enterprise Managed Users and you want to prevent enterprise members from creating repositories owned by their user accounts, select Block the creation of user namespace repositories.

Enforcing a policy for forking private or internal repositories

Across all organizations owned by your enterprise, you can allow people with access to a private or internal repository to fork the repository, never allow forking of private or internal repositories, or allow owners to administer the setting on the organization level.

People with admin permissions can set a more granular forking policy. For more information, see "Managing the forking policy for your organization."

1. 在 GitHub.com 的右上角，单击你的个人资料照片，然后单击“你的企业”。

2. 在企业列表中，单击您想要查看的企业。

3. 在企业边栏中，单击 “策略”。

4. 在“ 策略”下，单击“存储库”。

5. Under "Repository forking", review the information about changing the setting. （可选）若要在更改设置之前查看企业帐户中所有组织的当前配置，请单击 查看组织的当前配置。

6. Under "Repository forking", use the dropdown menu and choose a policy.

   

7. If forking is enabled, you can specify where users are allowed to fork repositories. Review the information about changing the setting and choose a policy.

   

Enforcing a policy for inviting outside collaborators to repositories

Across all organizations owned by your enterprise, you can allow members to invite outside collaborators to repositories, restrict outside collaborator invitations to organization owners, restrict outside collaborator invitations to enterprise owners, or allow organization owners to administer the setting on the organization level.

1. 在 GitHub.com 的右上角，单击你的个人资料照片，然后单击“你的企业”。

2. 在企业列表中，单击您想要查看的企业。

3. 在企业边栏中，单击 “策略”。

4. 在“ 策略”下，单击“存储库”。

5. Under "Repository outside collaborators", review the information about changing the setting. （可选）若要在更改设置之前查看企业帐户中所有组织的当前配置，请单击 查看组织的当前配置。

6. Under "Repository outside collaborators", use the drop-down menu and choose a policy.

   

Enforcing a policy for the default branch name

Across all organizations owned by your enterprise, you can set the default branch name for any new repositories that members create. You can choose to enforce that default branch name across all organizations or allow individual organizations to set a different one.

1. 在 GitHub.com 的右上角，单击你的个人资料照片，然后单击“你的企业”。

2. 在企业列表中，单击您想要查看的企业。

3. 在企业边栏中，单击 “策略”。

4. On the Repository policies tab, under "Default branch name", enter the default branch name that new repositories should use.

5. Optionally, to enforce the default branch name for all organizations in the enterprise, select Enforce across this enterprise.

6. Click Update.

Enforcing a policy for changes to repository visibility

Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.

If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "Setting a policy for repository creation."

1. 在 GitHub.com 的右上角，单击你的个人资料照片，然后单击“你的企业”。

2. 在企业列表中，单击您想要查看的企业。

3. 在企业边栏中，单击 “策略”。

4. 在“ 策略”下，单击“存储库”。

5. Under "Repository visibility change", review the information about changing the setting. （可选）若要在更改设置之前查看企业帐户中所有组织的当前配置，请单击 查看组织的当前配置。

6. Under "Repository visibility change", use the drop-down menu and choose a policy.

Enforcing a policy for repository deletion and transfer

Across all organizations owned by your enterprise, you can allow members with admin permissions to delete or transfer a repository, restrict repository deletion and transfers to organization owners, or allow owners to administer the setting on the organization level.

1. 在 GitHub.com 的右上角，单击你的个人资料照片，然后单击“你的企业”。

2. 在企业列表中，单击您想要查看的企业。

3. 在企业边栏中，单击 “策略”。

4. 在“ 策略”下，单击“存储库”。

5. Under "Repository deletion and transfer", review the information about changing the setting. （可选）若要在更改设置之前查看企业帐户中所有组织的当前配置，请单击 查看组织的当前配置。

6. 在“Repository deletion and transfer（仓库删除和转让）”下，使用下拉菜单选择策略。

Enforcing a policy for deleting issues

Across all organizations owned by your enterprise, you can allow members with admin access to delete issues in a repository, restrict issue deletion to organization owners, or allow owners to administer the setting on the organization level.

1. 在 GitHub.com 的右上角，单击你的个人资料照片，然后单击“你的企业”。

2. 在企业列表中，单击您想要查看的企业。

3. 在企业边栏中，单击 “策略”。

4. On the Repository policies tab, under "Repository issue deletion", review the information about changing the setting. （可选）若要在更改设置之前查看企业帐户中所有组织的当前配置，请单击 查看组织的当前配置。

5. Under "Repository issue deletion", use the drop-down menu and choose a policy.