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

Re: Is there a way to mark a branch as published?

From
NWNico Williams <nico@cryptonector.com>
Date
Aug 1, 2014, 19:17 UTC
Message-ID
<CAK3OfOgxngLhh7FjrBT9NcK=LhEH9TAz+18LAvXJtt_bV=96wA@mail.gmail.com>
In-Reply-To
<1406919490.3253.3.camel@spirit>
On Friday, August 1, 2014, Dennis Kaarsemaker <dennis@kaarsemaker.net> wrote:
Show 9 quoted lines
>
> On di, 2014-07-29 at 17:40 -0500, Nico Williams wrote:
> > (or all of a repo's branches)
> >
> > Teamware recorded whether it had any "children" and warned about
> > rebasing published contents.  Perhaps git could do the same.
>
> Git doesn't record this directly, but you can see which known remote
> branches contain the tip of a branch:

Yes, but that says nothing about whether they accept non-ff merge pushes, or should reject them, and it says nothing about whether they are intended to be seen as "published" in the sense of having stable history. (Teamware would mark repos as published when cloned, but that often meant needing to reset that flag [it wasn't a flag, but i'm eliding irrelevant details].)

Yes, non-fast-forward pushes can be rejected with a hook, but a flag that could be set with a git command would be more convenient.

Previous: Dennis Kaarsemaker
Message 3 of 3 in “Is there a way to mark a branch as published?”
  1. Nico WilliamsJul 29, 2014
  2. Dennis KaarsemakerAug 1, 2014
  3. Nico WilliamsAug 1, 2014

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.