Note difference on default behaviour on fetch/push on repo tags
This commit is contained in:
parent
690a441c25
commit
dbdd946cd9
@ -774,10 +774,11 @@ ab5ab4c added erlang
|
||||
* 17f4acf first commit
|
||||
</pre>
|
||||
|
||||
<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.
|
||||
<p>Tags pointing to objects tracked from branch heads will be
|
||||
automatically downloaded when you <code>fetch</code> from a remote
|
||||
repository. However, tags that aren't reachable from branch heads
|
||||
will be skipped. If you want to make sure <em>all</em> tags are <em>always</em>
|
||||
included, you must include the <code>--tags</code> option.
|
||||
</p>
|
||||
|
||||
<pre>
|
||||
@ -796,6 +797,11 @@ From git://github.com:example-user/example-repo
|
||||
<code>git fetch <remote> tag <tag-name></code>.
|
||||
</p>
|
||||
|
||||
<p>By default, tags are not included when you <code>push</code> to
|
||||
a remote repository. In order to explicitly update these you must
|
||||
include the <code>--tags</code> option when using <code>git push</code>.
|
||||
</p>
|
||||
|
||||
<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
|
||||
|
Loading…
Reference in New Issue
Block a user