Re: workflow with blessed, lieutenant, and developers

Assuming you actually want what you want:

Mihamina Rakotomandimby [off-list ref] writes:

1°) What command line do developers use to push to me but not to the
blessed (origin)?

For example:

  git remote add submission <your repository URL>

and then, submit with

  git push HEAD:submission/branch-name

2°) After they pushed to me, I have the choice to "approve" or "reject"
a commit: what is the keyword and git option for that?

Actually, you have the choice between "push" and "don't push", and you
can complement the later with "git branch -D" to delete the branch.

3°) I push the merge of approved commits to the blessed repository:
what keywords and git options?

What do you want that "git push" doesn't do?


Now, you may not really want this ;-). Here are some alternatives:

* Use a system like github/gitorious/giroco/gitolite, that allows you
  to manage a set of repositories with shared storage, on a single
  site. Take gitorious, for example. People would clone the blessed
  repository (like http://gitorious.org/project/repo.git) online
  (costs almost nothing thanks to shared storage). They get a remote
  repository like http://git.gitorious.org/~user/project/own-repo.git.
  Then get a local copy. They would push to
  http://git.gitorious.org/~user/project/own-repo.git, notify you of
  the changes (by email, or using gitorious itself), and you'd pull
  from them and push to the blessed repository. This way, each user
  has his own private local repository, and his submission repository.
  You avoid people messing their submission with each other.

* Look at code review tools like gerrit. I've never used them so I
  can't say much more.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/