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

关于仓库可见性

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 that is owned by an enterprise account, you can also choose to make the repository internal.

Public repositories are accessible to everyone on the internet. Private repositories are only accessible to you and the people you share them with. Internal repositories are accessible to members of your enterprise account. 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+。 For more information, see GitHub's products."

You can use internal repositories to practice "innersource" within your enterprise account. Members of your enterprise account can collaborate using open source methodologies without sharing proprietary information publicly. For more information on innersource, see GitHub's whitepaper "An introduction to innersource."

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

内部仓库是企业帐户所拥有的组织中的所有新仓库的默认设置。

If a user is removed from

an enterprise account, that user's forks of internal repositories are removed automatically.

问问别人

找不到要找的内容?

联系我们