Re: [git-users] how to protect my source while allowing a new developer to work
On Thu, Jun 6, 2013 at 3:42 PM, benoît person 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. Sam -- 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.
Re: [git-users] how to protect my source while allowing a new developer to work
use any git workflow http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows git is not centralized, so he cant mail you or something like that telling you to make a pull request.. (in github this is implemented very well) you have to become an integration manager 2013/6/6 Gergely Polonkai > Hello, > > git doesn't provide such thing by default. To achieve that, you should use > external software, like gitosis or gitolite. > > Best, > Gergely > On 7 Jun 2013 00:42, "benoît person" wrote: > >> 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 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. >> >> >> -- > 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.
Re: [git-users] how to protect my source while allowing a new developer to work
Hello, git doesn't provide such thing by default. To achieve that, you should use external software, like gitosis or gitolite. Best, Gergely On 7 Jun 2013 00:42, "benoît person" wrote: > 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 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. > > > -- 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.
Re: [git-users] how to protect my source while allowing a new developer to work
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 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.
