1 <?xml version=
"1.0" encoding=
"UTF-8"?>
2 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.1//EN"
3 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
4 <html xmlns=
"http://www.w3.org/1999/xhtml" xml:
lang=
"en">
6 <meta http-equiv=
"Content-Type" content=
"application/xhtml+xml; charset=UTF-8" />
7 <meta name=
"generator" content=
"AsciiDoc 10.2.0" />
8 <title>git-receive-pack(
1)
</title>
9 <style type=
"text/css">
10 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
14 font-family: Georgia,serif;
18 h1, h2, h3, h4, h5, h6,
19 div.title, caption.title,
20 thead, p.table.header,
22 #author, #revnumber, #revdate, #revremark,
24 font-family: Arial,Helvetica,sans-serif;
28 margin:
1em
5%
1em
5%;
33 text-decoration: underline;
49 h1, h2, h3, h4, h5, h6 {
57 border-bottom:
2px solid silver;
77 border:
1px solid silver;
88 ul
> li { color: #aaa; }
89 ul
> li
> * { color: black; }
91 .monospaced, code, pre {
92 font-family:
"Courier New", Courier, monospace;
99 white-space: pre-wrap;
109 #revnumber, #revdate, #revremark {
114 border-top:
2px solid silver;
120 padding-bottom:
0.5em;
124 padding-bottom:
0.5em;
129 margin-bottom:
1.5em;
131 div.imageblock, div.exampleblock, div.verseblock,
132 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
133 div.admonitionblock {
135 margin-bottom:
1.5em;
137 div.admonitionblock {
139 margin-bottom:
2.0em;
144 div.content { /* Block element content. */
148 /* Block element titles. */
149 div.title, caption.title {
154 margin-bottom:
0.5em;
160 td div.title:first-child {
163 div.content div.title:first-child {
166 div.content + div.title {
170 div.sidebarblock
> div.content {
172 border:
1px solid #dddddd;
173 border-left:
4px solid #f0f0f0;
177 div.listingblock
> div.content {
178 border:
1px solid #dddddd;
179 border-left:
5px solid #f0f0f0;
184 div.quoteblock, div.verseblock {
188 border-left:
5px solid #f0f0f0;
192 div.quoteblock
> div.attribution {
197 div.verseblock
> pre.content {
198 font-family: inherit;
201 div.verseblock
> div.attribution {
205 /* DEPRECATED: Pre version
8.2.7 verse style literal block. */
206 div.verseblock + div.attribution {
210 div.admonitionblock .icon {
214 text-decoration: underline;
216 padding-right:
0.5em;
218 div.admonitionblock td.content {
220 border-left:
3px solid #dddddd;
223 div.exampleblock
> div.content {
224 border-left:
3px solid #dddddd;
228 div.imageblock div.content { padding-left:
0; }
229 span.image img { border-style: none; vertical-align: text-bottom; }
230 a.image:visited { color: white; }
234 margin-bottom:
0.8em;
247 list-style-position: outside;
250 list-style-type: decimal;
253 list-style-type: lower-alpha;
256 list-style-type: upper-alpha;
259 list-style-type: lower-roman;
262 list-style-type: upper-roman;
265 div.compact ul, div.compact ol,
266 div.compact p, div.compact p,
267 div.compact div, div.compact div {
269 margin-bottom:
0.1em;
281 margin-bottom:
0.8em;
284 padding-bottom:
15px;
286 dt.hdlist1.strong, td.hdlist1.strong {
292 padding-right:
0.8em;
298 div.hdlist.compact tr {
307 .footnote, .footnoteref {
311 span.footnote, span.footnoteref {
312 vertical-align: super;
316 margin:
20px
0 20px
0;
320 #footnotes div.footnote {
326 border-top:
1px solid silver;
335 padding-right:
0.5em;
336 padding-bottom:
0.3em;
344 #footer-badges { display: none; }
348 margin-bottom:
2.5em;
356 margin-bottom:
0.1em;
359 div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
376 span.aqua { color: aqua; }
377 span.black { color: black; }
378 span.blue { color: blue; }
379 span.fuchsia { color: fuchsia; }
380 span.gray { color: gray; }
381 span.green { color: green; }
382 span.lime { color: lime; }
383 span.maroon { color: maroon; }
384 span.navy { color: navy; }
385 span.olive { color: olive; }
386 span.purple { color: purple; }
387 span.red { color: red; }
388 span.silver { color: silver; }
389 span.teal { color: teal; }
390 span.white { color: white; }
391 span.yellow { color: yellow; }
393 span.aqua-background { background: aqua; }
394 span.black-background { background: black; }
395 span.blue-background { background: blue; }
396 span.fuchsia-background { background: fuchsia; }
397 span.gray-background { background: gray; }
398 span.green-background { background: green; }
399 span.lime-background { background: lime; }
400 span.maroon-background { background: maroon; }
401 span.navy-background { background: navy; }
402 span.olive-background { background: olive; }
403 span.purple-background { background: purple; }
404 span.red-background { background: red; }
405 span.silver-background { background: silver; }
406 span.teal-background { background: teal; }
407 span.white-background { background: white; }
408 span.yellow-background { background: yellow; }
410 span.big { font-size:
2em; }
411 span.small { font-size:
0.6em; }
413 span.underline { text-decoration: underline; }
414 span.overline { text-decoration: overline; }
415 span.line-through { text-decoration: line-through; }
417 div.unbreakable { page-break-inside: avoid; }
427 margin-bottom:
1.5em;
429 div.tableblock
> table {
430 border:
3px solid #
527bbd;
432 thead, p.table.header {
439 /* Because the table frame attribute is overridden by CSS in most browsers. */
440 div.tableblock
> table[
frame=
"void"] {
443 div.tableblock
> table[
frame=
"hsides"] {
444 border-left-style: none;
445 border-right-style: none;
447 div.tableblock
> table[
frame=
"vsides"] {
448 border-top-style: none;
449 border-bottom-style: none;
460 margin-bottom:
1.5em;
462 thead, p.tableblock.header {
473 border-color: #
527bbd;
474 border-collapse: collapse;
476 th.tableblock, td.tableblock {
480 border-color: #
527bbd;
483 table.tableblock.frame-topbot {
484 border-left-style: hidden;
485 border-right-style: hidden;
487 table.tableblock.frame-sides {
488 border-top-style: hidden;
489 border-bottom-style: hidden;
491 table.tableblock.frame-none {
492 border-style: hidden;
495 th.tableblock.halign-left, td.tableblock.halign-left {
498 th.tableblock.halign-center, td.tableblock.halign-center {
501 th.tableblock.halign-right, td.tableblock.halign-right {
505 th.tableblock.valign-top, td.tableblock.valign-top {
508 th.tableblock.valign-middle, td.tableblock.valign-middle {
509 vertical-align: middle;
511 th.tableblock.valign-bottom, td.tableblock.valign-bottom {
512 vertical-align: bottom;
523 padding-bottom:
0.5em;
524 border-top:
2px solid silver;
525 border-bottom:
2px solid silver;
530 body.manpage div.sectionbody {
535 body.manpage div#toc { display: none; }
540 <script type=
"text/javascript">
542 var asciidoc = { // Namespace.
544 /////////////////////////////////////////////////////////////////////
545 // Table Of Contents generator
546 /////////////////////////////////////////////////////////////////////
548 /* Author: Mihai Bazon, September
2002
549 * http://students.infoiasi.ro/~mishoo
551 * Table Of Content generator
554 * Feel free to use this script under the terms of the GNU General Public
555 * License, as long as you do not remove or alter this notice.
558 /* modified by Troy D. Hanson, September
2006. License: GPL */
559 /* modified by Stuart Rackham,
2006,
2009. License: GPL */
562 toc: function (toclevels) {
564 function getText(el) {
566 for (var i = el.firstChild; i != null; i = i.nextSibling) {
567 if (i.nodeType ==
3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
569 else if (i.firstChild != null)
575 function TocEntry(el, text, toclevel) {
578 this.toclevel = toclevel;
581 function tocEntries(el, toclevels) {
582 var result = new Array;
583 var re = new RegExp('[hH]([
1-'+(toclevels+
1)+'])');
584 // Function that scans the DOM tree for header elements (the DOM2
585 // nodeIterator API would be a better technique but not supported by all
587 var iterate = function (el) {
588 for (var i = el.firstChild; i != null; i = i.nextSibling) {
589 if (i.nodeType ==
1 /* Node.ELEMENT_NODE */) {
590 var mo = re.exec(i.tagName);
591 if (mo && (i.getAttribute(
"class") || i.getAttribute(
"className")) !=
"float") {
592 result[result.length] = new TocEntry(i, getText(i), mo[
1]-
1);
602 var toc = document.getElementById(
"toc");
607 // Delete existing TOC entries in case we're reloading the TOC.
608 var tocEntriesToRemove = [];
610 for (i =
0; i < toc.childNodes.length; i++) {
611 var entry = toc.childNodes[i];
612 if (entry.nodeName.toLowerCase() == 'div'
613 && entry.getAttribute(
"class")
614 && entry.getAttribute(
"class").match(/^toclevel/))
615 tocEntriesToRemove.push(entry);
617 for (i =
0; i < tocEntriesToRemove.length; i++) {
618 toc.removeChild(tocEntriesToRemove[i]);
621 // Rebuild TOC entries.
622 var entries = tocEntries(document.getElementById(
"content"), toclevels);
623 for (var i =
0; i < entries.length; ++i) {
624 var entry = entries[i];
625 if (entry.element.id ==
"")
626 entry.element.id =
"_toc_" + i;
627 var a = document.createElement(
"a");
628 a.href =
"#" + entry.element.id;
629 a.appendChild(document.createTextNode(entry.text));
630 var div = document.createElement(
"div");
632 div.className =
"toclevel" + entry.toclevel;
633 toc.appendChild(div);
635 if (entries.length ==
0)
636 toc.parentNode.removeChild(toc);
640 /////////////////////////////////////////////////////////////////////
641 // Footnotes generator
642 /////////////////////////////////////////////////////////////////////
644 /* Based on footnote generation code from:
645 * http://www.brandspankingnew.net/archive/
2005/
07/format_footnote.html
648 footnotes: function () {
649 // Delete existing footnote entries in case we're reloading the footnodes.
651 var noteholder = document.getElementById(
"footnotes");
655 var entriesToRemove = [];
656 for (i =
0; i < noteholder.childNodes.length; i++) {
657 var entry = noteholder.childNodes[i];
658 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute(
"class") ==
"footnote")
659 entriesToRemove.push(entry);
661 for (i =
0; i < entriesToRemove.length; i++) {
662 noteholder.removeChild(entriesToRemove[i]);
665 // Rebuild footnote entries.
666 var cont = document.getElementById(
"content");
667 var spans = cont.getElementsByTagName(
"span");
670 for (i=
0; i
<spans.length; i++) {
671 if (spans[i].className ==
"footnote") {
673 var note = spans[i].getAttribute(
"data-note");
675 // Use [\s\S] in place of . so multi-line matches work.
676 // Because JavaScript has no s (dotall) regex flag.
677 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[
1];
679 "[<a id='_footnoteref_" + n +
"' href='#_footnote_" + n +
680 "' title='View footnote' class='footnote'>" + n +
"</a>]";
681 spans[i].setAttribute(
"data-note", note);
683 noteholder.innerHTML +=
684 "<div class='footnote' id='_footnote_" + n +
"'>" +
685 "<a href='#_footnoteref_" + n +
"' title='Return to text'>" +
686 n +
"</a>. " + note +
"</div>";
687 var id =spans[i].getAttribute(
"id");
688 if (id != null) refs[
"#"+id] = n;
692 noteholder.parentNode.removeChild(noteholder);
694 // Process footnoterefs.
695 for (i=
0; i
<spans.length; i++) {
696 if (spans[i].className ==
"footnoteref") {
697 var href = spans[i].getElementsByTagName(
"a")[
0].getAttribute(
"href");
698 href = href.match(/#.*/)[
0]; // Because IE return full URL.
701 "[<a href='#_footnote_" + n +
702 "' title='View footnote' class='footnote'>" + n +
"</a>]";
708 install: function(toclevels) {
711 function reinstall() {
712 asciidoc.footnotes();
714 asciidoc.toc(toclevels);
718 function reinstallAndRemoveTimer() {
719 clearInterval(timerId);
723 timerId = setInterval(reinstall,
500);
724 if (document.addEventListener)
725 document.addEventListener(
"DOMContentLoaded", reinstallAndRemoveTimer, false);
727 window.onload = reinstallAndRemoveTimer;
735 <body class=
"manpage">
738 git-receive-pack(
1) Manual Page
741 <div class=
"sectionbody">
742 <p>git-receive-pack -
743 Receive what is pushed into the repository
749 <h2 id=
"_synopsis">SYNOPSIS
</h2>
750 <div class=
"sectionbody">
751 <div class=
"verseblock">
752 <pre class=
"content"><em>git receive-pack
</em> <git-dir
></pre>
753 <div class=
"attribution">
758 <h2 id=
"_description">DESCRIPTION
</h2>
759 <div class=
"sectionbody">
760 <div class=
"paragraph"><p>Invoked by
<em>git send-pack
</em> and updates the repository with the
761 information fed from the remote end.
</p></div>
762 <div class=
"paragraph"><p>This command is usually not invoked directly by the end user.
763 The UI for the protocol is on the
<em>git send-pack
</em> side, and the
764 program pair is meant to be used to push updates to a remote
765 repository. For pull operations, see
<a href=
"git-fetch-pack.html">git-fetch-pack(
1)
</a>.
</p></div>
766 <div class=
"paragraph"><p>The command allows for the creation and fast-forwarding of sha1 refs
767 (heads/tags) on the remote end (strictly speaking, it is the
768 local end
<em>git-receive-pack
</em> runs, but to the user who is sitting at
769 the send-pack end, it is updating the remote. Confused?)
</p></div>
770 <div class=
"paragraph"><p>There are other real-world examples of using update and
771 post-update hooks found in the Documentation/howto directory.
</p></div>
772 <div class=
"paragraph"><p><em>git-receive-pack
</em> honours the receive.denyNonFastForwards config
773 option, which tells it if updates to a ref should be denied if they
774 are not fast-forwards.
</p></div>
775 <div class=
"paragraph"><p>A number of other receive.* config options are available to tweak
776 its behavior, see
<a href=
"git-config.html">git-config(
1)
</a>.
</p></div>
780 <h2 id=
"_options">OPTIONS
</h2>
781 <div class=
"sectionbody">
782 <div class=
"dlist"><dl>
788 The repository to sync into.
792 --http-backend-info-refs
796 Used by
<a href=
"git-http-backend.html">git-http-backend(
1)
</a> to serve up
797 <code>$GIT_URL/info/refs?service=git-receive-pack
</code> requests. See
798 <code>--http-backend-info-refs
</code> in
<a href=
"git-upload-pack.html">git-upload-pack(
1)
</a>.
805 <h2 id=
"_pre_receive_hook">PRE-RECEIVE HOOK
</h2>
806 <div class=
"sectionbody">
807 <div class=
"paragraph"><p>Before any ref is updated, if $GIT_DIR/hooks/pre-receive file exists
808 and is executable, it will be invoked once with no parameters. The
809 standard input of the hook will be one line per ref to be updated:
</p></div>
810 <div class=
"literalblock">
811 <div class=
"content">
812 <pre><code>sha1-old SP sha1-new SP refname LF
</code></pre>
814 <div class=
"paragraph"><p>The refname value is relative to $GIT_DIR; e.g. for the master
815 head this is
"refs/heads/master". The two sha1 values before
816 each refname are the object names for the refname before and after
817 the update. Refs to be created will have sha1-old equal to
0{
40},
818 while refs to be deleted will have sha1-new equal to
0{
40}, otherwise
819 sha1-old and sha1-new should be valid objects in the repository.
</p></div>
820 <div class=
"paragraph"><p>When accepting a signed push (see
<a href=
"git-push.html">git-push(
1)
</a>), the signed
821 push certificate is stored in a blob and an environment variable
822 <code>GIT_PUSH_CERT
</code> can be consulted for its object name. See the
823 description of
<code>post-receive
</code> hook for an example. In addition, the
824 certificate is verified using GPG and the result is exported with
825 the following environment variables:
</p></div>
826 <div class=
"dlist"><dl>
828 <code>GIT_PUSH_CERT_SIGNER
</code>
832 The name and the e-mail address of the owner of the key that
833 signed the push certificate.
837 <code>GIT_PUSH_CERT_KEY
</code>
841 The GPG key ID of the key that signed the push certificate.
845 <code>GIT_PUSH_CERT_STATUS
</code>
849 The status of GPG verification of the push certificate,
850 using the same mnemonic as used in
<code>%G?
</code> format of
<code>git log
</code>
851 family of commands (see
<a href=
"git-log.html">git-log(
1)
</a>).
855 <code>GIT_PUSH_CERT_NONCE
</code>
859 The nonce string the process asked the signer to include
860 in the push certificate. If this does not match the value
861 recorded on the
"nonce" header in the push certificate, it
862 may indicate that the certificate is a valid one that is
863 being replayed from a separate
"git push" session.
867 <code>GIT_PUSH_CERT_NONCE_STATUS
</code>
870 <div class=
"dlist"><dl>
872 <code>UNSOLICITED
</code>
876 "git push --signed" sent a nonce when we did not ask it to
885 "git push --signed" did not send any nonce header.
893 "git push --signed" sent a bogus nonce.
901 "git push --signed" sent the nonce we asked it to send.
909 "git push --signed" sent a nonce different from what we
910 asked it to send now, but in a previous session. See
911 <code>GIT_PUSH_CERT_NONCE_SLOP
</code> environment variable.
917 <code>GIT_PUSH_CERT_NONCE_SLOP
</code>
921 "git push --signed" sent a nonce different from what we
922 asked it to send now, but in a different session whose
923 starting time is different by this many seconds from the
924 current session. Only meaningful when
925 <code>GIT_PUSH_CERT_NONCE_STATUS
</code> says
<code>SLOP
</code>.
926 Also read about
<code>receive.certNonceSlop
</code> variable in
927 <a href=
"git-config.html">git-config(
1)
</a>.
931 <div class=
"paragraph"><p>This hook is called before any refname is updated and before any
932 fast-forward checks are performed.
</p></div>
933 <div class=
"paragraph"><p>If the pre-receive hook exits with a non-zero exit status no updates
934 will be performed, and the update, post-receive and post-update
935 hooks will not be invoked either. This can be useful to quickly
936 bail out if the update is not to be supported.
</p></div>
937 <div class=
"paragraph"><p>See the notes on the quarantine environment below.
</p></div>
941 <h2 id=
"_update_hook">UPDATE HOOK
</h2>
942 <div class=
"sectionbody">
943 <div class=
"paragraph"><p>Before each ref is updated, if $GIT_DIR/hooks/update file exists
944 and is executable, it is invoked once per ref, with three parameters:
</p></div>
945 <div class=
"literalblock">
946 <div class=
"content">
947 <pre><code>$GIT_DIR/hooks/update refname sha1-old sha1-new
</code></pre>
949 <div class=
"paragraph"><p>The refname parameter is relative to $GIT_DIR; e.g. for the master
950 head this is
"refs/heads/master". The two sha1 arguments are
951 the object names for the refname before and after the update.
952 Note that the hook is called before the refname is updated,
953 so either sha1-old is
0{
40} (meaning there is no such ref yet),
954 or it should match what is recorded in refname.
</p></div>
955 <div class=
"paragraph"><p>The hook should exit with non-zero status if it wants to disallow
956 updating the named ref. Otherwise it should exit with zero.
</p></div>
957 <div class=
"paragraph"><p>Successful execution (a zero exit status) of this hook does not
958 ensure the ref will actually be updated, it is only a prerequisite.
959 As such it is not a good idea to send notices (e.g. email) from
960 this hook. Consider using the post-receive hook instead.
</p></div>
964 <h2 id=
"_post_receive_hook">POST-RECEIVE HOOK
</h2>
965 <div class=
"sectionbody">
966 <div class=
"paragraph"><p>After all refs were updated (or attempted to be updated), if any
967 ref update was successful, and if $GIT_DIR/hooks/post-receive
968 file exists and is executable, it will be invoked once with no
969 parameters. The standard input of the hook will be one line
970 for each successfully updated ref:
</p></div>
971 <div class=
"literalblock">
972 <div class=
"content">
973 <pre><code>sha1-old SP sha1-new SP refname LF
</code></pre>
975 <div class=
"paragraph"><p>The refname value is relative to $GIT_DIR; e.g. for the master
976 head this is
"refs/heads/master". The two sha1 values before
977 each refname are the object names for the refname before and after
978 the update. Refs that were created will have sha1-old equal to
979 0{
40}, while refs that were deleted will have sha1-new equal to
980 0{
40}, otherwise sha1-old and sha1-new should be valid objects in
981 the repository.
</p></div>
982 <div class=
"paragraph"><p>The
<code>GIT_PUSH_CERT*
</code> environment variables can be inspected, just as
983 in
<code>pre-receive
</code> hook, after accepting a signed push.
</p></div>
984 <div class=
"paragraph"><p>Using this hook, it is easy to generate mails describing the updates
985 to the repository. This example script sends one mail message per
986 ref listing the commits pushed to the repository, and logs the push
987 certificates of signed pushes with good signatures to a logger
989 <div class=
"listingblock">
990 <div class=
"content">
992 # mail out commit update information.
993 while read oval nval ref
995 if expr
"$oval" : '
0*$'
>/dev/null
997 echo
"Created a new ref, with the following commits:"
998 git rev-list --pretty
"$nval"
1001 git rev-list --pretty
"$nval" "^$oval"
1003 mail -s
"Changes to ref $ref" commit-list@mydomain
1005 # log signed push certificate, if any
1006 if test -n
"${GIT_PUSH_CERT-}" && test ${GIT_PUSH_CERT_STATUS} = G
1009 echo expected nonce is ${GIT_PUSH_NONCE}
1010 git cat-file blob ${GIT_PUSH_CERT}
1011 ) | mail -s
"push certificate from $GIT_PUSH_CERT_SIGNER" push-log@mydomain
1015 <div class=
"paragraph"><p>The exit code from this hook invocation is ignored, however a
1016 non-zero exit code will generate an error message.
</p></div>
1017 <div class=
"paragraph"><p>Note that it is possible for refname to not have sha1-new when this
1018 hook runs. This can easily occur if another user modifies the ref
1019 after it was updated by
<em>git-receive-pack
</em>, but before the hook was able
1020 to evaluate it. It is recommended that hooks rely on sha1-new
1021 rather than the current value of refname.
</p></div>
1025 <h2 id=
"_post_update_hook">POST-UPDATE HOOK
</h2>
1026 <div class=
"sectionbody">
1027 <div class=
"paragraph"><p>After all other processing, if at least one ref was updated, and
1028 if $GIT_DIR/hooks/post-update file exists and is executable, then
1029 post-update will be called with the list of refs that have been updated.
1030 This can be used to implement any repository wide cleanup tasks.
</p></div>
1031 <div class=
"paragraph"><p>The exit code from this hook invocation is ignored; the only thing
1032 left for
<em>git-receive-pack
</em> to do at that point is to exit itself
1034 <div class=
"paragraph"><p>This hook can be used, for example, to run
<code>git update-server-info
</code>
1035 if the repository is packed and is served via a dumb transport.
</p></div>
1036 <div class=
"listingblock">
1037 <div class=
"content">
1038 <pre><code>#!/bin/sh
1039 exec git update-server-info
</code></pre>
1044 <h2 id=
"_quarantine_environment">QUARANTINE ENVIRONMENT
</h2>
1045 <div class=
"sectionbody">
1046 <div class=
"paragraph"><p>When
<code>receive-pack
</code> takes in objects, they are placed into a temporary
1047 "quarantine" directory within the
<code>$GIT_DIR/objects
</code> directory and
1048 migrated into the main object store only after the
<code>pre-receive
</code> hook
1049 has completed. If the push fails before then, the temporary directory is
1050 removed entirely.
</p></div>
1051 <div class=
"paragraph"><p>This has a few user-visible effects and caveats:
</p></div>
1052 <div class=
"olist arabic"><ol class=
"arabic">
1055 Pushes which fail due to problems with the incoming pack, missing
1056 objects, or due to the
<code>pre-receive
</code> hook will not leave any
1057 on-disk data. This is usually helpful to prevent repeated failed
1058 pushes from filling up your disk, but can make debugging more
1064 Any objects created by the
<code>pre-receive
</code> hook will be created in
1065 the quarantine directory (and migrated only if it succeeds).
1070 The
<code>pre-receive
</code> hook MUST NOT update any refs to point to
1071 quarantined objects. Other programs accessing the repository will
1072 not be able to see the objects (and if the pre-receive hook fails,
1073 those refs would become corrupted). For safety, any ref updates
1074 from within
<code>pre-receive
</code> are automatically rejected.
1081 <h2 id=
"_see_also">SEE ALSO
</h2>
1082 <div class=
"sectionbody">
1083 <div class=
"paragraph"><p><a href=
"git-send-pack.html">git-send-pack(
1)
</a>,
<a href=
"gitnamespaces.html">gitnamespaces(
7)
</a></p></div>
1087 <h2 id=
"_git">GIT
</h2>
1088 <div class=
"sectionbody">
1089 <div class=
"paragraph"><p>Part of the
<a href=
"git.html">git(
1)
</a> suite
</p></div>
1093 <div id=
"footnotes"><hr /></div>
1095 <div id=
"footer-text">
1097 2023-
10-
23 14:
43:
46 PDT