| blob | 2db82d04549fef958ede10151710e1f2eed0d22e |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 git-push(1) Manual Page
407 </h1>
410 <p>git-push -
411 Update remote refs along with associated objects
412 </p>
413 </div>
414 </div>
418 <div class="verseblock-content"><em>git push</em> [--all | --mirror | --tags] [-n | --dry-run] [--receive-pack=<git-receive-pack>]
422 </div></div>
423 </div>
427 necessary to complete the given refs.</p></div>
431 </div>
437 </dt>
438 <dd>
439 <p>
440 The "remote" repository that is destination of a push
441 operation. This parameter can be either a URL
444 </p>
445 </dd>
448 </dt>
449 <dd>
450 <p>
455 in the remote repository is to be updated.
456 </p>
457 <div class="paragraph"><p>The <src> is often the name of the branch you would want to push, but
460 <div class="paragraph"><p>The <dst> tells which ref on the remote side is updated with this
461 push. Arbitrary expressions cannot be used here, an actual ref must
463 updated.</p></div>
464 <div class="paragraph"><p>The object referenced by <src> is used to update the <dst> reference
465 on the remote side, but by default this is only allowed if the
469 EXAMPLES below for details.</p></div>
470 <div class="paragraph"><p><tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>.</p></div>
471 <div class="paragraph"><p>Pushing an empty <src> allows you to delete the <dst> ref from
472 the remote repository.</p></div>
473 <div class="paragraph"><p>The special refspec <tt>:</tt> (or <tt>+:</tt> to allow non-fast-forward updates)
474 directs git to push "matching" branches: for every branch that exists on
475 the local side, the remote side is updated if a branch of the same name
476 already exists on the remote side. This is the default operation mode
477 if no explicit refspec is found (that is neither on the command line
478 nor in any Push line of the corresponding remotes file---see below).</p></div>
479 </dd>
481 --all
482 </dt>
483 <dd>
484 <p>
485 Instead of naming each ref to push, specifies that all
487 </p>
488 </dd>
490 --mirror
491 </dt>
492 <dd>
493 <p>
494 Instead of naming each ref to push, specifies that all
497 be mirrored to the remote repository. Newly created local
498 refs will be pushed to the remote end, locally updated refs
499 will be force updated on the remote end, and deleted refs
500 will be removed from the remote end. This is the default
502 set.
503 </p>
504 </dd>
506 -n
507 </dt>
509 --dry-run
510 </dt>
511 <dd>
512 <p>
513 Do everything except actually send the updates.
514 </p>
515 </dd>
517 --porcelain
518 </dt>
519 <dd>
520 <p>
521 Produce machine-readable output. The output status line for each ref
522 will be tab-separated and sent to stdout instead of stderr. The full
523 symbolic names of the refs will be given.
524 </p>
525 </dd>
527 --delete
528 </dt>
529 <dd>
530 <p>
531 All listed refs are deleted from the remote repository. This is
532 the same as prefixing all refs with a colon.
533 </p>
534 </dd>
536 --tags
537 </dt>
538 <dd>
539 <p>
541 addition to refspecs explicitly listed on the command
542 line.
543 </p>
544 </dd>
547 </dt>
550 </dt>
551 <dd>
552 <p>
554 end. Sometimes useful when pushing to a remote
555 repository over ssh, and you do not have the program in
556 a directory on the default $PATH.
557 </p>
558 </dd>
560 -f
561 </dt>
563 --force
564 </dt>
565 <dd>
566 <p>
567 Usually, the command refuses to update a remote ref that is
568 not an ancestor of the local ref used to overwrite it.
569 This flag disables the check. This can cause the
570 remote repository to lose commits; use it with care.
571 </p>
572 </dd>
575 </dt>
576 <dd>
577 <p>
580 remote name from the current branch: If it tracks a remote
581 branch, then that remote repository is pushed to. Otherwise,
582 the name "origin" is used. For this latter case, this option
583 can be used to override the name "origin". In other words,
584 the difference between these two commands
585 </p>
590 </div></div>
592 only if the current branch does not track a remote branch. This is
594 </dd>
596 -u
597 </dt>
599 --set-upstream
600 </dt>
601 <dd>
602 <p>
603 For every branch that is up to date or successfully pushed, add
604 upstream (tracking) reference, used by argument-less
607 </p>
608 </dd>
610 --thin
611 </dt>
613 --no-thin
614 </dt>
615 <dd>
616 <p>
618 significantly reduces the amount of sent data when the sender and
619 receiver share many of the same objects in common. The default is
620 --thin.
621 </p>
622 </dd>
624 -q
625 </dt>
627 --quiet
628 </dt>
629 <dd>
630 <p>
631 Suppress all output, including the listing of updated refs,
632 unless an error occurs. Progress is not reported to the standard
633 error stream.
634 </p>
635 </dd>
637 -v
638 </dt>
640 --verbose
641 </dt>
642 <dd>
643 <p>
644 Run verbosely.
645 </p>
646 </dd>
648 --progress
649 </dt>
650 <dd>
651 <p>
652 Progress status is reported on the standard error stream
653 by default when it is attached to a terminal, unless -q
654 is specified. This flag forces progress status even if the
655 standard error stream is not directed to a terminal.
656 </p>
657 </dd>
658 </dl></div>
659 </div>
662 <div class="paragraph"><p>In general, URLs contain information about the transport protocol, the
663 address of the remote server, and the path to the repository.
664 Depending on the transport protocol, some of this information may be
665 absent.</p></div>
667 protocols. The following syntaxes may be used with them:</p></div>
669 <li>
670 <p>
672 </p>
673 </li>
674 <li>
675 <p>
677 </p>
678 </li>
679 <li>
680 <p>
682 </p>
683 </li>
684 <li>
685 <p>
687 </p>
688 </li>
689 <li>
690 <p>
691 rsync://host.xz/path/to/repo.git/
692 </p>
693 </li>
694 </ul></div>
695 <div class="paragraph"><p>An alternative scp-like syntax may also be used with the ssh protocol:</p></div>
697 <li>
698 <p>
700 </p>
701 </li>
702 </ul></div>
703 <div class="paragraph"><p>The ssh and git protocols additionally support ~username expansion:</p></div>
705 <li>
706 <p>
708 </p>
709 </li>
710 <li>
711 <p>
713 </p>
714 </li>
715 <li>
716 <p>
718 </p>
719 </li>
720 </ul></div>
722 syntaxes may be used:</p></div>
724 <li>
725 <p>
726 /path/to/repo.git/
727 </p>
728 </li>
729 <li>
730 <p>
732 </p>
733 </li>
734 </ul></div>
737 details.</p></div>
738 <div class="paragraph"><p>When git doesn’t know how to handle a certain transport protocol, it
740 exists. To explicitly request a remote helper, the following syntax
741 may be used:</p></div>
743 <li>
744 <p>
746 </p>
747 </li>
748 </ul></div>
749 <div class="paragraph"><p>where <address> may be a path, a server and path, or an arbitrary
750 URL-like string recognized by the specific remote helper being
752 <div class="paragraph"><p>If there are a large number of similarly-named remote repositories and
753 you want to use a different format for them (such that the URLs you
754 use will be rewritten into URLs that work), you can create a
755 configuration section of the form:</p></div>
760 </div></div>
765 insteadOf = host.xz:/path/to/
766 insteadOf = work:</tt></pre>
767 </div></div>
768 <div class="paragraph"><p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
771 configuration section of the form:</p></div>
776 </div></div>
781 pushInsteadOf = git://example.org/</tt></pre>
782 </div></div>
784 "ssh://example.org/path/to/repo.git" for pushes, but pulls will still
785 use the original URL.</p></div>
786 </div>
792 <li>
793 <p>
795 </p>
796 </li>
797 <li>
798 <p>
800 </p>
801 </li>
802 <li>
803 <p>
805 </p>
806 </li>
807 </ul></div>
809 because they each contain a refspec which git will use by default.</p></div>
810 <h3 id="_named_remote_in_configuration_file">Named remote in configuration file</h3><div style="clear:left"></div>
811 <div class="paragraph"><p>You can choose to provide the name of a remote which you had previously
812 configured using <a href="git-remote.html">git-remote(1)</a>, <a href="git-config.html">git-config(1)</a>
814 this remote will be used to access the repository. The refspec
815 of this remote will be used by default when you do
816 not provide a refspec on the command line. The entry in the
817 config file would appear like this:</p></div>
825 </div></div>
826 <div class="paragraph"><p>The <tt><pushurl></tt> is used for pushes only. It is optional and defaults
828 <h3 id="_named_file_in_tt_git_dir_remotes_tt">Named file in <tt>$GIT_DIR/remotes</tt></h3><div style="clear:left"></div>
831 in this file will be used to access the repository. The refspec
832 in this file will be used as default when you do not
833 provide a refspec on the command line. This file should have the
834 following format:</p></div>
837 <pre><tt> URL: one of the above URL format
840 </div></div>
844 be specified for additional branch mappings.</p></div>
845 <h3 id="_named_file_in_tt_git_dir_branches_tt">Named file in <tt>$GIT_DIR/branches</tt></h3><div style="clear:left"></div>
848 The URL in this file will be used to access the repository.
849 This file should have the following format:</p></div>
853 </div></div>
854 <div class="paragraph"><p><tt><url></tt> is required; <tt>#<head></tt> is optional.</p></div>
856 refspecs, if you don’t provide one on the command line.
863 </div></div>
868 </div></div>
869 </div>
873 section describes the output when pushing over the git protocol (either
874 locally or via ssh).</p></div>
876 representing the status of a single ref. Each line is of the form:</p></div>
879 <pre><tt> <flag> <summary> <from> -> <to> (<reason>)</tt></pre>
880 </div></div>
881 <div class="paragraph"><p>If --porcelain is used, then each line of the output is of the form:</p></div>
884 <pre><tt> <flag> \t <from>:<to> \t <summary> (<reason>)</tt></pre>
885 </div></div>
886 <div class="paragraph"><p>The status of up-to-date refs is shown only if --porcelain or --verbose
887 option is used.</p></div>
890 flag
891 </dt>
892 <dd>
893 <p>
894 A single character indicating the status of the ref:
895 </p>
898 (space)
899 </dt>
900 <dd>
901 <p>
902 for a successfully pushed fast-forward;
903 </p>
904 </dd>
907 </dt>
908 <dd>
909 <p>
910 for a successful forced update;
911 </p>
912 </dd>
915 </dt>
916 <dd>
917 <p>
918 for a successfully deleted ref;
919 </p>
920 </dd>
923 </dt>
924 <dd>
925 <p>
926 for a successfully pushed new ref;
927 </p>
928 </dd>
931 </dt>
932 <dd>
933 <p>
934 for a ref that was rejected or failed to push; and
935 </p>
936 </dd>
939 </dt>
940 <dd>
941 <p>
942 for a ref that was up to date and did not need pushing.
943 </p>
944 </dd>
945 </dl></div>
946 </dd>
948 summary
949 </dt>
950 <dd>
951 <p>
952 For a successfully pushed ref, the summary shows the old and new
953 values of the ref in a form suitable for using as an argument to
956 </p>
960 rejected
961 </dt>
962 <dd>
963 <p>
964 Git did not try to send the ref at all, typically because it
965 is not a fast-forward and you did not force the update.
966 </p>
967 </dd>
969 remote rejected
970 </dt>
971 <dd>
972 <p>
973 The remote end refused the update. Usually caused by a hook
974 on the remote side, or because the remote repository has one
975 of the following safety options in effect:
980 </p>
981 </dd>
983 remote failure
984 </dt>
985 <dd>
986 <p>
987 The remote end did not report the successful update of the ref,
988 perhaps because of a temporary error on the remote side, a
989 break in the network connection, or other transient error.
990 </p>
991 </dd>
992 </dl></div>
993 </dd>
995 from
996 </dt>
997 <dd>
998 <p>
999 The name of the local ref being pushed, minus its
1001 name of the local ref is omitted.
1002 </p>
1003 </dd>
1005 to
1006 </dt>
1007 <dd>
1008 <p>
1009 The name of the remote ref being updated, minus its
1011 </p>
1012 </dd>
1014 reason
1015 </dt>
1016 <dd>
1017 <p>
1018 A human-readable explanation. In the case of successfully pushed
1019 refs, no explanation is needed. For a failed ref, the reason for
1020 failure is described.
1021 </p>
1022 </dd>
1023 </dl></div>
1024 </div>
1027 <div class="paragraph"><p>When an update changes a branch (or more in general, a ref) that used to
1028 point at commit A to point at another commit B, it is called a
1029 fast-forward update if and only if B is a descendant of A.</p></div>
1030 <div class="paragraph"><p>In a fast-forward update from A to B, the set of commits that the original
1031 commit A built on top of is a subset of the commits the new commit B
1032 builds on top of. Hence, it does not lose any history.</p></div>
1033 <div class="paragraph"><p>In contrast, a non-fast-forward update will lose history. For example,
1034 suppose you and somebody else started at the same commit X, and you built
1035 a history leading to commit B while the other person built a history
1036 leading to commit A. The history looks like this:</p></div>
1039 <pre><tt> B
1040 /
1041 ---X---A</tt></pre>
1042 </div></div>
1043 <div class="paragraph"><p>Further suppose that the other person already pushed changes leading to A
1044 back to the original repository you two obtained the original commit X.</p></div>
1045 <div class="paragraph"><p>The push done by the other person updated the branch that used to point at
1046 commit X to point at commit A. It is a fast-forward.</p></div>
1049 so, the changes introduced by commit A will be lost, because everybody
1050 will now start building on top of B.</p></div>
1051 <div class="paragraph"><p>The command by default does not allow an update that is not a fast-forward
1052 to prevent such loss of history.</p></div>
1053 <div class="paragraph"><p>If you do not want to lose your work (history from X to B) nor the work by
1054 the other person (history from X to A), you would need to first fetch the
1055 history from the repository, create a history that contains changes done
1056 by both parties, and push the result back.</p></div>
1057 <div class="paragraph"><p>You can perform "git pull", resolve potential conflicts, and "git push"
1058 the result. A "git pull" will create a merge commit C between commits A
1059 and B.</p></div>
1062 <pre><tt> B---C
1063 / /
1064 ---X---A</tt></pre>
1065 </div></div>
1066 <div class="paragraph"><p>Updating A with the resulting merge commit will fast-forward and your
1067 push will be accepted.</p></div>
1068 <div class="paragraph"><p>Alternatively, you can rebase your change between X and B on top of A,
1069 with "git pull --rebase", and push the result back. The rebase will
1070 create a new commit D that builds the change between X and B on top of
1071 A.</p></div>
1074 <pre><tt> B D
1075 / /
1076 ---X---A</tt></pre>
1077 </div></div>
1078 <div class="paragraph"><p>Again, updating A with this commit will fast-forward and your push will be
1079 accepted.</p></div>
1080 <div class="paragraph"><p>There is another common situation where you may encounter non-fast-forward
1081 rejection when you try to push, and it is possible even when you are
1082 pushing into a repository nobody else pushes into. After you push commit
1083 A yourself (in the first picture in this section), replace it with "git
1084 commit --amend" to produce commit B, and you try to push it out, because
1085 forgot that you have pushed A out already. In such a case, and only if
1086 you are certain that nobody in the meantime fetched your earlier commit A
1087 (and started building on top of it), you can run "git push --force" to
1088 overwrite it. In other words, "git push --force" is a method reserved for
1089 a case where you do mean to lose history.</p></div>
1090 </div>
1095 git push
1096 </dt>
1097 <dd>
1098 <p>
1101 configured for the current branch).
1102 </p>
1103 </dd>
1105 git push origin
1106 </dt>
1107 <dd>
1108 <p>
1109 Without additional configuration, works like
1111 </p>
1112 <div class="paragraph"><p>The default behavior of this command when no <refspec> is given can be
1114 <div class="paragraph"><p>For example, to default to pushing only the current branch to <tt>origin</tt>
1116 the ones in the examples below) can be configured as the default for
1120 git push origin
1121 </dt>
1122 <dd>
1123 <p>
1126 description of "matching" branches.
1127 </p>
1128 </dd>
1129 </dl></div>
1130 </dd>
1132 git push origin master
1133 </dt>
1134 <dd>
1135 <p>
1140 created.
1141 </p>
1142 </dd>
1144 git push origin HEAD
1145 </dt>
1146 <dd>
1147 <p>
1148 A handy way to push the current branch to the same name on the
1149 remote.
1150 </p>
1151 </dd>
1153 git push origin master:satellite/master dev:satellite/dev
1154 </dt>
1155 <dd>
1156 <p>
1161 </p>
1162 </dd>
1164 git push origin HEAD:master
1165 </dt>
1166 <dd>
1167 <p>
1170 branch without thinking about its local name.
1171 </p>
1172 </dd>
1174 git push origin master:refs/heads/experimental
1175 </dt>
1176 <dd>
1177 <p>
1180 needed to create a new branch or tag in the remote repository when
1181 the local name and the remote name are different; otherwise,
1182 the ref name on its own will work.
1183 </p>
1184 </dd>
1186 git push origin :experimental
1187 </dt>
1188 <dd>
1189 <p>
1192 </p>
1193 </dd>
1195 git push origin +dev:master
1196 </dt>
1197 <dd>
1198 <p>
1199 Update the origin repository’s master branch with the dev branch,
1200 allowing non-fast-forward updates. <strong>This can leave unreferenced
1201 commits dangling in the origin repository.</strong> Consider the
1202 following situation, where a fast-forward is not possible:
1203 </p>
1206 <pre><tt> o---o---o---A---B origin/master
1207 \
1208 X---Y---Z dev</tt></pre>
1209 </div></div>
1213 <pre><tt> A---B (unnamed branch)
1214 /
1215 o---o---o---X---Y---Z master</tt></pre>
1216 </div></div>
1217 <div class="paragraph"><p>Commits A and B would no longer belong to a branch with a symbolic name,
1218 and so would be unreachable. As such, these commits would be removed by
1220 </dd>
1221 </dl></div>
1222 </div>
1226 </div>
1230 </div>
1231 </div>
1232 </body>
1233 </html>