在github文档和这里也找不到任何东西。但是我想知道是否有一个名为foo的私人存储库http://foo.github.com,只有一个人可以访问foo存储库本身。
我记得读过一些关于github页面总是公开的东西,但似乎再也找不到了。
令人惊讶的是,我似乎也找不到其他人问这个问题。
在github文档和这里也找不到任何东西。但是我想知道是否有一个名为foo的私人存储库http://foo.github.com,只有一个人可以访问foo存储库本身。
我记得读过一些关于github页面总是公开的东西,但似乎再也找不到了。
令人惊讶的是,我似乎也找不到其他人问这个问题。
当前回答
2021年1月:GitHub企业版现在可以实现(所以:github.com还没有)。 看到的:
GitHub页面的访问控制
GitHub Pages now gives you the option to limit access, making the site visible only to users with access to the repository that published the Page. With access control, you can use GitHub Pages to publish and share internal documentation and knowledge across your enterprise. As part of this release, we are introducing the following capabilities: Repo admins can select whether GitHub Pages sites are publicly visible or limited to users who have access to the repository. Both private and internal repositories support private visibility. With an internal repository, everyone in your enterprise will be able to view the Page with the same credentials they use to login to github.com Org admins can configure the visibility options that members will be able to select for their Page. For example, you can enforce that your members can only publish content privately. This feature is generally available today on GitHub Enterprise Cloud. To enable access control on Pages, navigate to your repository settings, and click the dropdown menu to toggle between public and private visibility for your site.
其他回答
2021年1月:GitHub企业版现在可以实现(所以:github.com还没有)。 看到的:
GitHub页面的访问控制
GitHub Pages now gives you the option to limit access, making the site visible only to users with access to the repository that published the Page. With access control, you can use GitHub Pages to publish and share internal documentation and knowledge across your enterprise. As part of this release, we are introducing the following capabilities: Repo admins can select whether GitHub Pages sites are publicly visible or limited to users who have access to the repository. Both private and internal repositories support private visibility. With an internal repository, everyone in your enterprise will be able to view the Page with the same credentials they use to login to github.com Org admins can configure the visibility options that members will be able to select for their Page. For example, you can enforce that your members can only publish content privately. This feature is generally available today on GitHub Enterprise Cloud. To enable access control on Pages, navigate to your repository settings, and click the dropdown menu to toggle between public and private visibility for your site.
github.com页面确实提到:
Github页面免费托管,通过我们的网站轻松发布,
没有提到访问控制。
GitHub页面帮助也没有提到任何ACL。 它们最好在gh-pages分支中进行管理,也可以在它们自己的子模块中进行管理。 但同样,在GitHub发布后,没有任何可视性限制。
许多答案都过时了(在微软收购之前/免费私人回购)。这篇文章是在宣布免费私人回购之后写的。
Github页面在个人免费私人回购中不可用,如回购设置所示:
2020年(现在最基本的计划是“团队”):
请注意
所有页面都是公开的,即使您进行了升级。升级只在私有回购上启用Pages功能,就像它启用其他功能一样。Pages功能是公开的静态虚拟主机。
如果您在私有回购上按下admin键,并向下滚动到关于页面的部分,它会写它将是公共的。我稍后会检查是否.htaccess control或类似的是可能的,但我不太希望它。
对于GitHub企业云客户来说,这终于成为可能:对GitHub页面的访问控制。
要在Pages上启用访问控制,请导航到存储库 设置,并单击下拉菜单在公共和 站点的私有可见性。