Re: Keep reflogs for deleted (remote tracking) branches?

From: Tao Klerks <tao@klerks.biz>
Date: Mar 14, 2022, 08:09 UTC
Message-ID: <CAPMMpoiF_vH_wUNfH6QrhLJmq+5kVWe2h_W-QEcctfF=dMdFmg@mail.gmail.com>
In-Reply-To: <2aa11123-5456-b0f1-6c33-302924164e98@jeffhostetler.com>

On Tue, Mar 8, 2022 at 3:57 PM Jeff Hostetler <git@jeffhostetler.com> wrote:

Show 10 quoted lines

>
>
> On 3/8/22 6:27 AM, Tao Klerks wrote:
> >
> > I have a practical question in case I missed something.
> >
>
> Have you considered having each team member have their own
> private fork of the repo?  Then their branches are theirs
> alone and no one else needs to see or collide with them.

Yes, this is a scheme that I've certainly considered - it is the public norm after all, at least in open-source development.

In the case I'm describing, however, teams often prefer to work in communal spaces, seeing work appear and disappear in their group environment.

Of course most teams wish to be isolated from each other, and of course individuals want and have the option to work in isolation from their team for any given period of time - and by "isolation" I don't necessarily mean secret, but rather "not pushing refs into a space that others will automatically fetch".

The case I am describing is a specific subset of an ecosystem - the case where a team normally works in a communal central refspace.

Anyway, thanks - it looks like no-one considers git's behavior very surprising here, I guess I'll just implement a server-hook-based workaround.