与缺乏经验的成员一起进行 Git 工作流程
当有经验不足的开发人员加入团队时，您会建议什么工作流程？ 我一直在我的项目中使用 git，现在一个新的开发人员将加入，但他之前没有使用过任何版本控制。 项目驻留在 Github 上，我无法直接与他联系。 我们都在防火墙后面。
我应该在 github 上为他创建一个分支并将其合并以掌握我自己，还是在一天结束时向他索要补丁。
What would you suggest as a work flow when there is a inexperienced developer joins the team. I have been using git for my projects and now a new developer will join but he has not used any version control before. Project resides in Github and I have no way of pulling directly with him. We are both behind firewalls.
Should I create a branch for him on github and merge it to master my self or do I ask him for patches at the end of the day.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我没有太多使用 github（我确实使用它，但只是非常基本的东西），但我看到了“分叉这个项目”功能和“请求拉取”。
我想他可以分叉该项目并要求您从他的分叉（而不是从他的机器）中拉取。
这是假设 fork 将为他创建一个项目，他可以将他的更改推送到 github，然后你可以从他的 github 项目中拉取，然后将其推送到他从中拉取的主项目。
I haven't worked much with github (I do use it, but only the very basic stuff), but I've seen a "fork this project" feature, and a "request pull".
I suppose he can fork the project and request you to pull from his fork (instead of from his machine).
This is assuming that the fork will create a project for him, where he can push his changes to github, then you can pull from his github project, then push it to the main one, where he pulls from.
我真的很喜欢使用 git format-patch 将一组提交转换为邮件。 然后您可以邮寄更改并在另一端重新应用它们。 这还意味着您可以在邮件列表等上讨论更改。
对我来说，这是一种绝妙的工作方式。 您可以在同一流程中进行代码审查，并且由于电子邮件通常可以穿过防火墙，因此它们并不是什么大问题。 不过，让存储库成形是另一回事。
I really like using git format-patch to turn a set of commits into mails. Then you can mail the changes and reapply them in the other end. It also means you can discuss the changes on a mailing list etc.
For me, this is a brilliant way to work. You get code reviews in the same process and since email usually can go over firewalls, they are not that much of a problem. Getting the repository in shape is another game though.
这两种选择听起来都像是想法。 不过，让他将自己的东西推送到 github 将为您提供他作品的免费异地备份。
Both options sound like ideas. Letting him push his stuff to github will give you a free off-site backup of his work though.
让他纯粹在本地为自己的客户工作。 每当你想要从他的客户中撤出并合并到你的客户中并检查更改时。 只要你愿意，你就可以推向他的客户。
Let him work purely locally on his own client. Whenever you want you pull from his client merging into yours and reviewing the changes. Whenever you want you push into his client.