git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: receive.denyCurrentBranch that allows pushing data, just not changing branch

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 25, 2019, 23:39 UTC
Message-ID
<875zpyf6ip.fsf@evledraar.gmail.com>
In-Reply-To
<CA+49okox4CfSWgQrdAYrM=R3ZNThWgkEY9RZtDzOMxAVs5b7Dw@mail.gmail.com>
On Sat, May 25 2019, Shawn Landden wrote:
> It would be nice if when pushing to a checked out repo you could get
> up git to still push the commits, just not update the branch's HEAD.

How would this proposed feature differ from what receive.denyCurrentBranch=false does now?

You have a commit X in a non-bare repo. Your checkout is checked-out to X, your index has X's content in it, and the branch reference is at X.

Now you push Y to the branch reference, what would you like to have happen to the checkout & index at this point?

Previous: Shawn Landden
Message 2 of 2 in “receive.denyCurrentBranch that allows pushing data, just not changing branch”
  1. Shawn LanddenMay 25, 2019
  2. Ævar Arnfjörð BjarmasonMay 25, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.