如何使用Github进行私有仓库访问控制?
对于美国存储库场景,我们需要探索如何使用 GitHub 或其他 Git 托管服务来实现我们的目标。
我们有一个私有存储库,可供一小群用户访问(读取)。我们需要为用户复制存储库作为组外的私有存储库。一两个用户可以通过用户私有存储库的任何推送来通知,并且也可以对该存储库进行读取访问。
对于第一个要求,我想我们可以创建一个组织的私有存储库,以便任何组成员都可以访问该私有存储库。
对于第二个要求,我不知道如何将私有存储库复制给组织外部的某人,并且复制的存储库也是私有的。
对于第三个要求,我想对于那些需要通知私有存储库并具有读取访问权限的人来说,需要一个新的组织。
我们没有 Git 托管来体验这些使用场景,但希望看看可行性。非常感谢您提前提供的意见。
With a repository usa scenario, we need to explore how to achieve our goal with GitHub or some other Git hosting service.
We have one private repository which is accessible (read) to a (small) group of users. We need to duplicate the repository for a user as a private repository outside of the group. And one or two users can be notified by any pushes of the user's private repository and have read access to the repository as well.
For the first requirement, I guess that we could create a private repository of an organization so that any group members can access the private repository.
For the second requirement, I don't know how to duplicate a private repository to someone outside of the organization and the duplicated repository is also private.
For the third requirement, I guess that a new organization is needed for those who needed to be notified to a private repository and have read access.
We don't have Git hosting to experience those use scenarios but want to see the feasibility. Thanks very much for your input in advance.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
Github 可以满足 1 & 2要求。您可以创建私有存储库,外部人员也可以使用临时个人访问令牌克隆该存储库。
访问 https://github.com/settings/tokens/new 生成密码令牌并确保定义正确的 该令牌的范围,以便外部人员不会获得额外的许可。克隆步骤的详细信息可以在此处找到。
Github can fullfill 1 & 2 requirement. You can create a private repo and outsider can also clone the repo by using a temporary Personal Access Token.
Visit https://github.com/settings/tokens/new to generate the password token and make sure you define the correct scope of that token so that the outsider would not gain extra permission. Detail of the cloning steps can be found here.
据我所知,我认为您可以克隆您的第一个私有存储库,然后推送到新的私有存储库。
from what i know, i think you could clone your first private repository and then you push to your new private repository.