git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: workflow with blessed, lieutenant, and developers

From
JJJoshua Juran <jjuran@gmail.com>
Date
Aug 9, 2010, 07:42 UTC
Message-ID
<172AD488-0169-440A-89FB-DD78584D244A@gmail.com>
In-Reply-To
<20100809092152.5f32646a@packard.rktmb.org>
On Aug 8, 2010, at 11:21 PM, Mihamina Rakotomandimby wrote:
> I would like to setup a similar thing but with
> - Only one lieutenant (me)

In Linux terminology, you would be the benevolent dictator, not the lieutenant. The lieutenants are those you trust to submit good patches.

> - A blessed repository where I am the only one to push to
Okay, though I might use the term 'official'.
> - Developers who push to me (the lieutenant)

Developers shouldn't push directly into your working repo. If you don't want to use pull requests (where a developer tells you when a branch is ready for you to pull into your own repo) then you can have a centralized bare Git repository for them to push to. Either they will push completed branches which you then merge into mainline (which is essentially the same as the pull request model, except the developers are sharing a repo for this purpose), or the developers themselves will do the merging in the developer repo, which you then pull into your working repo, and after vetting it push to the offical repo.

Show 10 quoted lines
> Developers pull/clone from the blessed repository.
> I initially clone from the blessed repository.
>
> 1°) What command line do developers use to push to me but not to the
> blessed (origin)?
> 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?
> 3°) I push the merge of approved commits to the blessed repository:
> what keywords and git options?

If you're going to manage a project, you need to spend enough time learning how Git works that you can answer these questions yourself. There are multiple good resources online. I suggest starting with a tutorial, and then experimenting to see what works and what doesn't before you actually try to start working for real. Along the way you'll find Google very helpful.

Josh
Previous: Mihamina RakotomandimbyNext: Matthieu Moy
Message 2 of 5 in “workflow with blessed, lieutenant, and developers”
  1. Mihamina RakotomandimbyAug 9, 2010
  2. Joshua JuranAug 9, 2010
  3. Matthieu MoyAug 9, 2010
  4. Jared HanceAug 9, 2010
  5. Enrico WeigeltAug 13, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.