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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 17, 2023, 21:09 UTC
Message-ID
<xmqqfs5mgs8v.fsf@gitster.g>
In-Reply-To
<CAGE71k3Ccm3hBrfNgXFqO9Zk0V9FkoskgD1ViJ6eSakxdBuqQQ@mail.gmail.com>
"Adam \"Sinus\" Skawiński"  <adam.skawinski@sinpi.net> writes:
> needed. I made it output some lines and exit with code 1, so it should
> abort after producing the output - and yet the pushes come through.

Did the output come back to your client side? "git push -v" should show.

If there is no need to update (i.e. after a successful push, you try to push the same thing), the hook would not even run, so you may need to rewind the "server" side while experimenting.

Previous: Junio C HamanoNext: Adam Sinus Skawiński
Message 3 of 9 in “receive.denyCurrentBranch=updateInstead won't update the repo”
  1. Adam Sinus SkawińskiJul 17, 2023
  2. Junio C HamanoJul 17, 2023
  3. Junio C HamanoJul 17, 2023
  4. Adam Sinus SkawińskiJul 17, 2023
  5. Adam Sinus SkawińskiJul 18, 2023
  6. Junio C HamanoJul 18, 2023
  7. Adam Sinus SkawińskiJul 18, 2023
  8. Junio C HamanoJul 18, 2023
  9. Adam Sinus SkawińskiJul 18, 2023

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.