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

Re: Private/public branches/repos workflow

From
SRSeth Robertson <in-gitvger@baka.org>
Date
May 5, 2011, 15:35 UTC
Message-ID
<201105051535.p45FZQDY019419@no.baka.org>
In-Reply-To
<BANLkTi=TLeePH0JDvnE0XPiCzXFxid9BWQ@mail.gmail.com>

In message <BANLkTi=TLeePH0JDvnE0XPiCzXFxid9BWQ@mail.gmail.com>, Jerome Martin writes:

    Is there any recommended workflow to achieve the result I am looking
    for ? How are other people doing it ?

Create an orphan branch. Commit what you want onto it. Push branch to a new repo as master.

git checkout <basesha> git checkout --orphan cleanmaster git add -A git commit -m "base of public release" (mkdir ../newrepo; cd ../newrepo; git init --bare) git remote add cleanremote ../newrepo git push cleanremote cleanmaster:master

You can then cherry pick/rebase from previous branches onto cleanmaster any subsequent commits that you want to keep history for.

Another approach might be to finesse a shallow clone to do what you want.

					-Seth Robertson
Previous: Jerome MartinNext: Jerome Martin
Message 2 of 8 in “Private/public branches/repos workflow”
  1. Jerome MartinMay 5, 2011
  2. Seth RobertsonMay 5, 2011
  3. Jerome MartinMay 5, 2011
  4. Junio C HamanoMay 5, 2011
  5. Jerome MartinMay 5, 2011
  6. Junio C HamanoMay 6, 2011
  7. Jerome MartinMay 6, 2011
  8. Jerome MartinMay 5, 2011

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.