Git workflow with an inexperienced member

Question

What would you suggest as a workflow when an inexperienced developer joins a team. I use git for my projects, and now the new developer will join, but before he did not use any version control. The project is located on Github, and I can not directly contact him. We are both behind the firewalls.

Should I create a branch for him on github and combine it to take control of myself or I will ask for his patches at the end of the day.

Answer 1

I did not work much with github (I use it, but only the simplest things), but I saw the function "fork this project" and "pull request".

I assume that he can fork out the project and ask you to pull it out of the plug (and not from his car).

This assumes that the plug will create a project for him in which he can push his changes to github, then you can pull it out of your github project, and then click on the main one, from where it draws.

Answer 2

I really like to use git format-patch to turn a set of commits into emails. You can then submit the changes and reapply them at the other end. It also means that you can discuss changes to the mailing list, etc.

For me, this is a brilliant way of working. You get code reviews in the same process, and since email can usually go through firewalls, they aren't that complicated. Getting the repository in the form is another game.

Answer 3

Both options sound like ideas. If you let him push his stuff to github, he will give you a free backup of his work.

Answer 4

Let him work exclusively locally with his client. Whenever you want you to pull from your client, merge with you and view the changes. Whenever you want you to put pressure on your client.