Hi >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.
Benoit Person On 7 June 2013 00:33, Peter Kellner <pkellne...@gmail.com> wrote: > I've got a new developer who I'm concerned might hurt our git repository (by > checking into master for example) if we give him r/w access to our bitbucket > repo. I want him to be able to check in to his branch only and be able to > merge master changes to his branch, but I don't want him to be able to > commit to the master branch. > > Sorry if my question is obvious, I've just never had to do this before. > > Thanks, > > -- > 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 to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
