Hi, we have noticed a change in behaviour with commit 3f763ddf28d28fe63963991513c8db4045eabadc. Here’s the steps to reproduce: mkdir git-test-dir cd git-test-dir git init --bare git remote add origin -- https://github.com/golang/go git -c protocol.version=2 fetch -f --depth=1 origin 16afa6a740fac7442e94dcd2ec5ea4a4853e45dc:refs/dummy git -c log.showsignature=false log --no-decorate -n1 --format="format:%H %ct %D" 16afa6a740fac7442e94dcd2ec5ea4a4853e45dc -- # Expected: # 16afa6a740fac7442e94dcd2ec5ea4a4853e45dc 1734108730 grafted, tag: go1.24rc1, refs/dummy # Tags are not fetch when using 2.48.1: # 16afa6a740fac7442e94dcd2ec5ea4a4853e45dc 1734108730 grafted --- git bisect revealed 3f763ddf28d28fe63963991513c8db4045eabadc as the culprit: commit 3f763ddf28d28fe63963991513c8db4045eabadc Author: Bence Ferdinandy Date: Fri Nov 22 13:28:50 2024 +0100 fetch: set remote/HEAD if it does not exist When cloning a repository remote/HEAD is created, but when the user creates a repository with git init, and later adds a remote, remote/HEAD is only created if the user explicitly runs a variant of "remote set-head". Attempt to set remote/HEAD during fetch, if the user does not have it already set. Silently ignore any errors. Signed-off-by: Bence Ferdinandy bence@xxxxxxxxxxxxxx Signed-off-by: Junio C Hamano gitster@xxxxxxxxx Is this intended? This was initially reported under https://github.com/zopencommunity/gitport/issues/146.
