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?

2. For the few of us who can push from local to authoritative, how do I 
configure my .gitconfig to normally push to the local repo? My code should 
be reviewed, just like everyone else's. 

Thoughts? Pointers to documentation is fine, I just don't know what to look 
for.

Leam

-- 
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.


Reply via email to