Setting it to -tags will fetch every tag from remote, even if they are not reachable from remote branch heads. git tag v1.0 v2. So you can try the remote.tagOpt config option: git config (-global) remote.tagOpt -tags Conclusion List Local Git Tags In order to list Git tags, you have to use the git tag command with no arguments. Request that all tags be fetched from the remote in addition to whatever else is being fetched.
See " Does “ git fetch -tags” include “ git fetch”?". Note that starting git 1.9/2.0 (Q1 2014), git fetch -tags will fetch everything (like git fetch), plus the tags. So if your tags are reacheable from the branches you are fetching, you don't have to include -tags by default.Ĭonsidering the large history of some repos (including the linux one), always wanting to fetch all tags might lead to tag list cluttering (a list of tag pollutted by hundreds of not-needed tags). The git fetch command shows the progression of the central history. git fetch -all -tags Fetching origin From git-repository 98a14be.7a9ad7f master -> origin/master new tag v1.0 -> v1.0 Let’s say for example that you have a tag named v1.0 that you want to check out in a branch named release. Both git fetch and git pull are used for downloading the content from the remote repository.
#GIT FETCH ALL TAGS UPDATE#
The former will fetch all tags, but won't update the branch heads. To fetch tags from your remote repository, use git fetch with the all and the tags options.
The latter will update branch heads, and will actually fetch tags reachable from those updated branches.
Fetching tags has a different effect than fetching commits ( git fetch), as explained in " Does “git fetch -tags” include “git fetch”?".
0 kommentar(er)
