(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.
Nico --
threads / discuss / 37244
Is there a way to mark a branch as published?
Subject: Is there a way to mark a branch as published?
Dennis KaarsemakerRe: Is there a way to mark a branch as published?
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:
git branch -a --contains yourbranchnamehere | grep remotes/
That doesn't say anything about remotes you don't know about of course.
-- Dennis Kaarsemaker www.kaarsemaker.net
Re: Is there a way to mark a branch as published?
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.