Re: [RFC PATCH 0/4] deny push to current branch of non-bare repo

From: Kyle Moffett <kyle@moffetthome.net>
Date: Nov 13, 2008, 13:58 UTC
Message-ID: <f73f7ab80811130558h34cb1220q76ef5536e853151c@mail.gmail.com>
In-Reply-To: <7vhc6ci24o.fsf@gitster.siamese.dyndns.org>

On Thu, Nov 13, 2008 at 1:14 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 16 quoted lines

> Jeff King <peff@peff.net> writes:
>> And then the "push to current branch" problem is neatly solved: you have
>> no current branch.
>>
>> So:
>>
>>   $ git checkout new/branch/to/test^0
>>   $ make, configure, etc
>
> Exactly.
>
> I keep a handful pseudo worktrees around (created with git-new-workdir on
> top of a single repository) for quick patch test and build purposes.  I do
> not push into them but pushing into a non-bare repository and checking out
> the same branch twice in such a setup share exactly the same issue, and I
> keep their HEADs all detached for exactly the same reason.

I guess the issue comes down to a UI complication. It would very easy for me to tell somebody how to check out and test their branch in my testbed if I'm not around, except for that little bit of arcane syntax. Moreover, the consequences if they forget are really frustrating and hard to figure out. It's also very easy with a GUI to do the simple *rightclick branch, click "Checkout"*, but would be much harder to do the detached HEAD checkout correctly.

If it didn't involve reconfiguring a lot of other people's repositories, I might consider having them push to "refs/remotes/*". In theory that's actually much closer to what I'm doing anyways. That would force any checkouts to be bare, but it would require lots of git-foo on the pushing side. Perhaps some way to "git push" which asks the remote repository where it wants the stuff?

Alternatively, it might be possible to add ref attributes or a config option to force detached HEAD checkouts.

Cheers, Kyle Moffett