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 AE 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."

Configuring the default visibility of new repositories

Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "About repositories."

If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "Setting a policy for repository creation."

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

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

3. 在 “策略” 下，单击“选项” 。

4. Under "Default repository visibility", use the drop-down menu and select a default visibility.

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 AE 的右上角，单击你的个人资料照片，然后单击“企业设置”。
2. 在企业边栏中，单击 “策略”。
3. 在“ 策略”下，单击“存储库”。
4. Under "Base permissions", review the information about changing the setting. （可选）若要在更改设置之前查看企业帐户中所有组织的当前配置，请单击 查看组织的当前配置。
5. 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.

For more information about internal repositories, see "Creating an internal repository."

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

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

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

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

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

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

   

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

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.

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

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

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

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

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

   

Enforcing a policy for inviting collaborators to repositories

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

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

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

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

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

5. Under "Repository invitations", 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 AE 的右上角，单击你的个人资料照片，然后单击“企业设置”。
2. 在企业边栏中，单击 “策略”。
3. On the Repository policies tab, under "Default branch name", enter the default branch name that new repositories should use.
4. Optionally, to enforce the default branch name for all organizations in the enterprise, select Enforce across this enterprise.
5. 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 AE 的右上角，单击你的个人资料照片，然后单击“企业设置”。
2. 在企业边栏中，单击 “策略”。
3. 在“ 策略”下，单击“存储库”。
4. Under "Repository visibility change", review the information about changing the setting. （可选）若要在更改设置之前查看企业帐户中所有组织的当前配置，请单击 查看组织的当前配置。
5. 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 AE 的右上角，单击你的个人资料照片，然后单击“企业设置”。

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

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

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

5. 在“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 AE 的右上角，单击你的个人资料照片，然后单击“企业设置”。

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

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

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

   

Enforcing a policy for Git push limits

To keep your repository size manageable and prevent performance issues, you can configure a file size limit for repositories in your enterprise.

By default, when you enforce repository upload limits, people cannot add or update files larger than 100 MB.

1. 在 GitHub AE 的右上角，单击你的个人资料照片，然后单击“企业设置”。
2. 在企业边栏中，单击 “策略”。
3. 在 “策略” 下，单击“选项” 。
4. Under "Repository upload limit", use the drop-down menu and click a maximum object size.
5. Optionally, to enforce a maximum upload limit for all repositories in your enterprise, select Enforce on all repositories

Configuring the merge conflict editor for pull requests between repositories

Requiring users to resolve merge conflicts locally on their computer can prevent people from inadvertently writing to an upstream repository from a fork.

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

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

3. 在 “策略” 下，单击“选项” 。

4. Under "Conflict editor for pull requests between repositories", use the drop-down menu, and click Disabled.

Configuring force pushes

Each repository inherits a default force push setting from the settings of the user account or organization that owns the repository. Each organization and user account inherits a default force push setting from the force push setting for the enterprise. If you change the force push setting for the enterprise, the policy applies to all repositories owned by any user or organization.

Blocking force pushes to all repositories

1. 在 GitHub AE 的右上角，单击你的个人资料照片，然后单击“企业设置”。
2. 在企业边栏中，单击 “策略”。
3. 在 “策略” 下，单击“选项” 。
4. Under "Force pushes", use the drop-down menu, and click Allow, Block or Block to the default branch.
5. Optionally, select Enforce on all repositories, which will override organization and repository level settings for force pushes.

Blocking force pushes to a specific repository

1. Sign in to your enterprise at http(s)://HOSTNAME/login.

2. 从 GitHub AE 上的管理帐户任意页面的右上角，单击 。

   

3. 如果你尚未在“站点管理员”页上，请在左上角单击“站点管理员”。

   

4. 在搜索字段中，键入存储库的名称，然后单击“搜索”。

5. 在搜索结果中，单击仓库名称。

6. 在页面的右上角，单击 “管理员”。

7. 在左侧栏中，单击“管理员”。

8. Select Block or Block to the default branch under Push and Pull.

Blocking force pushes to repositories owned by a user account or organization

Repositories inherit force push settings from the user account or organization to which they belong. User accounts and organizations in turn inherit their force push settings from the force push settings for the enterprise.

You can override the default inherited settings by configuring the settings for a user account or organization.

1. Sign in to your enterprise at http(s)://HOSTNAME/login.

2. 从 GitHub AE 上的管理帐户任意页面的右上角，单击 。

   

3. 如果你尚未在“站点管理员”页上，请在左上角单击“站点管理员”。

   

4. 在搜索字段中，键入用户或组织的名称，然后单击“搜索”。

5. 在搜索结果中，单击用户或组织的名称。

6. 在页面的右上角，单击 “管理员”。

7. 在左侧栏中，单击“管理员”。

8. Under "Repository default settings" in the "Force pushes" section, select

   • Block to block force pushes to all branches.
   • Block to the default branch to only block force pushes to the default branch.

9. Optionally, select Enforce on all repositories to override repository-specific settings. Note that this will not override an enterprise-wide policy.