Re: receive.denyCurrentBranch=updateInstead won't update the repo

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 18, 2023, 22:28 UTC
Message-ID: <xmqqa5vsg8gp.fsf@gitster.g>
In-Reply-To: <CAGE71k3tMOtyFVrmGW33RuQ3GufJg8X6ORKCwHQgg6RmXbRCQA@mail.gmail.com>

"Adam \"Sinus\" Skawiński"  <adam.skawinski@sinpi.net> writes:

Show 7 quoted lines

> Correct me if I'm wrong, but I'm looking at receive-pack.c and can't
> grasp one thing.
>
> In receive-pack.c:1452-1453,
>> if (!invoked_hook)
>>   retval = push_to_deploy(sha1, &env, worktree->path);
> ... push_to_deploy is reached only if... hook didn't get invoked?

Correct. The hook is responsible for both DECIDING if it wants to touch/update the working tree, AND ACTUALLY UPDATING the working tree itself.

And the entire point of the "hook" is that its update does not have to be just "checkout the given commit's tree", for which using the default push-to-deply is sufficient. It is for those who want to do more.