On Sat, May 02, 2020 at 02:01:35PM -0700, Ben Denhartog wrote: > # set up the fork > git -C /tmp/b init > git -C /tmp/b remote add -f --no-tags upstream file:///tmp/a > ``` > > You'll see the 0.0.1 tag being fetched. You can delete it all you > want, set the `remote.upstream.tagopt = --no-tags`, etc -- it will > always be pulled. This is the opposite behavior I would expect based > on the available documentation and discussion around the tag in the > mailing list. I don't see that behavior. I get: $ git -C /tmp/b remote add -f --no-tags upstream file:///tmp/a Updating upstream remote: Enumerating objects: 3, done. remote: Counting objects: 100% (3/3), done. remote: Total 3 (delta 0), reused 0 (delta 0), pack-reused 0 Unpacking objects: 100% (3/3), 197 bytes | 197.00 KiB/s, done. From file:///tmp/a * [new branch] master -> upstream/master Is it possible you have some other config that might be conflicting (e.g., extra refspecs that ask to transfer tags)? What does "git config --list --show-origin" say? -Peff
