Fork 0

Tip about tags not coming down the aisle unless you call for them

Tags are so incidental they are not normally slurped with the
usual fetch or push commands. A little heads up.

Also adds a nutshell inline with the rest of the cards.
Soon Van 11 years ago
parent cfb6480f51
commit 690a441c25

@ -774,6 +774,35 @@ ab5ab4c added erlang
* 17f4acf first commit
<p>By default, tags are not included when you <code>push</code> to or
<code>fetch</code> from a remote repository. In order to explicitly
update these you must include the <code>--tags</code> option to transfer
all the tags on the repo.
<b>$ git fetch origin --tags</b>
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
<p>If you just want a single tag, use
<code>git fetch &lt;remote> tag &lt;tag-name></code>.
<p class="nutshell">
<b>In a nutshell</b> you use <code>git tag</code> 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.