如何更新本地标记以匹配远程？

通过删除本地标记，然后执行 git 提取，我为回购修复了它。这带来了更新的标记。

是否有“正确”的方法来更新远程上可能已经更改的标记？这是一个简单的标记，没有签名或其他东西，用“ git 标记”创建

77865 次浏览
小开
最佳答案

Make sure you fetch all the tags (through git fetch --tags), to get all the tags and not just ones referencing commits reachable from the branch heads.

Those (fetched) tags are annotated ones (and usually not lightweight), and if you add deleted one on the local repo, they will just pop back after the fetch.

However, if you have deleted a lightweight one, then you need to recreate it locally: a lightweight tag isn't usually pushed or fetched to/from a remote repo.

Note that starting git 1.9/2.0 (Q1 2014), git fetch --tags will fetch everything (like git fetch), plus the tags. See "Does “ABC0” include “git fetch”?".

Again, fetch "everything" means annotated and lightweight (if those lightweight tags were previously pushed).

As noted below in biocyberman's answer, if you want to fetch tags from all remotes (not just the default remote named 'origin'), you need to add the --all option.

git fetch --tags --all
小开

What you have said is the right way and that is what the git tag manual recommends ( actually, it says, don't change the tags on the remote repo unless the world is coming to an end):

git tag -d X
git fetch origin tag X
小开

I don't think it's a bug. Though you shouldn't change tags, if one changes upstream, this will update the tag on your repo:

git fetch origin "+refs/tags/*:refs/tags/*"
小开

Previous to git 2.30, the right way seemed to be:

  git fetch origin --tags --force

You should avoid to have a branch with the same tag name, because the checkout prioritizes the branch and you can feel like the tag was not updated. Maybe git should have a warning in this case, something like:

You have updated a tag that differs now from a branch of the same name. The reference to "tagname" became ambiguous.

小开

In fact git fetch --tags is enough to let git overwrite lightweight and annotated tags by remote tags of either kind. You can consider it a documentation bug for not mentioning that.

Local tags with names which have no equivalent on the remote will be left alone with this command.

Tested with git version 2.7.4.

小开

In case one has multiple upstreams:

git --version
git version 2.11.1
git fetch --tags --all

without the --all option, I could not fetch the tags from the upstream whose name is not "upstream".

小开

Short cheat sheet with example below for tag XTAGX and commit ID 339f42b to whom, who are using tags only to mark specific commits for yourself (it might be okay to do re-tagging) and not for an opened to wide audience releases. Otherwise it is not good idea and @dannysauer already put a link with great explanation and use case.

remove locally: git tag -d XTAGX
remove on remote: git push -d origin XTAGX
create locally: git tag -a XTAGX -m "My XTAGX git tag" 339f42b
push to remote: git push origin --tags
list locally: git tags --list
list on remote: git ls-remote --tags origin
additional check to see tags in all history: git log --oneline

Good reference with explanations: https://stackoverflow.com/a/5480292/2957102


提交答案