On Thu, Jun 6, 2013 at 3:42 PM, benoît person <benoit.per...@gmail.com> wrote:
> From what I know, git does not support branch permissions. The best
> way to deal with that kind of permissions-thingy is to create two
> repos : a main repo and a fork for your new developer. He would only
> have permissions to pull from the main repo but could do
> "pull-request" to the main repo. That way you could review his work
> before merging it into the main one.
Above is the standard way, pull requests between repos, or mailed patch sets.
I want to add, though, that you are using a version control system, if
your new dev does a commit you don't like... you can roll it back.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.