File tree Expand file tree Collapse file tree 1 file changed +10
-4
lines changed Expand file tree Collapse file tree 1 file changed +10
-4
lines changed Original file line number Diff line number Diff line change @@ -774,10 +774,11 @@ <h2>
774
774
* 17f4acf first commit
775
775
</ pre >
776
776
777
- < p > By default, tags are not included when you < code > push</ code > to or
778
- < code > fetch</ code > from a remote repository. In order to explicitly
779
- update these you must include the < code > --tags</ code > option to transfer
780
- all the tags on the repo.
777
+ < p > Tags pointing to objects tracked from branch heads will be
778
+ automatically downloaded when you < code > fetch</ code > from a remote
779
+ repository. However, tags that aren't reachable from branch heads
780
+ will be skipped. If you want to make sure < em > all</ em > tags are < em > always</ em >
781
+ included, you must include the < code > --tags</ code > option.
781
782
</ p >
782
783
783
784
< pre >
@@ -796,6 +797,11 @@ <h2>
796
797
< code > git fetch <remote> tag <tag-name> </ code > .
797
798
</ p >
798
799
800
+ < p > By default, tags are not included when you < code > push</ code > to
801
+ a remote repository. In order to explicitly update these you must
802
+ include the < code > --tags</ code > option when using < code > git push</ code > .
803
+ </ p >
804
+
799
805
< p class ="nutshell ">
800
806
< b > In a nutshell</ b > you use < code > git tag</ code > to mark a
801
807
commit or point in your repo as important. This also allows
You can’t perform that action at this time.
0 commit comments