我们经常发布文档更新,此页面的翻译可能仍在进行中。有关最新信息,请访问英文文档。如果此页面上的翻译有问题,请告诉我们
文章版本: Enterprise Server 2.20

关于仓库可见性

You can restrict who has access to a repository by choosing a repository's visibility: public, internal, or private.

本文内容

关于仓库可见性

When you create a repository, you can choose to make the repository public or private. If you're creating the repository in an organization, you can also choose to make the repository internal.

If 您的 GitHub Enterprise Server 实例 is not in private mode or behind a firewall, public repositories are accessible to everyone on the internet. Otherwise, public repositories are available to everyone using 您的 GitHub Enterprise Server 实例, including outside collaborators. Private repositories are only accessible to you and the people you share them with. Internal repositories are accessible to members of any organization on your instance. For more information, see "About internal repositories."

Organization owners always have access to every repository created in an organization. For more information, see "Repository permission levels for an organization."

People with admin permissions for a repository can change an existing repository's visibility. For more information, see "Setting repository visibility."

关于内部仓库

注:内部仓库可用于 GitHub Enterprise Cloud 和 GitHub Enterprise Server 2.20+。 更多信息请参阅“GitHub 的产品”。

您可以使用内部仓库充分利用实例中的“内部资源”。 实例上任何组织的成员可使用开源方法进行协作,而无需公开共享专有信息,即使禁用了私有模式。 For more information on innersource, see GitHub's whitepaper "An introduction to innersource."

All organization members have read permissions to the internal repository, but internal repositories are not visible to people who are not members of an organization, including outside collaborators on organization repositories. For more information, see "Repository permission levels for an organization."

If a user is removed from

all organizations on the instance, that user's forks of internal repositories are removed automatically.

问问别人

找不到要找的内容?

联系我们