From: "Adam \"Sinus\" Skawiński" <adam.skawinski@sinpi.net>
To: git@vger.kernel.org
Subject: receive.denyCurrentBranch=updateInstead won't update the repo
Date: Mon, 17 Jul 2023 22:26:26 +0200 [thread overview]
Message-ID: <CAGE71k3Ccm3hBrfNgXFqO9Zk0V9FkoskgD1ViJ6eSakxdBuqQQ@mail.gmail.com> (raw)
I'm using Git to push-to-checkout a website.
The receive.denyCurrentBranch=updateInstead option (set on the server
repo), according to the docs, should allow the push and do a checkout
on the worktree if it's clean, or just refuse the push if the worktree
isn't clean. Instead, for me it allows the push, but doesn't update
the worktree - I have to `git checkout -f` on the remote shell after
each push, even though the worktree is clean.
Note: The `push-to-checkout` hook doesn't seem to run, either, even
though it's in the .git/hooks/push-to-checkout file, with +x rights as
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.
Other hooks, like `update`, work fine and can abort if they exit 1.
Setup:
My client is 2.31.0.windows.1 (TortoiseGit)
Server’s git is 2.39.1.
My remote is set as ssh://user@hostname.com/path.
Please advise what I can do to investigate further.
--
Adam "Sinus" Skawiński
next reply other threads:[~2023-07-17 20:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 20:26 Adam "Sinus" Skawiński [this message]
2023-07-17 20:52 ` receive.denyCurrentBranch=updateInstead won't update the repo Junio C Hamano
2023-07-17 21:09 ` Junio C Hamano
[not found] ` <CAGE71k2bdy2aYy7speu=OOStopgjzVNOPQ_-V-63aCURLibFWw@mail.gmail.com>
2023-07-17 22:26 ` Adam "Sinus" Skawiński
2023-07-18 22:20 ` Adam "Sinus" Skawiński
2023-07-18 22:28 ` Junio C Hamano
2023-07-18 22:49 ` Adam "Sinus" Skawiński
2023-07-18 23:03 ` Junio C Hamano
2023-07-18 23:29 ` Adam "Sinus" Skawiński
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGE71k3Ccm3hBrfNgXFqO9Zk0V9FkoskgD1ViJ6eSakxdBuqQQ@mail.gmail.com \
--to=adam.skawinski@sinpi.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).