Tags pointing to objects tracked from branch heads will be
+ automatically downloaded when you fetch from a remote
+ repository. However, tags that aren't reachable from branch heads
+ will be skipped. If you want to make sure all tags are always
+ included, you must include the --tags option.
+
+$ git fetch origin --tags +remote: Counting objects: 1832, done. +remote: Compressing objects: 100% (726/726), done. +remote: Total 1519 (delta 1000), reused 1202 (delta 764) +Receiving objects: 100% (1519/1519), 1.30 MiB | 1.21 MiB/s, done. +Resolving deltas: 100% (1000/1000), completed with 182 local objects. +From git://github.com:example-user/example-repo + * [new tag] v1.0 -> v1.0 + * [new tag] v1.1 -> v1.1 ++ +
If you just want a single tag, use
+ git fetch <remote> tag <tag-name>.
+
By default, tags are not included when you push to
+ a remote repository. In order to explicitly update these you must
+ include the --tags option when using git push.
+
+ In a nutshell you use git tag to mark a
+ commit or point in your repo as important. This also allows
+ you to refer to that commit with a more memorable reference
+ than a SHA.
+