如何通过Github进行外包？
我正在与一家公司合作，该公司希望外包我们一个项目的新功能开发。我们有一个 github 帐户，我想知道如何为外包人员提供对该帐户上的项目存储库的限制访问权限。
有没有办法使用一组特定的凭据将存储库的提交和推送限制到特定分支？
我听说过分叉，但从未真正使用过它。这就是我要找的吗？
更新：
在这个行业工作了三年之后，现在回顾这个问题很有趣。我有很多东西要学。
另外，人们将这篇文章标记为偏离主题，但我不确定当我最初发布它时是否存在更合适的堆栈交换站点。
无论如何，正如人们指出的那样，让外包商分叉该项目是处理这种情况的正确方法。然后，他们会提出拉取请求，我可以审查并批准这些请求，而无需授予他们对我们帐户的完全访问权限。
I am working with a company that wants to outsource the development of new features on one of our projects. We have a github account and I am wondering how I can give the outsourcees restricted access to the project repo on that account.
Is there a way to limit commits and pushes on a repo to a specific branch with a specific set of credentials?
I've heard about forking but have never really used it. Is that what I'm looking for?
Update:
It's funny looking back on this question now after three more years working in the industry. I had a lot to learn.
Also, people are marking this post as off-topic, but I'm not sure that a more appropriate stack exchange site existed when I originally posted it.
Anyway, as people have pointed out, having the outsourcees fork the project would have been the correct way to handle this situation. They would then have made pull requests which I could have reviewed and approved without giving them full access to our account.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我想您可以分叉存储库，授予对其的访问权限，然后继续将更改拉入您的主存储库 - 在这种情况下，将分叉视为私有分支。
I suppose you could fork the repository, grant access to that, and then keep pulling the changes into your main one - think of a fork as a private branch in this case.
是的，分叉可以为你做到这一点。我认为，如果您没有在分布式环境中使用您的私有 Github 存储库工作的经验，那么明智的做法是评估您的开发团队（您将工作外包给他们）在使用 Github 作为解决方案方面的专业知识。分布式/虚拟团队。一般来说，如果他们是 Github 的新手，那么让他们从一开始就掌握窍门并把事情做好是非常困难的。
好吧，我发现我正在回复一个非常旧的线程，但如果情况仍然如此，我建议只让那些使用 Github 工作得足够好的开发人员。事实上，作为一家 IT 咨询公司的成员，我管理着一个定期这样做的开发团队，并且我了解开发人员在开始使用 Github 时面临的挑战，特别是因为 Github 提供的巨大灵活性。
Yes, forking does that for you. I think if you don't have experience working in a distributed environment, using your private Github repo, it would be wise to assess your team of developers (whom you're outsourcing the work to) for their expertise on usage of Github as a distributed/virtual team. Generally, if they are new to Github, it's really difficult to get them have a hang of it and get things right since the start.
Well, I see that I am responding to a very old thread but if it's still the case, I would recommend getting only the developers who have worked sufficiently well using Github. Indeed, as a member of an IT consulting company, I manage a team of devs that do it regularly and I understand the challenges developers face while starting to use Github, particularly because of enormous flexibility Github offers.