disallowing push to currently checked-out branch

[Jeff King <peff@peff.net>]

On Sun, Feb 15, 2009 at 04:14:20PM -0800, david@lang.hm wrote:

>> Please, please, publicize that if there is somebody who is doing the same
>> as you (which I deem a dangerous workflow; I certainly do not use it
>> myself) that they will have to adjust their receive.denyCurrentBranch
>> variable.
>
> since this repository isn't use for anything other than publishing for  
> public access, what's so dangerous about it?
>
> what do you think that I should be doing instead?

What you are doing is not dangerous, because you are one of the clueful
users who understands that the repo is only for publishing, and has set
up a hook to (or is manually triggering) a checkout of the new contents.

It is the less clueful user who doesn't realize that his working tree
and index in the pushed-to repository contain totally bogus information
which can cause him to create bad commits or even lose work permanently.
Dealing with this is one of the most common FAQ's we see on the list.

So the proposal is about making you, the clueful user, set a config
option that promises you have a clue. Which is sad that this must impact
you, but unfortunately it is not a very good strategy to ask clueless
users to set a variable saying that they are so.

-Peff