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

关于仓库可见性

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

本文内容

此文档对您有帮助吗?

帮助我们创建出色的文档!

所有 GitHub 文档都是开源的。看到错误或不清楚的内容了吗?提交拉取请求。

做出贡献

或, 了解如何参与。

关于仓库可见性

创建仓库时,您可以选择将仓库设为公共或私有仓库。 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, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to members of your enterprise. 更多信息请参阅“关于内部仓库”。

组织所有者始终有权访问其组织中创建的每个仓库。 更多信息请参阅“组织的仓库权限级别”。

拥有仓库管理员权限的人可更改现有仓库的可见性。 更多信息请参阅“设置仓库可见性”。

关于内部仓库

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

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. 有关内部资源的更多信息,请参阅 GitHub 的白皮书“内部资源简介”。

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

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

如果用户从

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

此文档对您有帮助吗?

帮助我们创建出色的文档!

所有 GitHub 文档都是开源的。看到错误或不清楚的内容了吗?提交拉取请求。

做出贡献

或, 了解如何参与。