On Wed, Jul 31, 2013 at 08:22:10AM -0700, leam hall wrote:
> I'm trying to design a workflow for our team and could use some advice. My 
> git-fu is young. 
> We have  a remote repo that will store the authoritative code. That will be 
> pulled to a server local repo where the team has access. Each person will 
> clone the local repo into their home directory, edit files, and then push 
> to the local repo. Somehow we will trigger code review and acks, and then 
> someone will push from the local repo to the authoritative repo. 
> What I need help understanding is:
> 1. How to prevent code being pushed from local repo to authoritative
>    until it is reviewed? Is this a process issue or does git have a
>    way to enforce it?

It is a process issue external to git, but I think this particular use
case is exactly what [gerrit][1] addresses.


[1]: https://code.google.com/p/gerrit/

Magnus Therning                      OpenPGP: 0xAB4DFBA4 
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe               http://therning.org/magnus

Perl is another example of filling a tiny, short-term need, and then
being a real problem in the longer term.
     -- Alan Kay

Attachment: pgp77Nvcw3HQT.pgp
Description: PGP signature

Reply via email to