作为拥有多个开发人员的组织访问客户的 Github 存储库的最佳方式
我将与一些同事一起更改客户的代码库。通常，在处理项目时，我们会在 Github 上为我们的组织创建一个存储库，并为每个用户设置权限。
但对于这个项目，我们将不得不使用客户拥有的存储库。我希望我们可以让他们将我们的组织添加为协作者，这样我们就一切就绪了，但似乎您无法添加组织，只能添加普通用户。
要求客户将每个开发人员添加为客户存储库中的单独协作者将非常混乱。允许我们的多个开发人员访问远程存储库的更好方法是什么？
最后的手段可能是让他们与一个开发人员共享它，该开发人员可以分叉该项目并允许其他人访问该分叉，在我们进行时在主存储库上创建拉取请求，但作为开发人员，每个人都可以直接访问所涉及的内容会随着时间而改变。
编辑： 这篇文章被评论为一种可能的解决方案，虽然问题非常严重类似的（虽然4岁了）没有给出真正的解决方案。
Together with some colleagues I'll be making changes to a client's codebase. Normally when working on projects we create a repo for our organization on Github and setup permissions on a per-user basis.
But for this project we will have to work with a repo owned by the client. I was hoping we could have them add our organization as a collaborator and we'd be all set, but it seems you can't add a organization, only regular users.
Asking the client to add every dev as a separate collaborator on the client's repo would be extremely messy. What would be a better way of allowing our multiple devs access to a remote repo?
A last resort might be to have them share it with a single dev who can fork the project and allows the rest access to this fork, creating pull requests on the main repo as we go, but direct access for everyone would be preferable as the devs involved will change over time.
edit:
This post was commented as a possible solution and while the question is very similar (though 4 years old) no real solution was given.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当客户拥有 GitHub enterprise 和配置了 SAML 和 SCIM 支持的身份提供商时，他们可以将您的团队添加为其 IdP 中的访客并同步到 GitHub。这样他们就可以从 IdP 中的另一个组织联合到您的团队中。
如果这不是一个选择，他们可以让您/一些团队成员成为存储库管理组的一部分。
分叉也可能是一种选择，但不支持通过拉取请求跨组织分叉私有存储库。
When the client has GitHub enterprise and an Identity Provider configured with SAML and SCIM support, they can add your team as a guest in their IdP and sync into GitHub. That way they could federate in your team from another organization in the IdP.
If that's not an option, they could make you/a few team members part of the admin group of the repository.
Forking may be an option too, but forking private repos across organizations with pull requests and all isn't supported.