git-config.html

   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">
   5 <head>
   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-config(1)</title>
   9 <style type="text/css">
  10 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
  11
  12 /* Default font. */
  13 body {
  14   font-family: Georgia,serif;
  15 }
  16
  17 /* Title font. */
  18 h1, h2, h3, h4, h5, h6,
  19 div.title, caption.title,
  20 thead, p.table.header,
  21 #toctitle,
  22 #author, #revnumber, #revdate, #revremark,
  23 #footer {
  24   font-family: Arial,Helvetica,sans-serif;
  25 }
  26
  27 body {
  28   margin: 1em 5% 1em 5%;
  29 }
  30
  31 a {
  32   color: blue;
  33   text-decoration: underline;
  34 }
  35 a:visited {
  36   color: fuchsia;
  37 }
  38
  39 em {
  40   font-style: italic;
  41   color: navy;
  42 }
  43
  44 strong {
  45   font-weight: bold;
  46   color: #083194;
  47 }
  48
  49 h1, h2, h3, h4, h5, h6 {
  50   color: #527bbd;
  51   margin-top: 1.2em;
  52   margin-bottom: 0.5em;
  53   line-height: 1.3;
  54 }
  55
  56 h1, h2, h3 {
  57   border-bottom: 2px solid silver;
  58 }
  59 h2 {
  60   padding-top: 0.5em;
  61 }
  62 h3 {
  63   float: left;
  64 }
  65 h3 + * {
  66   clear: left;
  67 }
  68 h5 {
  69   font-size: 1.0em;
  70 }
  71
  72 div.sectionbody {
  73   margin-left: 0;
  74 }
  75
  76 hr {
  77   border: 1px solid silver;
  78 }
  79
  80 p {
  81   margin-top: 0.5em;
  82   margin-bottom: 0.5em;
  83 }
  84
  85 ul, ol, li > p {
  86   margin-top: 0;
  87 }
  88 ul > li     { color: #aaa; }
  89 ul > li > * { color: black; }
  90
  91 .monospaced, code, pre {
  92   font-family: "Courier New", Courier, monospace;
  93   font-size: inherit;
  94   color: navy;
  95   padding: 0;
  96   margin: 0;
  97 }
  98 pre {
  99   white-space: pre-wrap;
 100 }
 101
 102 #author {
 103   color: #527bbd;
 104   font-weight: bold;
 105   font-size: 1.1em;
 106 }
 107 #email {
 108 }
 109 #revnumber, #revdate, #revremark {
 110 }
 111
 112 #footer {
 113   font-size: small;
 114   border-top: 2px solid silver;
 115   padding-top: 0.5em;
 116   margin-top: 4.0em;
 117 }
 118 #footer-text {
 119   float: left;
 120   padding-bottom: 0.5em;
 121 }
 122 #footer-badges {
 123   float: right;
 124   padding-bottom: 0.5em;
 125 }
 126
 127 #preamble {
 128   margin-top: 1.5em;
 129   margin-bottom: 1.5em;
 130 }
 131 div.imageblock, div.exampleblock, div.verseblock,
 132 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
 133 div.admonitionblock {
 134   margin-top: 1.0em;
 135   margin-bottom: 1.5em;
 136 }
 137 div.admonitionblock {
 138   margin-top: 2.0em;
 139   margin-bottom: 2.0em;
 140   margin-right: 10%;
 141   color: #606060;
 142 }
 143
 144 div.content { /* Block element content. */
 145   padding: 0;
 146 }
 147
 148 /* Block element titles. */
 149 div.title, caption.title {
 150   color: #527bbd;
 151   font-weight: bold;
 152   text-align: left;
 153   margin-top: 1.0em;
 154   margin-bottom: 0.5em;
 155 }
 156 div.title + * {
 157   margin-top: 0;
 158 }
 159
 160 td div.title:first-child {
 161   margin-top: 0.0em;
 162 }
 163 div.content div.title:first-child {
 164   margin-top: 0.0em;
 165 }
 166 div.content + div.title {
 167   margin-top: 0.0em;
 168 }
 169
 170 div.sidebarblock > div.content {
 171   background: #ffffee;
 172   border: 1px solid #dddddd;
 173   border-left: 4px solid #f0f0f0;
 174   padding: 0.5em;
 175 }
 176
 177 div.listingblock > div.content {
 178   border: 1px solid #dddddd;
 179   border-left: 5px solid #f0f0f0;
 180   background: #f8f8f8;
 181   padding: 0.5em;
 182 }
 183
 184 div.quoteblock, div.verseblock {
 185   padding-left: 1.0em;
 186   margin-left: 1.0em;
 187   margin-right: 10%;
 188   border-left: 5px solid #f0f0f0;
 189   color: #888;
 190 }
 191
 192 div.quoteblock > div.attribution {
 193   padding-top: 0.5em;
 194   text-align: right;
 195 }
 196
 197 div.verseblock > pre.content {
 198   font-family: inherit;
 199   font-size: inherit;
 200 }
 201 div.verseblock > div.attribution {
 202   padding-top: 0.75em;
 203   text-align: left;
 204 }
 205 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
 206 div.verseblock + div.attribution {
 207   text-align: left;
 208 }
 209
 210 div.admonitionblock .icon {
 211   vertical-align: top;
 212   font-size: 1.1em;
 213   font-weight: bold;
 214   text-decoration: underline;
 215   color: #527bbd;
 216   padding-right: 0.5em;
 217 }
 218 div.admonitionblock td.content {
 219   padding-left: 0.5em;
 220   border-left: 3px solid #dddddd;
 221 }
 222
 223 div.exampleblock > div.content {
 224   border-left: 3px solid #dddddd;
 225   padding-left: 0.5em;
 226 }
 227
 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; }
 231
 232 dl {
 233   margin-top: 0.8em;
 234   margin-bottom: 0.8em;
 235 }
 236 dt {
 237   margin-top: 0.5em;
 238   margin-bottom: 0;
 239   font-style: normal;
 240   color: navy;
 241 }
 242 dd > *:first-child {
 243   margin-top: 0.1em;
 244 }
 245
 246 ul, ol {
 247     list-style-position: outside;
 248 }
 249 ol.arabic {
 250   list-style-type: decimal;
 251 }
 252 ol.loweralpha {
 253   list-style-type: lower-alpha;
 254 }
 255 ol.upperalpha {
 256   list-style-type: upper-alpha;
 257 }
 258 ol.lowerroman {
 259   list-style-type: lower-roman;
 260 }
 261 ol.upperroman {
 262   list-style-type: upper-roman;
 263 }
 264
 265 div.compact ul, div.compact ol,
 266 div.compact p, div.compact p,
 267 div.compact div, div.compact div {
 268   margin-top: 0.1em;
 269   margin-bottom: 0.1em;
 270 }
 271
 272 tfoot {
 273   font-weight: bold;
 274 }
 275 td > div.verse {
 276   white-space: pre;
 277 }
 278
 279 div.hdlist {
 280   margin-top: 0.8em;
 281   margin-bottom: 0.8em;
 282 }
 283 div.hdlist tr {
 284   padding-bottom: 15px;
 285 }
 286 dt.hdlist1.strong, td.hdlist1.strong {
 287   font-weight: bold;
 288 }
 289 td.hdlist1 {
 290   vertical-align: top;
 291   font-style: normal;
 292   padding-right: 0.8em;
 293   color: navy;
 294 }
 295 td.hdlist2 {
 296   vertical-align: top;
 297 }
 298 div.hdlist.compact tr {
 299   margin: 0;
 300   padding-bottom: 0;
 301 }
 302
 303 .comment {
 304   background: yellow;
 305 }
 306
 307 .footnote, .footnoteref {
 308   font-size: 0.8em;
 309 }
 310
 311 span.footnote, span.footnoteref {
 312   vertical-align: super;
 313 }
 314
 315 #footnotes {
 316   margin: 20px 0 20px 0;
 317   padding: 7px 0 0 0;
 318 }
 319
 320 #footnotes div.footnote {
 321   margin: 0 0 5px 0;
 322 }
 323
 324 #footnotes hr {
 325   border: none;
 326   border-top: 1px solid silver;
 327   height: 1px;
 328   text-align: left;
 329   margin-left: 0;
 330   width: 20%;
 331   min-width: 100px;
 332 }
 333
 334 div.colist td {
 335   padding-right: 0.5em;
 336   padding-bottom: 0.3em;
 337   vertical-align: top;
 338 }
 339 div.colist td img {
 340   margin-top: 0.3em;
 341 }
 342
 343 @media print {
 344   #footer-badges { display: none; }
 345 }
 346
 347 #toc {
 348   margin-bottom: 2.5em;
 349 }
 350
 351 #toctitle {
 352   color: #527bbd;
 353   font-size: 1.1em;
 354   font-weight: bold;
 355   margin-top: 1.0em;
 356   margin-bottom: 0.1em;
 357 }
 358
 359 div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
 360   margin-top: 0;
 361   margin-bottom: 0;
 362 }
 363 div.toclevel2 {
 364   margin-left: 2em;
 365   font-size: 0.9em;
 366 }
 367 div.toclevel3 {
 368   margin-left: 4em;
 369   font-size: 0.9em;
 370 }
 371 div.toclevel4 {
 372   margin-left: 6em;
 373   font-size: 0.9em;
 374 }
 375
 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; }
 392
 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; }
 409
 410 span.big { font-size: 2em; }
 411 span.small { font-size: 0.6em; }
 412
 413 span.underline { text-decoration: underline; }
 414 span.overline { text-decoration: overline; }
 415 span.line-through { text-decoration: line-through; }
 416
 417 div.unbreakable { page-break-inside: avoid; }
 418
 419
 420 /*
 421  * xhtml11 specific
 422  *
 423  * */
 424
 425 div.tableblock {
 426   margin-top: 1.0em;
 427   margin-bottom: 1.5em;
 428 }
 429 div.tableblock > table {
 430   border: 3px solid #527bbd;
 431 }
 432 thead, p.table.header {
 433   font-weight: bold;
 434   color: #527bbd;
 435 }
 436 p.table {
 437   margin-top: 0;
 438 }
 439 /* Because the table frame attribute is overridden by CSS in most browsers. */
 440 div.tableblock > table[frame="void"] {
 441   border-style: none;
 442 }
 443 div.tableblock > table[frame="hsides"] {
 444   border-left-style: none;
 445   border-right-style: none;
 446 }
 447 div.tableblock > table[frame="vsides"] {
 448   border-top-style: none;
 449   border-bottom-style: none;
 450 }
 451
 452
 453 /*
 454  * html5 specific
 455  *
 456  * */
 457
 458 table.tableblock {
 459   margin-top: 1.0em;
 460   margin-bottom: 1.5em;
 461 }
 462 thead, p.tableblock.header {
 463   font-weight: bold;
 464   color: #527bbd;
 465 }
 466 p.tableblock {
 467   margin-top: 0;
 468 }
 469 table.tableblock {
 470   border-width: 3px;
 471   border-spacing: 0px;
 472   border-style: solid;
 473   border-color: #527bbd;
 474   border-collapse: collapse;
 475 }
 476 th.tableblock, td.tableblock {
 477   border-width: 1px;
 478   padding: 4px;
 479   border-style: solid;
 480   border-color: #527bbd;
 481 }
 482
 483 table.tableblock.frame-topbot {
 484   border-left-style: hidden;
 485   border-right-style: hidden;
 486 }
 487 table.tableblock.frame-sides {
 488   border-top-style: hidden;
 489   border-bottom-style: hidden;
 490 }
 491 table.tableblock.frame-none {
 492   border-style: hidden;
 493 }
 494
 495 th.tableblock.halign-left, td.tableblock.halign-left {
 496   text-align: left;
 497 }
 498 th.tableblock.halign-center, td.tableblock.halign-center {
 499   text-align: center;
 500 }
 501 th.tableblock.halign-right, td.tableblock.halign-right {
 502   text-align: right;
 503 }
 504
 505 th.tableblock.valign-top, td.tableblock.valign-top {
 506   vertical-align: top;
 507 }
 508 th.tableblock.valign-middle, td.tableblock.valign-middle {
 509   vertical-align: middle;
 510 }
 511 th.tableblock.valign-bottom, td.tableblock.valign-bottom {
 512   vertical-align: bottom;
 513 }
 514
 515
 516 /*
 517  * manpage specific
 518  *
 519  * */
 520
 521 body.manpage h1 {
 522   padding-top: 0.5em;
 523   padding-bottom: 0.5em;
 524   border-top: 2px solid silver;
 525   border-bottom: 2px solid silver;
 526 }
 527 body.manpage h2 {
 528   border-style: none;
 529 }
 530 body.manpage div.sectionbody {
 531   margin-left: 3em;
 532 }
 533
 534 @media print {
 535   body.manpage div#toc { display: none; }
 536 }
 537
 538
 539 </style>
 540 <script type="text/javascript">
 541 /*<![CDATA[*/
 542 var asciidoc = {  // Namespace.
 543
 544 /////////////////////////////////////////////////////////////////////
 545 // Table Of Contents generator
 546 /////////////////////////////////////////////////////////////////////
 547
 548 /* Author: Mihai Bazon, September 2002
 549  * http://students.infoiasi.ro/~mishoo
 550  *
 551  * Table Of Content generator
 552  * Version: 0.4
 553  *
 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.
 556  */
 557
 558  /* modified by Troy D. Hanson, September 2006. License: GPL */
 559  /* modified by Stuart Rackham, 2006, 2009. License: GPL */
 560
 561 // toclevels = 1..4.
 562 toc: function (toclevels) {
 563
 564   function getText(el) {
 565     var text = "";
 566     for (var i = el.firstChild; i != null; i = i.nextSibling) {
 567       if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
 568         text += i.data;
 569       else if (i.firstChild != null)
 570         text += getText(i);
 571     }
 572     return text;
 573   }
 574
 575   function TocEntry(el, text, toclevel) {
 576     this.element = el;
 577     this.text = text;
 578     this.toclevel = toclevel;
 579   }
 580
 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
 586     // browsers).
 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);
 593           }
 594           iterate(i);
 595         }
 596       }
 597     }
 598     iterate(el);
 599     return result;
 600   }
 601
 602   var toc = document.getElementById("toc");
 603   if (!toc) {
 604     return;
 605   }
 606
 607   // Delete existing TOC entries in case we're reloading the TOC.
 608   var tocEntriesToRemove = [];
 609   var i;
 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);
 616   }
 617   for (i = 0; i < tocEntriesToRemove.length; i++) {
 618     toc.removeChild(tocEntriesToRemove[i]);
 619   }
 620
 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");
 631     div.appendChild(a);
 632     div.className = "toclevel" + entry.toclevel;
 633     toc.appendChild(div);
 634   }
 635   if (entries.length == 0)
 636     toc.parentNode.removeChild(toc);
 637 },
 638
 639
 640 /////////////////////////////////////////////////////////////////////
 641 // Footnotes generator
 642 /////////////////////////////////////////////////////////////////////
 643
 644 /* Based on footnote generation code from:
 645  * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
 646  */
 647
 648 footnotes: function () {
 649   // Delete existing footnote entries in case we're reloading the footnodes.
 650   var i;
 651   var noteholder = document.getElementById("footnotes");
 652   if (!noteholder) {
 653     return;
 654   }
 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);
 660   }
 661   for (i = 0; i < entriesToRemove.length; i++) {
 662     noteholder.removeChild(entriesToRemove[i]);
 663   }
 664
 665   // Rebuild footnote entries.
 666   var cont = document.getElementById("content");
 667   var spans = cont.getElementsByTagName("span");
 668   var refs = {};
 669   var n = 0;
 670   for (i=0; i<spans.length; i++) {
 671     if (spans[i].className == "footnote") {
 672       n++;
 673       var note = spans[i].getAttribute("data-note");
 674       if (!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];
 678         spans[i].innerHTML =
 679           "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
 680           "' title='View footnote' class='footnote'>" + n + "</a>]";
 681         spans[i].setAttribute("data-note", note);
 682       }
 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;
 689     }
 690   }
 691   if (n == 0)
 692     noteholder.parentNode.removeChild(noteholder);
 693   else {
 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.
 699         n = refs[href];
 700         spans[i].innerHTML =
 701           "[<a href='#_footnote_" + n +
 702           "' title='View footnote' class='footnote'>" + n + "</a>]";
 703       }
 704     }
 705   }
 706 },
 707
 708 install: function(toclevels) {
 709   var timerId;
 710
 711   function reinstall() {
 712     asciidoc.footnotes();
 713     if (toclevels) {
 714       asciidoc.toc(toclevels);
 715     }
 716   }
 717
 718   function reinstallAndRemoveTimer() {
 719     clearInterval(timerId);
 720     reinstall();
 721   }
 722
 723   timerId = setInterval(reinstall, 500);
 724   if (document.addEventListener)
 725     document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
 726   else
 727     window.onload = reinstallAndRemoveTimer;
 728 }
 729
 730 }
 731 asciidoc.install();
 732 /*]]>*/
 733 </script>
 734 </head>
 735 <body class="manpage">
 736 <div id="header">
 737 <h1>
 738 git-config(1) Manual Page
 739 </h1>
 740 <h2>NAME</h2>
 741 <div class="sectionbody">
 742 <p>git-config -
 743    Get and set repository or global options
 744 </p>
 745 </div>
 746 </div>
 747 <div id="content">
 748 <div class="sect1">
 749 <h2 id="_synopsis">SYNOPSIS</h2>
 750 <div class="sectionbody">
 751 <div class="verseblock">
 752 <pre class="content"><em>git config</em> [&lt;file-option&gt;] [--type=&lt;type&gt;] [--fixed-value] [--show-origin] [--show-scope] [-z|--null] &lt;name&gt; [&lt;value&gt; [&lt;value-pattern&gt;]]
 753 <em>git config</em> [&lt;file-option&gt;] [--type=&lt;type&gt;] --add &lt;name&gt; &lt;value&gt;
 754 <em>git config</em> [&lt;file-option&gt;] [--type=&lt;type&gt;] [--fixed-value] --replace-all &lt;name&gt; &lt;value&gt; [&lt;value-pattern&gt;]
 755 <em>git config</em> [&lt;file-option&gt;] [--type=&lt;type&gt;] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] --get &lt;name&gt; [&lt;value-pattern&gt;]
 756 <em>git config</em> [&lt;file-option&gt;] [--type=&lt;type&gt;] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] --get-all &lt;name&gt; [&lt;value-pattern&gt;]
 757 <em>git config</em> [&lt;file-option&gt;] [--type=&lt;type&gt;] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] [--name-only] --get-regexp &lt;name-regex&gt; [&lt;value-pattern&gt;]
 758 <em>git config</em> [&lt;file-option&gt;] [--type=&lt;type&gt;] [-z|--null] --get-urlmatch &lt;name&gt; &lt;URL&gt;
 759 <em>git config</em> [&lt;file-option&gt;] [--fixed-value] --unset &lt;name&gt; [&lt;value-pattern&gt;]
 760 <em>git config</em> [&lt;file-option&gt;] [--fixed-value] --unset-all &lt;name&gt; [&lt;value-pattern&gt;]
 761 <em>git config</em> [&lt;file-option&gt;] --rename-section &lt;old-name&gt; &lt;new-name&gt;
 762 <em>git config</em> [&lt;file-option&gt;] --remove-section &lt;name&gt;
 763 <em>git config</em> [&lt;file-option&gt;] [--show-origin] [--show-scope] [-z|--null] [--name-only] -l | --list
 764 <em>git config</em> [&lt;file-option&gt;] --get-color &lt;name&gt; [&lt;default&gt;]
 765 <em>git config</em> [&lt;file-option&gt;] --get-colorbool &lt;name&gt; [&lt;stdout-is-tty&gt;]
 766 <em>git config</em> [&lt;file-option&gt;] -e | --edit</pre>
 767 <div class="attribution">
 768 </div></div>
 769 </div>
 770 </div>
 771 <div class="sect1">
 772 <h2 id="_description">DESCRIPTION</h2>
 773 <div class="sectionbody">
 774 <div class="paragraph"><p>You can query/set/replace/unset options with this command. The name is
 775 actually the section and the key separated by a dot, and the value will be
 776 escaped.</p></div>
 777 <div class="paragraph"><p>Multiple lines can be added to an option by using the <code>--add</code> option.
 778 If you want to update or unset an option which can occur on multiple
 779 lines, a <code>value-pattern</code> (which is an extended regular expression,
 780 unless the <code>--fixed-value</code> option is given) needs to be given.  Only the
 781 existing values that match the pattern are updated or unset.  If
 782 you want to handle the lines that do <strong>not</strong> match the pattern, just
 783 prepend a single exclamation mark in front (see also <a href="#EXAMPLES">[EXAMPLES]</a>),
 784 but note that this only works when the <code>--fixed-value</code> option is not
 785 in use.</p></div>
 786 <div class="paragraph"><p>The <code>--type=&lt;type&gt;</code> option instructs <em>git config</em> to ensure that incoming and
 787 outgoing values are canonicalize-able under the given &lt;type&gt;.  If no
 788 <code>--type=&lt;type&gt;</code> is given, no canonicalization will be performed. Callers may
 789 unset an existing <code>--type</code> specifier with <code>--no-type</code>.</p></div>
 790 <div class="paragraph"><p>When reading, the values are read from the system, global and
 791 repository local configuration files by default, and options
 792 <code>--system</code>, <code>--global</code>, <code>--local</code>, <code>--worktree</code> and
 793 <code>--file &lt;filename&gt;</code> can be used to tell the command to read from only
 794 that location (see <a href="#FILES">[FILES]</a>).</p></div>
 795 <div class="paragraph"><p>When writing, the new value is written to the repository local
 796 configuration file by default, and options <code>--system</code>, <code>--global</code>,
 797 <code>--worktree</code>, <code>--file &lt;filename&gt;</code> can be used to tell the command to
 798 write to that location (you can say <code>--local</code> but that is the
 799 default).</p></div>
 800 <div class="paragraph"><p>This command will fail with non-zero status upon error.  Some exit
 801 codes are:</p></div>
 802 <div class="ulist"><ul>
 803 <li>
 804 <p>
 805 The section or key is invalid (ret=1),
 806 </p>
 807 </li>
 808 <li>
 809 <p>
 810 no section or name was provided (ret=2),
 811 </p>
 812 </li>
 813 <li>
 814 <p>
 815 the config file is invalid (ret=3),
 816 </p>
 817 </li>
 818 <li>
 819 <p>
 820 the config file cannot be written (ret=4),
 821 </p>
 822 </li>
 823 <li>
 824 <p>
 825 you try to unset an option which does not exist (ret=5),
 826 </p>
 827 </li>
 828 <li>
 829 <p>
 830 you try to unset/set an option for which multiple lines match (ret=5), or
 831 </p>
 832 </li>
 833 <li>
 834 <p>
 835 you try to use an invalid regexp (ret=6).
 836 </p>
 837 </li>
 838 </ul></div>
 839 <div class="paragraph"><p>On success, the command returns the exit code 0.</p></div>
 840 <div class="paragraph"><p>A list of all available configuration variables can be obtained using the
 841 <code>git help --config</code> command.</p></div>
 842 </div>
 843 </div>
 844 <div class="sect1">
 845 <h2 id="OPTIONS">OPTIONS</h2>
 846 <div class="sectionbody">
 847 <div class="dlist"><dl>
 848 <dt class="hdlist1">
 849 --replace-all
 850 </dt>
 851 <dd>
 852 <p>
 853         Default behavior is to replace at most one line. This replaces
 854         all lines matching the key (and optionally the <code>value-pattern</code>).
 855 </p>
 856 </dd>
 857 <dt class="hdlist1">
 858 --add
 859 </dt>
 860 <dd>
 861 <p>
 862         Adds a new line to the option without altering any existing
 863         values.  This is the same as providing <em>^$</em> as the <code>value-pattern</code>
 864         in <code>--replace-all</code>.
 865 </p>
 866 </dd>
 867 <dt class="hdlist1">
 868 --get
 869 </dt>
 870 <dd>
 871 <p>
 872         Get the value for a given key (optionally filtered by a regex
 873         matching the value). Returns error code 1 if the key was not
 874         found and the last value if multiple key values were found.
 875 </p>
 876 </dd>
 877 <dt class="hdlist1">
 878 --get-all
 879 </dt>
 880 <dd>
 881 <p>
 882         Like get, but returns all values for a multi-valued key.
 883 </p>
 884 </dd>
 885 <dt class="hdlist1">
 886 --get-regexp
 887 </dt>
 888 <dd>
 889 <p>
 890         Like --get-all, but interprets the name as a regular expression and
 891         writes out the key names.  Regular expression matching is currently
 892         case-sensitive and done against a canonicalized version of the key
 893         in which section and variable names are lowercased, but subsection
 894         names are not.
 895 </p>
 896 </dd>
 897 <dt class="hdlist1">
 898 --get-urlmatch &lt;name&gt; &lt;URL&gt;
 899 </dt>
 900 <dd>
 901 <p>
 902         When given a two-part name section.key, the value for
 903         section.&lt;URL&gt;.key whose &lt;URL&gt; part matches the best to the
 904         given URL is returned (if no such key exists, the value for
 905         section.key is used as a fallback).  When given just the
 906         section as name, do so for all the keys in the section and
 907         list them.  Returns error code 1 if no value is found.
 908 </p>
 909 </dd>
 910 <dt class="hdlist1">
 911 --global
 912 </dt>
 913 <dd>
 914 <p>
 915         For writing options: write to global <code>~/.gitconfig</code> file
 916         rather than the repository <code>.git/config</code>, write to
 917         <code>$XDG_CONFIG_HOME/git/config</code> file if this file exists and the
 918         <code>~/.gitconfig</code> file doesn&#8217;t.
 919 </p>
 920 <div class="paragraph"><p>For reading options: read only from global <code>~/.gitconfig</code> and from
 921 <code>$XDG_CONFIG_HOME/git/config</code> rather than from all available files.</p></div>
 922 <div class="paragraph"><p>See also <a href="#FILES">[FILES]</a>.</p></div>
 923 </dd>
 924 <dt class="hdlist1">
 925 --system
 926 </dt>
 927 <dd>
 928 <p>
 929         For writing options: write to system-wide
 930         <code>$(prefix)/etc/gitconfig</code> rather than the repository
 931         <code>.git/config</code>.
 932 </p>
 933 <div class="paragraph"><p>For reading options: read only from system-wide <code>$(prefix)/etc/gitconfig</code>
 934 rather than from all available files.</p></div>
 935 <div class="paragraph"><p>See also <a href="#FILES">[FILES]</a>.</p></div>
 936 </dd>
 937 <dt class="hdlist1">
 938 --local
 939 </dt>
 940 <dd>
 941 <p>
 942         For writing options: write to the repository <code>.git/config</code> file.
 943         This is the default behavior.
 944 </p>
 945 <div class="paragraph"><p>For reading options: read only from the repository <code>.git/config</code> rather than
 946 from all available files.</p></div>
 947 <div class="paragraph"><p>See also <a href="#FILES">[FILES]</a>.</p></div>
 948 </dd>
 949 <dt class="hdlist1">
 950 --worktree
 951 </dt>
 952 <dd>
 953 <p>
 954         Similar to <code>--local</code> except that <code>$GIT_DIR/config.worktree</code> is
 955         read from or written to if <code>extensions.worktreeConfig</code> is
 956         enabled. If not it&#8217;s the same as <code>--local</code>. Note that <code>$GIT_DIR</code>
 957         is equal to <code>$GIT_COMMON_DIR</code> for the main working tree, but is of
 958         the form <code>$GIT_DIR/worktrees/&lt;id&gt;/</code> for other working trees. See
 959         <a href="git-worktree.html">git-worktree(1)</a> to learn how to enable
 960         <code>extensions.worktreeConfig</code>.
 961 </p>
 962 </dd>
 963 <dt class="hdlist1">
 964 -f &lt;config-file&gt;
 965 </dt>
 966 <dt class="hdlist1">
 967 --file &lt;config-file&gt;
 968 </dt>
 969 <dd>
 970 <p>
 971         For writing options: write to the specified file rather than the
 972         repository <code>.git/config</code>.
 973 </p>
 974 <div class="paragraph"><p>For reading options: read only from the specified file rather than from all
 975 available files.</p></div>
 976 <div class="paragraph"><p>See also <a href="#FILES">[FILES]</a>.</p></div>
 977 </dd>
 978 <dt class="hdlist1">
 979 --blob &lt;blob&gt;
 980 </dt>
 981 <dd>
 982 <p>
 983         Similar to <code>--file</code> but use the given blob instead of a file. E.g.
 984         you can use <em>master:.gitmodules</em> to read values from the file
 985         <em>.gitmodules</em> in the master branch. See "SPECIFYING REVISIONS"
 986         section in <a href="gitrevisions.html">gitrevisions(7)</a> for a more complete list of
 987         ways to spell blob names.
 988 </p>
 989 </dd>
 990 <dt class="hdlist1">
 991 --remove-section
 992 </dt>
 993 <dd>
 994 <p>
 995         Remove the given section from the configuration file.
 996 </p>
 997 </dd>
 998 <dt class="hdlist1">
 999 --rename-section
1000 </dt>
1001 <dd>
1002 <p>
1003         Rename the given section to a new name.
1004 </p>
1005 </dd>
1006 <dt class="hdlist1">
1007 --unset
1008 </dt>
1009 <dd>
1010 <p>
1011         Remove the line matching the key from config file.
1012 </p>
1013 </dd>
1014 <dt class="hdlist1">
1015 --unset-all
1016 </dt>
1017 <dd>
1018 <p>
1019         Remove all lines matching the key from config file.
1020 </p>
1021 </dd>
1022 <dt class="hdlist1">
1023 -l
1024 </dt>
1025 <dt class="hdlist1">
1026 --list
1027 </dt>
1028 <dd>
1029 <p>
1030         List all variables set in config file, along with their values.
1031 </p>
1032 </dd>
1033 <dt class="hdlist1">
1034 --fixed-value
1035 </dt>
1036 <dd>
1037 <p>
1038         When used with the <code>value-pattern</code> argument, treat <code>value-pattern</code> as
1039         an exact string instead of a regular expression. This will restrict
1040         the name/value pairs that are matched to only those where the value
1041         is exactly equal to the <code>value-pattern</code>.
1042 </p>
1043 </dd>
1044 <dt class="hdlist1">
1045 --type &lt;type&gt;
1046 </dt>
1047 <dd>
1048 <p>
1049   <em>git config</em> will ensure that any input or output is valid under the given
1050   type constraint(s), and will canonicalize outgoing values in <code>&lt;type&gt;</code>'s
1051   canonical form.
1052 </p>
1053 <div class="paragraph"><p>Valid <code>&lt;type&gt;</code>'s include:</p></div>
1054 <div class="ulist"><ul>
1055 <li>
1056 <p>
1057 <em>bool</em>: canonicalize values as either "true" or "false".
1058 </p>
1059 </li>
1060 <li>
1061 <p>
1062 <em>int</em>: canonicalize values as simple decimal numbers. An optional suffix of
1063   <em>k</em>, <em>m</em>, or <em>g</em> will cause the value to be multiplied by 1024, 1048576, or
1064   1073741824 upon input.
1065 </p>
1066 </li>
1067 <li>
1068 <p>
1069 <em>bool-or-int</em>: canonicalize according to either <em>bool</em> or <em>int</em>, as described
1070   above.
1071 </p>
1072 </li>
1073 <li>
1074 <p>
1075 <em>path</em>: canonicalize by expanding a leading <code>~</code> to the value of <code>$HOME</code> and
1076   <code>~user</code> to the home directory for the specified user. This specifier has no
1077   effect when setting the value (but you can use <code>git config section.variable
1078   ~/</code> from the command line to let your shell do the expansion.)
1079 </p>
1080 </li>
1081 <li>
1082 <p>
1083 <em>expiry-date</em>: canonicalize by converting from a fixed or relative date-string
1084   to a timestamp. This specifier has no effect when setting the value.
1085 </p>
1086 </li>
1087 <li>
1088 <p>
1089 <em>color</em>: When getting a value, canonicalize by converting to an ANSI color
1090   escape sequence. When setting a value, a sanity-check is performed to ensure
1091   that the given value is canonicalize-able as an ANSI color, but it is written
1092   as-is.
1093 </p>
1094 </li>
1095 </ul></div>
1096 </dd>
1097 <dt class="hdlist1">
1098 --bool
1099 </dt>
1100 <dt class="hdlist1">
1101 --int
1102 </dt>
1103 <dt class="hdlist1">
1104 --bool-or-int
1105 </dt>
1106 <dt class="hdlist1">
1107 --path
1108 </dt>
1109 <dt class="hdlist1">
1110 --expiry-date
1111 </dt>
1112 <dd>
1113 <p>
1114   Historical options for selecting a type specifier. Prefer instead <code>--type</code>
1115   (see above).
1116 </p>
1117 </dd>
1118 <dt class="hdlist1">
1119 --no-type
1120 </dt>
1121 <dd>
1122 <p>
1123   Un-sets the previously set type specifier (if one was previously set). This
1124   option requests that <em>git config</em> not canonicalize the retrieved variable.
1125   <code>--no-type</code> has no effect without <code>--type=&lt;type&gt;</code> or <code>--&lt;type&gt;</code>.
1126 </p>
1127 </dd>
1128 <dt class="hdlist1">
1129 -z
1130 </dt>
1131 <dt class="hdlist1">
1132 --null
1133 </dt>
1134 <dd>
1135 <p>
1136         For all options that output values and/or keys, always
1137         end values with the null character (instead of a
1138         newline). Use newline instead as a delimiter between
1139         key and value. This allows for secure parsing of the
1140         output without getting confused e.g. by values that
1141         contain line breaks.
1142 </p>
1143 </dd>
1144 <dt class="hdlist1">
1145 --name-only
1146 </dt>
1147 <dd>
1148 <p>
1149         Output only the names of config variables for <code>--list</code> or
1150         <code>--get-regexp</code>.
1151 </p>
1152 </dd>
1153 <dt class="hdlist1">
1154 --show-origin
1155 </dt>
1156 <dd>
1157 <p>
1158         Augment the output of all queried config options with the
1159         origin type (file, standard input, blob, command line) and
1160         the actual origin (config file path, ref, or blob id if
1161         applicable).
1162 </p>
1163 </dd>
1164 <dt class="hdlist1">
1165 --show-scope
1166 </dt>
1167 <dd>
1168 <p>
1169         Similar to <code>--show-origin</code> in that it augments the output of
1170         all queried config options with the scope of that value
1171         (worktree, local, global, system, command).
1172 </p>
1173 </dd>
1174 <dt class="hdlist1">
1175 --get-colorbool &lt;name&gt; [&lt;stdout-is-tty&gt;]
1176 </dt>
1177 <dd>
1178 <p>
1179         Find the color setting for <code>&lt;name&gt;</code> (e.g. <code>color.diff</code>) and output
1180         "true" or "false".  <code>&lt;stdout-is-tty&gt;</code> should be either "true" or
1181         "false", and is taken into account when configuration says
1182         "auto".  If <code>&lt;stdout-is-tty&gt;</code> is missing, then checks the standard
1183         output of the command itself, and exits with status 0 if color
1184         is to be used, or exits with status 1 otherwise.
1185         When the color setting for <code>name</code> is undefined, the command uses
1186         <code>color.ui</code> as fallback.
1187 </p>
1188 </dd>
1189 <dt class="hdlist1">
1190 --get-color &lt;name&gt; [&lt;default&gt;]
1191 </dt>
1192 <dd>
1193 <p>
1194         Find the color configured for <code>name</code> (e.g. <code>color.diff.new</code>) and
1195         output it as the ANSI color escape sequence to the standard
1196         output.  The optional <code>default</code> parameter is used instead, if
1197         there is no color configured for <code>name</code>.
1198 </p>
1199 <div class="paragraph"><p><code>--type=color [--default=&lt;default&gt;]</code> is preferred over <code>--get-color</code>
1200 (but note that <code>--get-color</code> will omit the trailing newline printed by
1201 <code>--type=color</code>).</p></div>
1202 </dd>
1203 <dt class="hdlist1">
1204 -e
1205 </dt>
1206 <dt class="hdlist1">
1207 --edit
1208 </dt>
1209 <dd>
1210 <p>
1211         Opens an editor to modify the specified config file; either
1212         <code>--system</code>, <code>--global</code>, or repository (default).
1213 </p>
1214 </dd>
1215 <dt class="hdlist1">
1216 --[no-]includes
1217 </dt>
1218 <dd>
1219 <p>
1220         Respect <code>include.*</code> directives in config files when looking up
1221         values. Defaults to <code>off</code> when a specific file is given (e.g.,
1222         using <code>--file</code>, <code>--global</code>, etc) and <code>on</code> when searching all
1223         config files.
1224 </p>
1225 </dd>
1226 <dt class="hdlist1">
1227 --default &lt;value&gt;
1228 </dt>
1229 <dd>
1230 <p>
1231   When using <code>--get</code>, and the requested variable is not found, behave as if
1232   &lt;value&gt; were the value assigned to the that variable.
1233 </p>
1234 </dd>
1235 </dl></div>
1236 </div>
1237 </div>
1238 <div class="sect1">
1239 <h2 id="_configuration">CONFIGURATION</h2>
1240 <div class="sectionbody">
1241 <div class="paragraph"><p><code>pager.config</code> is only respected when listing configuration, i.e., when
1242 using <code>--list</code> or any of the <code>--get-*</code> which may return multiple results.
1243 The default is to use a pager.</p></div>
1244 </div>
1245 </div>
1246 <div class="sect1">
1247 <h2 id="FILES">FILES</h2>
1248 <div class="sectionbody">
1249 <div class="paragraph"><p>By default, <em>git config</em> will read configuration options from multiple
1250 files:</p></div>
1251 <div class="dlist"><dl>
1252 <dt class="hdlist1">
1253 $(prefix)/etc/gitconfig
1254 </dt>
1255 <dd>
1256 <p>
1257         System-wide configuration file.
1258 </p>
1259 </dd>
1260 <dt class="hdlist1">
1261 $XDG_CONFIG_HOME/git/config
1262 </dt>
1263 <dt class="hdlist1">
1264 ~/.gitconfig
1265 </dt>
1266 <dd>
1267 <p>
1268         User-specific configuration files. When the XDG_CONFIG_HOME environment
1269         variable is not set or empty, $HOME/.config/ is used as
1270         $XDG_CONFIG_HOME.
1271 </p>
1272 <div class="paragraph"><p>These are also called "global" configuration files. If both files exist, both
1273 files are read in the order given above.</p></div>
1274 </dd>
1275 <dt class="hdlist1">
1276 $GIT_DIR/config
1277 </dt>
1278 <dd>
1279 <p>
1280         Repository specific configuration file.
1281 </p>
1282 </dd>
1283 <dt class="hdlist1">
1284 $GIT_DIR/config.worktree
1285 </dt>
1286 <dd>
1287 <p>
1288         This is optional and is only searched when
1289         <code>extensions.worktreeConfig</code> is present in $GIT_DIR/config.
1290 </p>
1291 </dd>
1292 </dl></div>
1293 <div class="paragraph"><p>You may also provide additional configuration parameters when running any
1294 git command by using the <code>-c</code> option. See <a href="git.html">git(1)</a> for details.</p></div>
1295 <div class="paragraph"><p>Options will be read from all of these files that are available. If the
1296 global or the system-wide configuration files are missing or unreadable they
1297 will be ignored. If the repository configuration file is missing or unreadable,
1298 <em>git config</em> will exit with a non-zero error code. An error message is produced
1299 if the file is unreadable, but not if it is missing.</p></div>
1300 <div class="paragraph"><p>The files are read in the order given above, with last value found taking
1301 precedence over values read earlier.  When multiple values are taken then all
1302 values of a key from all files will be used.</p></div>
1303 <div class="paragraph"><p>By default, options are only written to the repository specific
1304 configuration file. Note that this also affects options like <code>--replace-all</code>
1305 and <code>--unset</code>. <strong><em>git config</em> will only ever change one file at a time</strong>.</p></div>
1306 <div class="paragraph"><p>You can limit which configuration sources are read from or written to by
1307 specifying the path of a file with the <code>--file</code> option, or by specifying a
1308 configuration scope with <code>--system</code>, <code>--global</code>, <code>--local</code>, or <code>--worktree</code>.
1309 For more, see <a href="#OPTIONS">[OPTIONS]</a> above.</p></div>
1310 </div>
1311 </div>
1312 <div class="sect1">
1313 <h2 id="SCOPES">SCOPES</h2>
1314 <div class="sectionbody">
1315 <div class="paragraph"><p>Each configuration source falls within a configuration scope. The scopes
1316 are:</p></div>
1317 <div class="dlist"><dl>
1318 <dt class="hdlist1">
1319 system
1320 </dt>
1321 <dd>
1322 <p>
1323         $(prefix)/etc/gitconfig
1324 </p>
1325 </dd>
1326 <dt class="hdlist1">
1327 global
1328 </dt>
1329 <dd>
1330 <p>
1331         $XDG_CONFIG_HOME/git/config
1332 </p>
1333 <div class="paragraph"><p>~/.gitconfig</p></div>
1334 </dd>
1335 <dt class="hdlist1">
1336 local
1337 </dt>
1338 <dd>
1339 <p>
1340         $GIT_DIR/config
1341 </p>
1342 </dd>
1343 <dt class="hdlist1">
1344 worktree
1345 </dt>
1346 <dd>
1347 <p>
1348         $GIT_DIR/config.worktree
1349 </p>
1350 </dd>
1351 <dt class="hdlist1">
1352 command
1353 </dt>
1354 <dd>
1355 <p>
1356         GIT_CONFIG_{COUNT,KEY,VALUE} environment variables (see <a href="#ENVIRONMENT">[ENVIRONMENT]</a>
1357         below)
1358 </p>
1359 <div class="paragraph"><p>the <code>-c</code> option</p></div>
1360 </dd>
1361 </dl></div>
1362 <div class="paragraph"><p>With the exception of <em>command</em>, each scope corresponds to a command line
1363 option: <code>--system</code>, <code>--global</code>, <code>--local</code>, <code>--worktree</code>.</p></div>
1364 <div class="paragraph"><p>When reading options, specifying a scope will only read options from the
1365 files within that scope. When writing options, specifying a scope will write
1366 to the files within that scope (instead of the repository specific
1367 configuration file). See <a href="#OPTIONS">[OPTIONS]</a> above for a complete description.</p></div>
1368 <div class="paragraph"><p>Most configuration options are respected regardless of the scope it is
1369 defined in, but some options are only respected in certain scopes. See the
1370 respective option&#8217;s documentation for the full details.</p></div>
1371 <div class="sect2">
1372 <h3 id="_protected_configuration">Protected configuration</h3>
1373 <div class="paragraph"><p>Protected configuration refers to the <em>system</em>, <em>global</em>, and <em>command</em> scopes.
1374 For security reasons, certain options are only respected when they are
1375 specified in protected configuration, and ignored otherwise.</p></div>
1376 <div class="paragraph"><p>Git treats these scopes as if they are controlled by the user or a trusted
1377 administrator. This is because an attacker who controls these scopes can do
1378 substantial harm without using Git, so it is assumed that the user&#8217;s environment
1379 protects these scopes against attackers.</p></div>
1380 </div>
1381 </div>
1382 </div>
1383 <div class="sect1">
1384 <h2 id="ENVIRONMENT">ENVIRONMENT</h2>
1385 <div class="sectionbody">
1386 <div class="dlist"><dl>
1387 <dt class="hdlist1">
1388 GIT_CONFIG_GLOBAL
1389 </dt>
1390 <dt class="hdlist1">
1391 GIT_CONFIG_SYSTEM
1392 </dt>
1393 <dd>
1394 <p>
1395         Take the configuration from the given files instead from global or
1396         system-level configuration. See <a href="git.html">git(1)</a> for details.
1397 </p>
1398 </dd>
1399 <dt class="hdlist1">
1400 GIT_CONFIG_NOSYSTEM
1401 </dt>
1402 <dd>
1403 <p>
1404         Whether to skip reading settings from the system-wide
1405         $(prefix)/etc/gitconfig file. See <a href="git.html">git(1)</a> for details.
1406 </p>
1407 </dd>
1408 </dl></div>
1409 <div class="paragraph"><p>See also <a href="#FILES">[FILES]</a>.</p></div>
1410 <div class="dlist"><dl>
1411 <dt class="hdlist1">
1412 GIT_CONFIG_COUNT
1413 </dt>
1414 <dt class="hdlist1">
1415 GIT_CONFIG_KEY_&lt;n&gt;
1416 </dt>
1417 <dt class="hdlist1">
1418 GIT_CONFIG_VALUE_&lt;n&gt;
1419 </dt>
1420 <dd>
1421 <p>
1422         If GIT_CONFIG_COUNT is set to a positive number, all environment pairs
1423         GIT_CONFIG_KEY_&lt;n&gt; and GIT_CONFIG_VALUE_&lt;n&gt; up to that number will be
1424         added to the process&#8217;s runtime configuration. The config pairs are
1425         zero-indexed. Any missing key or value is treated as an error. An empty
1426         GIT_CONFIG_COUNT is treated the same as GIT_CONFIG_COUNT=0, namely no
1427         pairs are processed. These environment variables will override values
1428         in configuration files, but will be overridden by any explicit options
1429         passed via <code>git -c</code>.
1430 </p>
1431 <div class="paragraph"><p>This is useful for cases where you want to spawn multiple git commands
1432 with a common configuration but cannot depend on a configuration file,
1433 for example when writing scripts.</p></div>
1434 </dd>
1435 <dt class="hdlist1">
1436 GIT_CONFIG
1437 </dt>
1438 <dd>
1439 <p>
1440         If no <code>--file</code> option is provided to <code>git config</code>, use the file
1441         given by <code>GIT_CONFIG</code> as if it were provided via <code>--file</code>. This
1442         variable has no effect on other Git commands, and is mostly for
1443         historical compatibility; there is generally no reason to use it
1444         instead of the <code>--file</code> option.
1445 </p>
1446 </dd>
1447 </dl></div>
1448 </div>
1449 </div>
1450 <div class="sect1">
1451 <h2 id="EXAMPLES">EXAMPLES</h2>
1452 <div class="sectionbody">
1453 <div class="paragraph"><p>Given a .git/config like this:</p></div>
1454 <div class="listingblock">
1455 <div class="content">
1456 <pre><code>#
1457 # This is the config file, and
1458 # a '#' or ';' character indicates
1459 # a comment
1460 #
1461
1462 ; core variables
1463 [core]
1464         ; Don't trust file modes
1465         filemode = false
1466
1467 ; Our diff algorithm
1468 [diff]
1469         external = /usr/local/bin/diff-wrapper
1470         renames = true
1471
1472 ; Proxy settings
1473 [core]
1474         gitproxy=proxy-command for kernel.org
1475         gitproxy=default-proxy ; for all the rest
1476
1477 ; HTTP
1478 [http]
1479         sslVerify
1480 [http "https://weak.example.com"]
1481         sslVerify = false
1482         cookieFile = /tmp/cookie.txt</code></pre>
1483 </div></div>
1484 <div class="paragraph"><p>you can set the filemode to true with</p></div>
1485 <div class="listingblock">
1486 <div class="content">
1487 <pre><code>% git config core.filemode true</code></pre>
1488 </div></div>
1489 <div class="paragraph"><p>The hypothetical proxy command entries actually have a postfix to discern
1490 what URL they apply to. Here is how to change the entry for kernel.org
1491 to "ssh".</p></div>
1492 <div class="listingblock">
1493 <div class="content">
1494 <pre><code>% git config core.gitproxy '"ssh" for kernel.org' 'for kernel.org$'</code></pre>
1495 </div></div>
1496 <div class="paragraph"><p>This makes sure that only the key/value pair for kernel.org is replaced.</p></div>
1497 <div class="paragraph"><p>To delete the entry for renames, do</p></div>
1498 <div class="listingblock">
1499 <div class="content">
1500 <pre><code>% git config --unset diff.renames</code></pre>
1501 </div></div>
1502 <div class="paragraph"><p>If you want to delete an entry for a multivar (like core.gitproxy above),
1503 you have to provide a regex matching the value of exactly one line.</p></div>
1504 <div class="paragraph"><p>To query the value for a given key, do</p></div>
1505 <div class="listingblock">
1506 <div class="content">
1507 <pre><code>% git config --get core.filemode</code></pre>
1508 </div></div>
1509 <div class="paragraph"><p>or</p></div>
1510 <div class="listingblock">
1511 <div class="content">
1512 <pre><code>% git config core.filemode</code></pre>
1513 </div></div>
1514 <div class="paragraph"><p>or, to query a multivar:</p></div>
1515 <div class="listingblock">
1516 <div class="content">
1517 <pre><code>% git config --get core.gitproxy "for kernel.org$"</code></pre>
1518 </div></div>
1519 <div class="paragraph"><p>If you want to know all the values for a multivar, do:</p></div>
1520 <div class="listingblock">
1521 <div class="content">
1522 <pre><code>% git config --get-all core.gitproxy</code></pre>
1523 </div></div>
1524 <div class="paragraph"><p>If you like to live dangerously, you can replace <strong>all</strong> core.gitproxy by a
1525 new one with</p></div>
1526 <div class="listingblock">
1527 <div class="content">
1528 <pre><code>% git config --replace-all core.gitproxy ssh</code></pre>
1529 </div></div>
1530 <div class="paragraph"><p>However, if you really only want to replace the line for the default proxy,
1531 i.e. the one without a "for &#8230;" postfix, do something like this:</p></div>
1532 <div class="listingblock">
1533 <div class="content">
1534 <pre><code>% git config core.gitproxy ssh '! for '</code></pre>
1535 </div></div>
1536 <div class="paragraph"><p>To actually match only values with an exclamation mark, you have to</p></div>
1537 <div class="listingblock">
1538 <div class="content">
1539 <pre><code>% git config section.key value '[!]'</code></pre>
1540 </div></div>
1541 <div class="paragraph"><p>To add a new proxy, without altering any of the existing ones, use</p></div>
1542 <div class="listingblock">
1543 <div class="content">
1544 <pre><code>% git config --add core.gitproxy '"proxy-command" for example.com'</code></pre>
1545 </div></div>
1546 <div class="paragraph"><p>An example to use customized color from the configuration in your
1547 script:</p></div>
1548 <div class="listingblock">
1549 <div class="content">
1550 <pre><code>#!/bin/sh
1551 WS=$(git config --get-color color.diff.whitespace "blue reverse")
1552 RESET=$(git config --get-color "" "reset")
1553 echo "${WS}your whitespace color or blue reverse${RESET}"</code></pre>
1554 </div></div>
1555 <div class="paragraph"><p>For URLs in <code>https://weak.example.com</code>, <code>http.sslVerify</code> is set to
1556 false, while it is set to <code>true</code> for all others:</p></div>
1557 <div class="listingblock">
1558 <div class="content">
1559 <pre><code>% git config --type=bool --get-urlmatch http.sslverify https://good.example.com
1560 true
1561 % git config --type=bool --get-urlmatch http.sslverify https://weak.example.com
1562 false
1563 % git config --get-urlmatch http https://weak.example.com
1564 http.cookieFile /tmp/cookie.txt
1565 http.sslverify false</code></pre>
1566 </div></div>
1567 </div>
1568 </div>
1569 <div class="sect1">
1570 <h2 id="_configuration_file">CONFIGURATION FILE</h2>
1571 <div class="sectionbody">
1572 <div class="paragraph"><p>The Git configuration file contains a number of variables that affect
1573 the Git commands' behavior. The files <code>.git/config</code> and optionally
1574 <code>config.worktree</code> (see the "CONFIGURATION FILE" section of
1575 <a href="git-worktree.html">git-worktree(1)</a>) in each repository are used to store the
1576 configuration for that repository, and <code>$HOME/.gitconfig</code> is used to
1577 store a per-user configuration as fallback values for the <code>.git/config</code>
1578 file. The file <code>/etc/gitconfig</code> can be used to store a system-wide
1579 default configuration.</p></div>
1580 <div class="paragraph"><p>The configuration variables are used by both the Git plumbing
1581 and the porcelains. The variables are divided into sections, wherein
1582 the fully qualified variable name of the variable itself is the last
1583 dot-separated segment and the section name is everything before the last
1584 dot. The variable names are case-insensitive, allow only alphanumeric
1585 characters and <code>-</code>, and must start with an alphabetic character.  Some
1586 variables may appear multiple times; we say then that the variable is
1587 multivalued.</p></div>
1588 <div class="sect2">
1589 <h3 id="_syntax">Syntax</h3>
1590 <div class="paragraph"><p>The syntax is fairly flexible and permissive; whitespaces are mostly
1591 ignored.  The <em>#</em> and <em>;</em> characters begin comments to the end of line,
1592 blank lines are ignored.</p></div>
1593 <div class="paragraph"><p>The file consists of sections and variables.  A section begins with
1594 the name of the section in square brackets and continues until the next
1595 section begins.  Section names are case-insensitive.  Only alphanumeric
1596 characters, <code>-</code> and <code>.</code> are allowed in section names.  Each variable
1597 must belong to some section, which means that there must be a section
1598 header before the first setting of a variable.</p></div>
1599 <div class="paragraph"><p>Sections can be further divided into subsections.  To begin a subsection
1600 put its name in double quotes, separated by space from the section name,
1601 in the section header, like in the example below:</p></div>
1602 <div class="listingblock">
1603 <div class="content">
1604 <pre><code>        [section "subsection"]</code></pre>
1605 </div></div>
1606 <div class="paragraph"><p>Subsection names are case sensitive and can contain any characters except
1607 newline and the null byte. Doublequote <code>"</code> and backslash can be included
1608 by escaping them as <code>\"</code> and <code>\\</code>, respectively. Backslashes preceding
1609 other characters are dropped when reading; for example, <code>\t</code> is read as
1610 <code>t</code> and <code>\0</code> is read as <code>0</code>. Section headers cannot span multiple lines.
1611 Variables may belong directly to a section or to a given subsection. You
1612 can have <code>[section]</code> if you have <code>[section "subsection"]</code>, but you don&#8217;t
1613 need to.</p></div>
1614 <div class="paragraph"><p>There is also a deprecated <code>[section.subsection]</code> syntax. With this
1615 syntax, the subsection name is converted to lower-case and is also
1616 compared case sensitively. These subsection names follow the same
1617 restrictions as section names.</p></div>
1618 <div class="paragraph"><p>All the other lines (and the remainder of the line after the section
1619 header) are recognized as setting variables, in the form
1620 <em>name = value</em> (or just <em>name</em>, which is a short-hand to say that
1621 the variable is the boolean "true").
1622 The variable names are case-insensitive, allow only alphanumeric characters
1623 and <code>-</code>, and must start with an alphabetic character.</p></div>
1624 <div class="paragraph"><p>A line that defines a value can be continued to the next line by
1625 ending it with a <code>\</code>; the backslash and the end-of-line are
1626 stripped.  Leading whitespaces after <em>name =</em>, the remainder of the
1627 line after the first comment character <em>#</em> or <em>;</em>, and trailing
1628 whitespaces of the line are discarded unless they are enclosed in
1629 double quotes.  Internal whitespaces within the value are retained
1630 verbatim.</p></div>
1631 <div class="paragraph"><p>Inside double quotes, double quote <code>"</code> and backslash <code>\</code> characters
1632 must be escaped: use <code>\"</code> for <code>"</code> and <code>\\</code> for <code>\</code>.</p></div>
1633 <div class="paragraph"><p>The following escape sequences (beside <code>\"</code> and <code>\\</code>) are recognized:
1634 <code>\n</code> for newline character (NL), <code>\t</code> for horizontal tabulation (HT, TAB)
1635 and <code>\b</code> for backspace (BS).  Other char escape sequences (including octal
1636 escape sequences) are invalid.</p></div>
1637 </div>
1638 <div class="sect2">
1639 <h3 id="_includes">Includes</h3>
1640 <div class="paragraph"><p>The <code>include</code> and <code>includeIf</code> sections allow you to include config
1641 directives from another source. These sections behave identically to
1642 each other with the exception that <code>includeIf</code> sections may be ignored
1643 if their condition does not evaluate to true; see "Conditional includes"
1644 below.</p></div>
1645 <div class="paragraph"><p>You can include a config file from another by setting the special
1646 <code>include.path</code> (or <code>includeIf.*.path</code>) variable to the name of the file
1647 to be included. The variable takes a pathname as its value, and is
1648 subject to tilde expansion. These variables can be given multiple times.</p></div>
1649 <div class="paragraph"><p>The contents of the included file are inserted immediately, as if they
1650 had been found at the location of the include directive. If the value of the
1651 variable is a relative path, the path is considered to
1652 be relative to the configuration file in which the include directive
1653 was found.  See below for examples.</p></div>
1654 </div>
1655 <div class="sect2">
1656 <h3 id="_conditional_includes">Conditional includes</h3>
1657 <div class="paragraph"><p>You can include a config file from another conditionally by setting a
1658 <code>includeIf.&lt;condition&gt;.path</code> variable to the name of the file to be
1659 included.</p></div>
1660 <div class="paragraph"><p>The condition starts with a keyword followed by a colon and some data
1661 whose format and meaning depends on the keyword. Supported keywords
1662 are:</p></div>
1663 <div class="dlist"><dl>
1664 <dt class="hdlist1">
1665 <code>gitdir</code>
1666 </dt>
1667 <dd>
1668 <p>
1669         The data that follows the keyword <code>gitdir:</code> is used as a glob
1670         pattern. If the location of the .git directory matches the
1671         pattern, the include condition is met.
1672 </p>
1673 <div class="paragraph"><p>The .git location may be auto-discovered, or come from <code>$GIT_DIR</code>
1674 environment variable. If the repository is auto discovered via a .git
1675 file (e.g. from submodules, or a linked worktree), the .git location
1676 would be the final location where the .git directory is, not where the
1677 .git file is.</p></div>
1678 <div class="paragraph"><p>The pattern can contain standard globbing wildcards and two additional
1679 ones, <code>**/</code> and <code>/**</code>, that can match multiple path components. Please
1680 refer to <a href="gitignore.html">gitignore(5)</a> for details. For convenience:</p></div>
1681 <div class="ulist"><ul>
1682 <li>
1683 <p>
1684 If the pattern starts with <code>~/</code>, <code>~</code> will be substituted with the
1685    content of the environment variable <code>HOME</code>.
1686 </p>
1687 </li>
1688 <li>
1689 <p>
1690 If the pattern starts with <code>./</code>, it is replaced with the directory
1691    containing the current config file.
1692 </p>
1693 </li>
1694 <li>
1695 <p>
1696 If the pattern does not start with either <code>~/</code>, <code>./</code> or <code>/</code>, <code>**/</code>
1697    will be automatically prepended. For example, the pattern <code>foo/bar</code>
1698    becomes <code>**/foo/bar</code> and would match <code>/any/path/to/foo/bar</code>.
1699 </p>
1700 </li>
1701 <li>
1702 <p>
1703 If the pattern ends with <code>/</code>, <code>**</code> will be automatically added. For
1704    example, the pattern <code>foo/</code> becomes <code>foo/**</code>. In other words, it
1705    matches "foo" and everything inside, recursively.
1706 </p>
1707 </li>
1708 </ul></div>
1709 </dd>
1710 <dt class="hdlist1">
1711 <code>gitdir/i</code>
1712 </dt>
1713 <dd>
1714 <p>
1715         This is the same as <code>gitdir</code> except that matching is done
1716         case-insensitively (e.g. on case-insensitive file systems)
1717 </p>
1718 </dd>
1719 <dt class="hdlist1">
1720 <code>onbranch</code>
1721 </dt>
1722 <dd>
1723 <p>
1724         The data that follows the keyword <code>onbranch:</code> is taken to be a
1725         pattern with standard globbing wildcards and two additional
1726         ones, <code>**/</code> and <code>/**</code>, that can match multiple path components.
1727         If we are in a worktree where the name of the branch that is
1728         currently checked out matches the pattern, the include condition
1729         is met.
1730 </p>
1731 <div class="paragraph"><p>If the pattern ends with <code>/</code>, <code>**</code> will be automatically added. For
1732 example, the pattern <code>foo/</code> becomes <code>foo/**</code>. In other words, it matches
1733 all branches that begin with <code>foo/</code>. This is useful if your branches are
1734 organized hierarchically and you would like to apply a configuration to
1735 all the branches in that hierarchy.</p></div>
1736 </dd>
1737 <dt class="hdlist1">
1738 <code>hasconfig:remote.*.url:</code>
1739 </dt>
1740 <dd>
1741 <p>
1742         The data that follows this keyword is taken to
1743         be a pattern with standard globbing wildcards and two
1744         additional ones, <code>**/</code> and <code>/**</code>, that can match multiple
1745         components. The first time this keyword is seen, the rest of
1746         the config files will be scanned for remote URLs (without
1747         applying any values). If there exists at least one remote URL
1748         that matches this pattern, the include condition is met.
1749 </p>
1750 <div class="paragraph"><p>Files included by this option (directly or indirectly) are not allowed
1751 to contain remote URLs.</p></div>
1752 <div class="paragraph"><p>Note that unlike other includeIf conditions, resolving this condition
1753 relies on information that is not yet known at the point of reading the
1754 condition. A typical use case is this option being present as a
1755 system-level or global-level config, and the remote URL being in a
1756 local-level config; hence the need to scan ahead when resolving this
1757 condition. In order to avoid the chicken-and-egg problem in which
1758 potentially-included files can affect whether such files are potentially
1759 included, Git breaks the cycle by prohibiting these files from affecting
1760 the resolution of these conditions (thus, prohibiting them from
1761 declaring remote URLs).</p></div>
1762 <div class="paragraph"><p>As for the naming of this keyword, it is for forwards compatibility with
1763 a naming scheme that supports more variable-based include conditions,
1764 but currently Git only supports the exact keyword described above.</p></div>
1765 </dd>
1766 </dl></div>
1767 <div class="paragraph"><p>A few more notes on matching via <code>gitdir</code> and <code>gitdir/i</code>:</p></div>
1768 <div class="ulist"><ul>
1769 <li>
1770 <p>
1771 Symlinks in <code>$GIT_DIR</code> are not resolved before matching.
1772 </p>
1773 </li>
1774 <li>
1775 <p>
1776 Both the symlink &amp; realpath versions of paths will be matched
1777    outside of <code>$GIT_DIR</code>. E.g. if ~/git is a symlink to
1778    /mnt/storage/git, both <code>gitdir:~/git</code> and <code>gitdir:/mnt/storage/git</code>
1779    will match.
1780 </p>
1781 <div class="paragraph"><p>This was not the case in the initial release of this feature in
1782 v2.13.0, which only matched the realpath version. Configuration that
1783 wants to be compatible with the initial release of this feature needs
1784 to either specify only the realpath version, or both versions.</p></div>
1785 </li>
1786 <li>
1787 <p>
1788 Note that "../" is not special and will match literally, which is
1789    unlikely what you want.
1790 </p>
1791 </li>
1792 </ul></div>
1793 </div>
1794 <div class="sect2">
1795 <h3 id="_example">Example</h3>
1796 <div class="listingblock">
1797 <div class="content">
1798 <pre><code># Core variables
1799 [core]
1800         ; Don't trust file modes
1801         filemode = false
1802
1803 # Our diff algorithm
1804 [diff]
1805         external = /usr/local/bin/diff-wrapper
1806         renames = true
1807
1808 [branch "devel"]
1809         remote = origin
1810         merge = refs/heads/devel
1811
1812 # Proxy settings
1813 [core]
1814         gitProxy="ssh" for "kernel.org"
1815         gitProxy=default-proxy ; for the rest
1816
1817 [include]
1818         path = /path/to/foo.inc ; include by absolute path
1819         path = foo.inc ; find "foo.inc" relative to the current file
1820         path = ~/foo.inc ; find "foo.inc" in your `$HOME` directory
1821
1822 ; include if $GIT_DIR is /path/to/foo/.git
1823 [includeIf "gitdir:/path/to/foo/.git"]
1824         path = /path/to/foo.inc
1825
1826 ; include for all repositories inside /path/to/group
1827 [includeIf "gitdir:/path/to/group/"]
1828         path = /path/to/foo.inc
1829
1830 ; include for all repositories inside $HOME/to/group
1831 [includeIf "gitdir:~/to/group/"]
1832         path = /path/to/foo.inc
1833
1834 ; relative paths are always relative to the including
1835 ; file (if the condition is true); their location is not
1836 ; affected by the condition
1837 [includeIf "gitdir:/path/to/group/"]
1838         path = foo.inc
1839
1840 ; include only if we are in a worktree where foo-branch is
1841 ; currently checked out
1842 [includeIf "onbranch:foo-branch"]
1843         path = foo.inc
1844
1845 ; include only if a remote with the given URL exists (note
1846 ; that such a URL may be provided later in a file or in a
1847 ; file read after this file is read, as seen in this example)
1848 [includeIf "hasconfig:remote.*.url:https://example.com/**"]
1849         path = foo.inc
1850 [remote "origin"]
1851         url = https://example.com/git</code></pre>
1852 </div></div>
1853 </div>
1854 <div class="sect2">
1855 <h3 id="_values">Values</h3>
1856 <div class="paragraph"><p>Values of many variables are treated as a simple string, but there
1857 are variables that take values of specific types and there are rules
1858 as to how to spell them.</p></div>
1859 <div class="dlist"><dl>
1860 <dt class="hdlist1">
1861 boolean
1862 </dt>
1863 <dd>
1864 <p>
1865        When a variable is said to take a boolean value, many
1866        synonyms are accepted for <em>true</em> and <em>false</em>; these are all
1867        case-insensitive.
1868 </p>
1869 <div class="dlist"><dl>
1870 <dt class="hdlist1">
1871 true
1872 </dt>
1873 <dd>
1874 <p>
1875 Boolean true literals are <code>yes</code>, <code>on</code>, <code>true</code>,
1876                 and <code>1</code>.  Also, a variable defined without <code>= &lt;value&gt;</code>
1877                 is taken as true.
1878 </p>
1879 </dd>
1880 <dt class="hdlist1">
1881 false
1882 </dt>
1883 <dd>
1884 <p>
1885 Boolean false literals are <code>no</code>, <code>off</code>, <code>false</code>,
1886                 <code>0</code> and the empty string.
1887 </p>
1888 <div class="paragraph"><p>When converting a value to its canonical form using the <code>--type=bool</code> type
1889 specifier, <em>git config</em> will ensure that the output is "true" or
1890 "false" (spelled in lowercase).</p></div>
1891 </dd>
1892 </dl></div>
1893 </dd>
1894 <dt class="hdlist1">
1895 integer
1896 </dt>
1897 <dd>
1898 <p>
1899        The value for many variables that specify various sizes can
1900        be suffixed with <code>k</code>, <code>M</code>,&#8230; to mean "scale the number by
1901        1024", "by 1024x1024", etc.
1902 </p>
1903 </dd>
1904 <dt class="hdlist1">
1905 color
1906 </dt>
1907 <dd>
1908 <p>
1909        The value for a variable that takes a color is a list of
1910        colors (at most two, one for foreground and one for background)
1911        and attributes (as many as you want), separated by spaces.
1912 </p>
1913 <div class="paragraph"><p>The basic colors accepted are <code>normal</code>, <code>black</code>, <code>red</code>, <code>green</code>,
1914 <code>yellow</code>, <code>blue</code>, <code>magenta</code>, <code>cyan</code>, <code>white</code> and <code>default</code>.  The first
1915 color given is the foreground; the second is the background.  All the
1916 basic colors except <code>normal</code> and <code>default</code> have a bright variant that can
1917 be specified by prefixing the color with <code>bright</code>, like <code>brightred</code>.</p></div>
1918 <div class="paragraph"><p>The color <code>normal</code> makes no change to the color. It is the same as an
1919 empty string, but can be used as the foreground color when specifying a
1920 background color alone (for example, "normal red").</p></div>
1921 <div class="paragraph"><p>The color <code>default</code> explicitly resets the color to the terminal default,
1922 for example to specify a cleared background. Although it varies between
1923 terminals, this is usually not the same as setting to "white black".</p></div>
1924 <div class="paragraph"><p>Colors may also be given as numbers between 0 and 255; these use ANSI
1925 256-color mode (but note that not all terminals may support this).  If
1926 your terminal supports it, you may also specify 24-bit RGB values as
1927 hex, like <code>#ff0ab3</code>.</p></div>
1928 <div class="paragraph"><p>The accepted attributes are <code>bold</code>, <code>dim</code>, <code>ul</code>, <code>blink</code>, <code>reverse</code>,
1929 <code>italic</code>, and <code>strike</code> (for crossed-out or "strikethrough" letters).
1930 The position of any attributes with respect to the colors
1931 (before, after, or in between), doesn&#8217;t matter. Specific attributes may
1932 be turned off by prefixing them with <code>no</code> or <code>no-</code> (e.g., <code>noreverse</code>,
1933 <code>no-ul</code>, etc).</p></div>
1934 <div class="paragraph"><p>The pseudo-attribute <code>reset</code> resets all colors and attributes before
1935 applying the specified coloring. For example, <code>reset green</code> will result
1936 in a green foreground and default background without any active
1937 attributes.</p></div>
1938 <div class="paragraph"><p>An empty color string produces no color effect at all. This can be used
1939 to avoid coloring specific elements without disabling color entirely.</p></div>
1940 <div class="paragraph"><p>For git&#8217;s pre-defined color slots, the attributes are meant to be reset
1941 at the beginning of each item in the colored output. So setting
1942 <code>color.decorate.branch</code> to <code>black</code> will paint that branch name in a
1943 plain <code>black</code>, even if the previous thing on the same output line (e.g.
1944 opening parenthesis before the list of branch names in <code>log --decorate</code>
1945 output) is set to be painted with <code>bold</code> or some other attribute.
1946 However, custom log formats may do more complicated and layered
1947 coloring, and the negated forms may be useful there.</p></div>
1948 </dd>
1949 <dt class="hdlist1">
1950 pathname
1951 </dt>
1952 <dd>
1953 <p>
1954         A variable that takes a pathname value can be given a
1955         string that begins with "<code>~/</code>" or "<code>~user/</code>", and the usual
1956         tilde expansion happens to such a string: <code>~/</code>
1957         is expanded to the value of <code>$HOME</code>, and <code>~user/</code> to the
1958         specified user&#8217;s home directory.
1959 </p>
1960 <div class="paragraph"><p>If a path starts with <code>%(prefix)/</code>, the remainder is interpreted as a
1961 path relative to Git&#8217;s "runtime prefix", i.e. relative to the location
1962 where Git itself was installed. For example, <code>%(prefix)/bin/</code> refers to
1963 the directory in which the Git executable itself lives. If Git was
1964 compiled without runtime prefix support, the compiled-in prefix will be
1965 substituted instead. In the unlikely event that a literal path needs to
1966 be specified that should <em>not</em> be expanded, it needs to be prefixed by
1967 <code>./</code>, like so: <code>./%(prefix)/bin</code>.</p></div>
1968 </dd>
1969 </dl></div>
1970 </div>
1971 <div class="sect2">
1972 <h3 id="_variables">Variables</h3>
1973 <div class="paragraph"><p>Note that this list is non-comprehensive and not necessarily complete.
1974 For command-specific variables, you will find a more detailed description
1975 in the appropriate manual page.</p></div>
1976 <div class="paragraph"><p>Other git-related tools may and do use their own variables.  When
1977 inventing new variables for use in your own tool, make sure their
1978 names do not conflict with those that are used by Git itself and
1979 other popular tools, and describe them in your documentation.</p></div>
1980 <div class="dlist"><dl>
1981 <dt class="hdlist1">
1982 advice.*
1983 </dt>
1984 <dd>
1985 <p>
1986         These variables control various optional help messages designed to
1987         aid new users. All <em>advice.*</em> variables default to <em>true</em>, and you
1988         can tell Git that you do not need help by setting these to <em>false</em>:
1989 </p>
1990 <div class="openblock">
1991 <div class="content">
1992 <div class="dlist"><dl>
1993 <dt class="hdlist1">
1994 ambiguousFetchRefspec
1995 </dt>
1996 <dd>
1997 <p>
1998                 Advice shown when fetch refspec for multiple remotes map to
1999                 the same remote-tracking branch namespace and causes branch
2000                 tracking set-up to fail.
2001 </p>
2002 </dd>
2003 <dt class="hdlist1">
2004 fetchShowForcedUpdates
2005 </dt>
2006 <dd>
2007 <p>
2008                 Advice shown when <a href="git-fetch.html">git-fetch(1)</a> takes a long time
2009                 to calculate forced updates after ref updates, or to warn
2010                 that the check is disabled.
2011 </p>
2012 </dd>
2013 <dt class="hdlist1">
2014 pushUpdateRejected
2015 </dt>
2016 <dd>
2017 <p>
2018                 Set this variable to <em>false</em> if you want to disable
2019                 <em>pushNonFFCurrent</em>, <em>pushNonFFMatching</em>, <em>pushAlreadyExists</em>,
2020                 <em>pushFetchFirst</em>, <em>pushNeedsForce</em>, and <em>pushRefNeedsUpdate</em>
2021                 simultaneously.
2022 </p>
2023 </dd>
2024 <dt class="hdlist1">
2025 pushNonFFCurrent
2026 </dt>
2027 <dd>
2028 <p>
2029                 Advice shown when <a href="git-push.html">git-push(1)</a> fails due to a
2030                 non-fast-forward update to the current branch.
2031 </p>
2032 </dd>
2033 <dt class="hdlist1">
2034 pushNonFFMatching
2035 </dt>
2036 <dd>
2037 <p>
2038                 Advice shown when you ran <a href="git-push.html">git-push(1)</a> and pushed
2039                 <em>matching refs</em> explicitly (i.e. you used <em>:</em>, or
2040                 specified a refspec that isn&#8217;t your current branch) and
2041                 it resulted in a non-fast-forward error.
2042 </p>
2043 </dd>
2044 <dt class="hdlist1">
2045 pushAlreadyExists
2046 </dt>
2047 <dd>
2048 <p>
2049                 Shown when <a href="git-push.html">git-push(1)</a> rejects an update that
2050                 does not qualify for fast-forwarding (e.g., a tag.)
2051 </p>
2052 </dd>
2053 <dt class="hdlist1">
2054 pushFetchFirst
2055 </dt>
2056 <dd>
2057 <p>
2058                 Shown when <a href="git-push.html">git-push(1)</a> rejects an update that
2059                 tries to overwrite a remote ref that points at an
2060                 object we do not have.
2061 </p>
2062 </dd>
2063 <dt class="hdlist1">
2064 pushNeedsForce
2065 </dt>
2066 <dd>
2067 <p>
2068                 Shown when <a href="git-push.html">git-push(1)</a> rejects an update that
2069                 tries to overwrite a remote ref that points at an
2070                 object that is not a commit-ish, or make the remote
2071                 ref point at an object that is not a commit-ish.
2072 </p>
2073 </dd>
2074 <dt class="hdlist1">
2075 pushUnqualifiedRefname
2076 </dt>
2077 <dd>
2078 <p>
2079                 Shown when <a href="git-push.html">git-push(1)</a> gives up trying to
2080                 guess based on the source and destination refs what
2081                 remote ref namespace the source belongs in, but where
2082                 we can still suggest that the user push to either
2083                 refs/heads/* or refs/tags/* based on the type of the
2084                 source object.
2085 </p>
2086 </dd>
2087 <dt class="hdlist1">
2088 pushRefNeedsUpdate
2089 </dt>
2090 <dd>
2091 <p>
2092                 Shown when <a href="git-push.html">git-push(1)</a> rejects a forced update of
2093                 a branch when its remote-tracking ref has updates that we
2094                 do not have locally.
2095 </p>
2096 </dd>
2097 <dt class="hdlist1">
2098 skippedCherryPicks
2099 </dt>
2100 <dd>
2101 <p>
2102                 Shown when <a href="git-rebase.html">git-rebase(1)</a> skips a commit that has already
2103                 been cherry-picked onto the upstream branch.
2104 </p>
2105 </dd>
2106 <dt class="hdlist1">
2107 statusAheadBehind
2108 </dt>
2109 <dd>
2110 <p>
2111                 Shown when <a href="git-status.html">git-status(1)</a> computes the ahead/behind
2112                 counts for a local ref compared to its remote tracking ref,
2113                 and that calculation takes longer than expected. Will not
2114                 appear if <code>status.aheadBehind</code> is false or the option
2115                 <code>--no-ahead-behind</code> is given.
2116 </p>
2117 </dd>
2118 <dt class="hdlist1">
2119 statusHints
2120 </dt>
2121 <dd>
2122 <p>
2123                 Show directions on how to proceed from the current
2124                 state in the output of <a href="git-status.html">git-status(1)</a>, in
2125                 the template shown when writing commit messages in
2126                 <a href="git-commit.html">git-commit(1)</a>, and in the help message shown
2127                 by <a href="git-switch.html">git-switch(1)</a> or
2128                 <a href="git-checkout.html">git-checkout(1)</a> when switching branch.
2129 </p>
2130 </dd>
2131 <dt class="hdlist1">
2132 statusUoption
2133 </dt>
2134 <dd>
2135 <p>
2136                 Advise to consider using the <code>-u</code> option to <a href="git-status.html">git-status(1)</a>
2137                 when the command takes more than 2 seconds to enumerate untracked
2138                 files.
2139 </p>
2140 </dd>
2141 <dt class="hdlist1">
2142 commitBeforeMerge
2143 </dt>
2144 <dd>
2145 <p>
2146                 Advice shown when <a href="git-merge.html">git-merge(1)</a> refuses to
2147                 merge to avoid overwriting local changes.
2148 </p>
2149 </dd>
2150 <dt class="hdlist1">
2151 resetNoRefresh
2152 </dt>
2153 <dd>
2154 <p>
2155                 Advice to consider using the <code>--no-refresh</code> option to
2156                 <a href="git-reset.html">git-reset(1)</a> when the command takes more than 2 seconds
2157                 to refresh the index after reset.
2158 </p>
2159 </dd>
2160 <dt class="hdlist1">
2161 resolveConflict
2162 </dt>
2163 <dd>
2164 <p>
2165                 Advice shown by various commands when conflicts
2166                 prevent the operation from being performed.
2167 </p>
2168 </dd>
2169 <dt class="hdlist1">
2170 sequencerInUse
2171 </dt>
2172 <dd>
2173 <p>
2174                 Advice shown when a sequencer command is already in progress.
2175 </p>
2176 </dd>
2177 <dt class="hdlist1">
2178 implicitIdentity
2179 </dt>
2180 <dd>
2181 <p>
2182                 Advice on how to set your identity configuration when
2183                 your information is guessed from the system username and
2184                 domain name.
2185 </p>
2186 </dd>
2187 <dt class="hdlist1">
2188 detachedHead
2189 </dt>
2190 <dd>
2191 <p>
2192                 Advice shown when you used
2193                 <a href="git-switch.html">git-switch(1)</a> or <a href="git-checkout.html">git-checkout(1)</a>
2194                 to move to the detach HEAD state, to instruct how to
2195                 create a local branch after the fact.
2196 </p>
2197 </dd>
2198 <dt class="hdlist1">
2199 suggestDetachingHead
2200 </dt>
2201 <dd>
2202 <p>
2203                 Advice shown when <a href="git-switch.html">git-switch(1)</a> refuses to detach HEAD
2204                 without the explicit <code>--detach</code> option.
2205 </p>
2206 </dd>
2207 <dt class="hdlist1">
2208 checkoutAmbiguousRemoteBranchName
2209 </dt>
2210 <dd>
2211 <p>
2212                 Advice shown when the argument to
2213                 <a href="git-checkout.html">git-checkout(1)</a> and <a href="git-switch.html">git-switch(1)</a>
2214                 ambiguously resolves to a
2215                 remote tracking branch on more than one remote in
2216                 situations where an unambiguous argument would have
2217                 otherwise caused a remote-tracking branch to be
2218                 checked out. See the <code>checkout.defaultRemote</code>
2219                 configuration variable for how to set a given remote
2220                 to used by default in some situations where this
2221                 advice would be printed.
2222 </p>
2223 </dd>
2224 <dt class="hdlist1">
2225 amWorkDir
2226 </dt>
2227 <dd>
2228 <p>
2229                 Advice that shows the location of the patch file when
2230                 <a href="git-am.html">git-am(1)</a> fails to apply it.
2231 </p>
2232 </dd>
2233 <dt class="hdlist1">
2234 rmHints
2235 </dt>
2236 <dd>
2237 <p>
2238                 In case of failure in the output of <a href="git-rm.html">git-rm(1)</a>,
2239                 show directions on how to proceed from the current state.
2240 </p>
2241 </dd>
2242 <dt class="hdlist1">
2243 addEmbeddedRepo
2244 </dt>
2245 <dd>
2246 <p>
2247                 Advice on what to do when you&#8217;ve accidentally added one
2248                 git repo inside of another.
2249 </p>
2250 </dd>
2251 <dt class="hdlist1">
2252 ignoredHook
2253 </dt>
2254 <dd>
2255 <p>
2256                 Advice shown if a hook is ignored because the hook is not
2257                 set as executable.
2258 </p>
2259 </dd>
2260 <dt class="hdlist1">
2261 waitingForEditor
2262 </dt>
2263 <dd>
2264 <p>
2265                 Print a message to the terminal whenever Git is waiting for
2266                 editor input from the user.
2267 </p>
2268 </dd>
2269 <dt class="hdlist1">
2270 nestedTag
2271 </dt>
2272 <dd>
2273 <p>
2274                 Advice shown if a user attempts to recursively tag a tag object.
2275 </p>
2276 </dd>
2277 <dt class="hdlist1">
2278 submoduleAlternateErrorStrategyDie
2279 </dt>
2280 <dd>
2281 <p>
2282                 Advice shown when a submodule.alternateErrorStrategy option
2283                 configured to "die" causes a fatal error.
2284 </p>
2285 </dd>
2286 <dt class="hdlist1">
2287 submodulesNotUpdated
2288 </dt>
2289 <dd>
2290 <p>
2291                 Advice shown when a user runs a submodule command that fails
2292                 because <code>git submodule update --init</code> was not run.
2293 </p>
2294 </dd>
2295 <dt class="hdlist1">
2296 addIgnoredFile
2297 </dt>
2298 <dd>
2299 <p>
2300                 Advice shown if a user attempts to add an ignored file to
2301                 the index.
2302 </p>
2303 </dd>
2304 <dt class="hdlist1">
2305 addEmptyPathspec
2306 </dt>
2307 <dd>
2308 <p>
2309                 Advice shown if a user runs the add command without providing
2310                 the pathspec parameter.
2311 </p>
2312 </dd>
2313 <dt class="hdlist1">
2314 updateSparsePath
2315 </dt>
2316 <dd>
2317 <p>
2318                 Advice shown when either <a href="git-add.html">git-add(1)</a> or <a href="git-rm.html">git-rm(1)</a>
2319                 is asked to update index entries outside the current sparse
2320                 checkout.
2321 </p>
2322 </dd>
2323 <dt class="hdlist1">
2324 diverging
2325 </dt>
2326 <dd>
2327 <p>
2328                 Advice shown when a fast-forward is not possible.
2329 </p>
2330 </dd>
2331 <dt class="hdlist1">
2332 worktreeAddOrphan
2333 </dt>
2334 <dd>
2335 <p>
2336                 Advice shown when a user tries to create a worktree from an
2337                 invalid reference, to instruct how to create a new orphan
2338                 branch instead.
2339 </p>
2340 </dd>
2341 </dl></div>
2342 </div></div>
2343 </dd>
2344 <dt class="hdlist1">
2345 core.fileMode
2346 </dt>
2347 <dd>
2348 <p>
2349         Tells Git if the executable bit of files in the working tree
2350         is to be honored.
2351 </p>
2352 <div class="paragraph"><p>Some filesystems lose the executable bit when a file that is
2353 marked as executable is checked out, or checks out a
2354 non-executable file with executable bit on.
2355 <a href="git-clone.html">git-clone(1)</a> or <a href="git-init.html">git-init(1)</a> probe the filesystem
2356 to see if it handles the executable bit correctly
2357 and this variable is automatically set as necessary.</p></div>
2358 <div class="paragraph"><p>A repository, however, may be on a filesystem that handles
2359 the filemode correctly, and this variable is set to <em>true</em>
2360 when created, but later may be made accessible from another
2361 environment that loses the filemode (e.g. exporting ext4 via
2362 CIFS mount, visiting a Cygwin created repository with
2363 Git for Windows or Eclipse).
2364 In such a case it may be necessary to set this variable to <em>false</em>.
2365 See <a href="git-update-index.html">git-update-index(1)</a>.</p></div>
2366 <div class="paragraph"><p>The default is true (when core.filemode is not specified in the config file).</p></div>
2367 </dd>
2368 <dt class="hdlist1">
2369 core.hideDotFiles
2370 </dt>
2371 <dd>
2372 <p>
2373         (Windows-only) If true, mark newly-created directories and files whose
2374         name starts with a dot as hidden.  If <em>dotGitOnly</em>, only the <code>.git/</code>
2375         directory is hidden, but no other files starting with a dot.  The
2376         default mode is <em>dotGitOnly</em>.
2377 </p>
2378 </dd>
2379 <dt class="hdlist1">
2380 core.ignoreCase
2381 </dt>
2382 <dd>
2383 <p>
2384         Internal variable which enables various workarounds to enable
2385         Git to work better on filesystems that are not case sensitive,
2386         like APFS, HFS+, FAT, NTFS, etc. For example, if a directory listing
2387         finds "makefile" when Git expects "Makefile", Git will assume
2388         it is really the same file, and continue to remember it as
2389         "Makefile".
2390 </p>
2391 <div class="paragraph"><p>The default is false, except <a href="git-clone.html">git-clone(1)</a> or <a href="git-init.html">git-init(1)</a>
2392 will probe and set core.ignoreCase true if appropriate when the repository
2393 is created.</p></div>
2394 <div class="paragraph"><p>Git relies on the proper configuration of this variable for your operating
2395 and file system. Modifying this value may result in unexpected behavior.</p></div>
2396 </dd>
2397 <dt class="hdlist1">
2398 core.precomposeUnicode
2399 </dt>
2400 <dd>
2401 <p>
2402         This option is only used by Mac OS implementation of Git.
2403         When core.precomposeUnicode=true, Git reverts the unicode decomposition
2404         of filenames done by Mac OS. This is useful when sharing a repository
2405         between Mac OS and Linux or Windows.
2406         (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7).
2407         When false, file names are handled fully transparent by Git,
2408         which is backward compatible with older versions of Git.
2409 </p>
2410 </dd>
2411 <dt class="hdlist1">
2412 core.protectHFS
2413 </dt>
2414 <dd>
2415 <p>
2416         If set to true, do not allow checkout of paths that would
2417         be considered equivalent to <code>.git</code> on an HFS+ filesystem.
2418         Defaults to <code>true</code> on Mac OS, and <code>false</code> elsewhere.
2419 </p>
2420 </dd>
2421 <dt class="hdlist1">
2422 core.protectNTFS
2423 </dt>
2424 <dd>
2425 <p>
2426         If set to true, do not allow checkout of paths that would
2427         cause problems with the NTFS filesystem, e.g. conflict with
2428         8.3 "short" names.
2429         Defaults to <code>true</code> on Windows, and <code>false</code> elsewhere.
2430 </p>
2431 </dd>
2432 <dt class="hdlist1">
2433 core.fsmonitor
2434 </dt>
2435 <dd>
2436 <p>
2437         If set to true, enable the built-in file system monitor
2438         daemon for this working directory (<a href="git-fsmonitor&#45;&#45;daemon.html">git-fsmonitor&#45;&#45;daemon(1)</a>).
2439 </p>
2440 <div class="paragraph"><p>Like hook-based file system monitors, the built-in file system monitor
2441 can speed up Git commands that need to refresh the Git index
2442 (e.g. <code>git status</code>) in a working directory with many files.  The
2443 built-in monitor eliminates the need to install and maintain an
2444 external third-party tool.</p></div>
2445 <div class="paragraph"><p>The built-in file system monitor is currently available only on a
2446 limited set of supported platforms.  Currently, this includes Windows
2447 and MacOS.</p></div>
2448 <div class="literalblock">
2449 <div class="content">
2450 <pre><code>Otherwise, this variable contains the pathname of the "fsmonitor"
2451 hook command.</code></pre>
2452 </div></div>
2453 <div class="paragraph"><p>This hook command is used to identify all files that may have changed
2454 since the requested date/time. This information is used to speed up
2455 git by avoiding unnecessary scanning of files that have not changed.</p></div>
2456 <div class="paragraph"><p>See the "fsmonitor-watchman" section of <a href="githooks.html">githooks(5)</a>.</p></div>
2457 <div class="paragraph"><p>Note that if you concurrently use multiple versions of Git, such
2458 as one version on the command line and another version in an IDE
2459 tool, that the definition of <code>core.fsmonitor</code> was extended to
2460 allow boolean values in addition to hook pathnames.  Git versions
2461 2.35.1 and prior will not understand the boolean values and will
2462 consider the "true" or "false" values as hook pathnames to be
2463 invoked.  Git versions 2.26 thru 2.35.1 default to hook protocol
2464 V2 and will fall back to no fsmonitor (full scan).  Git versions
2465 prior to 2.26 default to hook protocol V1 and will silently
2466 assume there were no changes to report (no scan), so status
2467 commands may report incomplete results.  For this reason, it is
2468 best to upgrade all of your Git versions before using the built-in
2469 file system monitor.</p></div>
2470 </dd>
2471 <dt class="hdlist1">
2472 core.fsmonitorHookVersion
2473 </dt>
2474 <dd>
2475 <p>
2476         Sets the protocol version to be used when invoking the
2477         "fsmonitor" hook.
2478 </p>
2479 <div class="paragraph"><p>There are currently versions 1 and 2. When this is not set,
2480 version 2 will be tried first and if it fails then version 1
2481 will be tried. Version 1 uses a timestamp as input to determine
2482 which files have changes since that time but some monitors
2483 like Watchman have race conditions when used with a timestamp.
2484 Version 2 uses an opaque string so that the monitor can return
2485 something that can be used to determine what files have changed
2486 without race conditions.</p></div>
2487 </dd>
2488 <dt class="hdlist1">
2489 core.trustctime
2490 </dt>
2491 <dd>
2492 <p>
2493         If false, the ctime differences between the index and the
2494         working tree are ignored; useful when the inode change time
2495         is regularly modified by something outside Git (file system
2496         crawlers and some backup systems).
2497         See <a href="git-update-index.html">git-update-index(1)</a>. True by default.
2498 </p>
2499 </dd>
2500 <dt class="hdlist1">
2501 core.splitIndex
2502 </dt>
2503 <dd>
2504 <p>
2505         If true, the split-index feature of the index will be used.
2506         See <a href="git-update-index.html">git-update-index(1)</a>. False by default.
2507 </p>
2508 </dd>
2509 <dt class="hdlist1">
2510 core.untrackedCache
2511 </dt>
2512 <dd>
2513 <p>
2514         Determines what to do about the untracked cache feature of the
2515         index. It will be kept, if this variable is unset or set to
2516         <code>keep</code>. It will automatically be added if set to <code>true</code>. And
2517         it will automatically be removed, if set to <code>false</code>. Before
2518         setting it to <code>true</code>, you should check that mtime is working
2519         properly on your system.
2520         See <a href="git-update-index.html">git-update-index(1)</a>. <code>keep</code> by default, unless
2521         <code>feature.manyFiles</code> is enabled which sets this setting to
2522         <code>true</code> by default.
2523 </p>
2524 </dd>
2525 <dt class="hdlist1">
2526 core.checkStat
2527 </dt>
2528 <dd>
2529 <p>
2530         When missing or is set to <code>default</code>, many fields in the stat
2531         structure are checked to detect if a file has been modified
2532         since Git looked at it.  When this configuration variable is
2533         set to <code>minimal</code>, sub-second part of mtime and ctime, the
2534         uid and gid of the owner of the file, the inode number (and
2535         the device number, if Git was compiled to use it), are
2536         excluded from the check among these fields, leaving only the
2537         whole-second part of mtime (and ctime, if <code>core.trustCtime</code>
2538         is set) and the filesize to be checked.
2539 </p>
2540 <div class="paragraph"><p>There are implementations of Git that do not leave usable values in
2541 some fields (e.g. JGit); by excluding these fields from the
2542 comparison, the <code>minimal</code> mode may help interoperability when the
2543 same repository is used by these other systems at the same time.</p></div>
2544 </dd>
2545 <dt class="hdlist1">
2546 core.quotePath
2547 </dt>
2548 <dd>
2549 <p>
2550         Commands that output paths (e.g. <em>ls-files</em>, <em>diff</em>), will
2551         quote "unusual" characters in the pathname by enclosing the
2552         pathname in double-quotes and escaping those characters with
2553         backslashes in the same way C escapes control characters (e.g.
2554         <code>\t</code> for TAB, <code>\n</code> for LF, <code>\\</code> for backslash) or bytes with
2555         values larger than 0x80 (e.g. octal <code>\302\265</code> for "micro" in
2556         UTF-8).  If this variable is set to false, bytes higher than
2557         0x80 are not considered "unusual" any more. Double-quotes,
2558         backslash and control characters are always escaped regardless
2559         of the setting of this variable.  A simple space character is
2560         not considered "unusual".  Many commands can output pathnames
2561         completely verbatim using the <code>-z</code> option. The default value
2562         is true.
2563 </p>
2564 </dd>
2565 <dt class="hdlist1">
2566 core.eol
2567 </dt>
2568 <dd>
2569 <p>
2570         Sets the line ending type to use in the working directory for
2571         files that are marked as text (either by having the <code>text</code>
2572         attribute set, or by having <code>text=auto</code> and Git auto-detecting
2573         the contents as text).
2574         Alternatives are <em>lf</em>, <em>crlf</em> and <em>native</em>, which uses the platform&#8217;s
2575         native line ending.  The default value is <code>native</code>.  See
2576         <a href="gitattributes.html">gitattributes(5)</a> for more information on end-of-line
2577         conversion. Note that this value is ignored if <code>core.autocrlf</code>
2578         is set to <code>true</code> or <code>input</code>.
2579 </p>
2580 </dd>
2581 <dt class="hdlist1">
2582 core.safecrlf
2583 </dt>
2584 <dd>
2585 <p>
2586         If true, makes Git check if converting <code>CRLF</code> is reversible when
2587         end-of-line conversion is active.  Git will verify if a command
2588         modifies a file in the work tree either directly or indirectly.
2589         For example, committing a file followed by checking out the
2590         same file should yield the original file in the work tree.  If
2591         this is not the case for the current setting of
2592         <code>core.autocrlf</code>, Git will reject the file.  The variable can
2593         be set to "warn", in which case Git will only warn about an
2594         irreversible conversion but continue the operation.
2595 </p>
2596 <div class="paragraph"><p>CRLF conversion bears a slight chance of corrupting data.
2597 When it is enabled, Git will convert CRLF to LF during commit and LF to
2598 CRLF during checkout.  A file that contains a mixture of LF and
2599 CRLF before the commit cannot be recreated by Git.  For text
2600 files this is the right thing to do: it corrects line endings
2601 such that we have only LF line endings in the repository.
2602 But for binary files that are accidentally classified as text the
2603 conversion can corrupt data.</p></div>
2604 <div class="paragraph"><p>If you recognize such corruption early you can easily fix it by
2605 setting the conversion type explicitly in .gitattributes.  Right
2606 after committing you still have the original file in your work
2607 tree and this file is not yet corrupted.  You can explicitly tell
2608 Git that this file is binary and Git will handle the file
2609 appropriately.</p></div>
2610 <div class="paragraph"><p>Unfortunately, the desired effect of cleaning up text files with
2611 mixed line endings and the undesired effect of corrupting binary
2612 files cannot be distinguished.  In both cases CRLFs are removed
2613 in an irreversible way.  For text files this is the right thing
2614 to do because CRLFs are line endings, while for binary files
2615 converting CRLFs corrupts data.</p></div>
2616 <div class="paragraph"><p>Note, this safety check does not mean that a checkout will generate a
2617 file identical to the original file for a different setting of
2618 <code>core.eol</code> and <code>core.autocrlf</code>, but only for the current one.  For
2619 example, a text file with <code>LF</code> would be accepted with <code>core.eol=lf</code>
2620 and could later be checked out with <code>core.eol=crlf</code>, in which case the
2621 resulting file would contain <code>CRLF</code>, although the original file
2622 contained <code>LF</code>.  However, in both work trees the line endings would be
2623 consistent, that is either all <code>LF</code> or all <code>CRLF</code>, but never mixed.  A
2624 file with mixed line endings would be reported by the <code>core.safecrlf</code>
2625 mechanism.</p></div>
2626 </dd>
2627 <dt class="hdlist1">
2628 core.autocrlf
2629 </dt>
2630 <dd>
2631 <p>
2632         Setting this variable to "true" is the same as setting
2633         the <code>text</code> attribute to "auto" on all files and core.eol to "crlf".
2634         Set to true if you want to have <code>CRLF</code> line endings in your
2635         working directory and the repository has LF line endings.
2636         This variable can be set to <em>input</em>,
2637         in which case no output conversion is performed.
2638 </p>
2639 </dd>
2640 <dt class="hdlist1">
2641 core.checkRoundtripEncoding
2642 </dt>
2643 <dd>
2644 <p>
2645         A comma and/or whitespace separated list of encodings that Git
2646         performs UTF-8 round trip checks on if they are used in an
2647         <code>working-tree-encoding</code> attribute (see <a href="gitattributes.html">gitattributes(5)</a>).
2648         The default value is <code>SHIFT-JIS</code>.
2649 </p>
2650 </dd>
2651 <dt class="hdlist1">
2652 core.symlinks
2653 </dt>
2654 <dd>
2655 <p>
2656         If false, symbolic links are checked out as small plain files that
2657         contain the link text. <a href="git-update-index.html">git-update-index(1)</a> and
2658         <a href="git-add.html">git-add(1)</a> will not change the recorded type to regular
2659         file. Useful on filesystems like FAT that do not support
2660         symbolic links.
2661 </p>
2662 <div class="paragraph"><p>The default is true, except <a href="git-clone.html">git-clone(1)</a> or <a href="git-init.html">git-init(1)</a>
2663 will probe and set core.symlinks false if appropriate when the repository
2664 is created.</p></div>
2665 </dd>
2666 <dt class="hdlist1">
2667 core.gitProxy
2668 </dt>
2669 <dd>
2670 <p>
2671         A "proxy command" to execute (as <em>command host port</em>) instead
2672         of establishing direct connection to the remote server when
2673         using the Git protocol for fetching. If the variable value is
2674         in the "COMMAND for DOMAIN" format, the command is applied only
2675         on hostnames ending with the specified domain string. This variable
2676         may be set multiple times and is matched in the given order;
2677         the first match wins.
2678 </p>
2679 <div class="paragraph"><p>Can be overridden by the <code>GIT_PROXY_COMMAND</code> environment variable
2680 (which always applies universally, without the special "for"
2681 handling).</p></div>
2682 <div class="paragraph"><p>The special string <code>none</code> can be used as the proxy command to
2683 specify that no proxy be used for a given domain pattern.
2684 This is useful for excluding servers inside a firewall from
2685 proxy use, while defaulting to a common proxy for external domains.</p></div>
2686 </dd>
2687 <dt class="hdlist1">
2688 core.sshCommand
2689 </dt>
2690 <dd>
2691 <p>
2692         If this variable is set, <code>git fetch</code> and <code>git push</code> will
2693         use the specified command instead of <code>ssh</code> when they need to
2694         connect to a remote system. The command is in the same form as
2695         the <code>GIT_SSH_COMMAND</code> environment variable and is overridden
2696         when the environment variable is set.
2697 </p>
2698 </dd>
2699 <dt class="hdlist1">
2700 core.ignoreStat
2701 </dt>
2702 <dd>
2703 <p>
2704         If true, Git will avoid using lstat() calls to detect if files have
2705         changed by setting the "assume-unchanged" bit for those tracked files
2706         which it has updated identically in both the index and working tree.
2707 </p>
2708 <div class="paragraph"><p>When files are modified outside of Git, the user will need to stage
2709 the modified files explicitly (e.g. see <em>Examples</em> section in
2710 <a href="git-update-index.html">git-update-index(1)</a>).
2711 Git will not normally detect changes to those files.</p></div>
2712 <div class="paragraph"><p>This is useful on systems where lstat() calls are very slow, such as
2713 CIFS/Microsoft Windows.</p></div>
2714 <div class="paragraph"><p>False by default.</p></div>
2715 </dd>
2716 <dt class="hdlist1">
2717 core.preferSymlinkRefs
2718 </dt>
2719 <dd>
2720 <p>
2721         Instead of the default "symref" format for HEAD
2722         and other symbolic reference files, use symbolic links.
2723         This is sometimes needed to work with old scripts that
2724         expect HEAD to be a symbolic link.
2725 </p>
2726 </dd>
2727 <dt class="hdlist1">
2728 core.alternateRefsCommand
2729 </dt>
2730 <dd>
2731 <p>
2732         When advertising tips of available history from an alternate, use the shell to
2733         execute the specified command instead of <a href="git-for-each-ref.html">git-for-each-ref(1)</a>. The
2734         first argument is the absolute path of the alternate. Output must contain one
2735         hex object id per line (i.e., the same as produced by <code>git for-each-ref
2736         --format='%(objectname)'</code>).
2737 </p>
2738 <div class="paragraph"><p>Note that you cannot generally put <code>git for-each-ref</code> directly into the config
2739 value, as it does not take a repository path as an argument (but you can wrap
2740 the command above in a shell script).</p></div>
2741 </dd>
2742 <dt class="hdlist1">
2743 core.alternateRefsPrefixes
2744 </dt>
2745 <dd>
2746 <p>
2747         When listing references from an alternate, list only references that begin
2748         with the given prefix. Prefixes match as if they were given as arguments to
2749         <a href="git-for-each-ref.html">git-for-each-ref(1)</a>. To list multiple prefixes, separate them with
2750         whitespace. If <code>core.alternateRefsCommand</code> is set, setting
2751         <code>core.alternateRefsPrefixes</code> has no effect.
2752 </p>
2753 </dd>
2754 <dt class="hdlist1">
2755 core.bare
2756 </dt>
2757 <dd>
2758 <p>
2759         If true this repository is assumed to be <em>bare</em> and has no
2760         working directory associated with it.  If this is the case a
2761         number of commands that require a working directory will be
2762         disabled, such as <a href="git-add.html">git-add(1)</a> or <a href="git-merge.html">git-merge(1)</a>.
2763 </p>
2764 <div class="paragraph"><p>This setting is automatically guessed by <a href="git-clone.html">git-clone(1)</a> or
2765 <a href="git-init.html">git-init(1)</a> when the repository was created.  By default a
2766 repository that ends in "/.git" is assumed to be not bare (bare =
2767 false), while all other repositories are assumed to be bare (bare
2768 = true).</p></div>
2769 </dd>
2770 <dt class="hdlist1">
2771 core.worktree
2772 </dt>
2773 <dd>
2774 <p>
2775         Set the path to the root of the working tree.
2776         If <code>GIT_COMMON_DIR</code> environment variable is set, core.worktree
2777         is ignored and not used for determining the root of working tree.
2778         This can be overridden by the <code>GIT_WORK_TREE</code> environment
2779         variable and the <code>--work-tree</code> command-line option.
2780         The value can be an absolute path or relative to the path to
2781         the .git directory, which is either specified by --git-dir
2782         or GIT_DIR, or automatically discovered.
2783         If --git-dir or GIT_DIR is specified but none of
2784         --work-tree, GIT_WORK_TREE and core.worktree is specified,
2785         the current working directory is regarded as the top level
2786         of your working tree.
2787 </p>
2788 <div class="paragraph"><p>Note that this variable is honored even when set in a configuration
2789 file in a ".git" subdirectory of a directory and its value differs
2790 from the latter directory (e.g. "/path/to/.git/config" has
2791 core.worktree set to "/different/path"), which is most likely a
2792 misconfiguration.  Running Git commands in the "/path/to" directory will
2793 still use "/different/path" as the root of the work tree and can cause
2794 confusion unless you know what you are doing (e.g. you are creating a
2795 read-only snapshot of the same index to a location different from the
2796 repository&#8217;s usual working tree).</p></div>
2797 </dd>
2798 <dt class="hdlist1">
2799 core.logAllRefUpdates
2800 </dt>
2801 <dd>
2802 <p>
2803         Enable the reflog. Updates to a ref &lt;ref&gt; is logged to the file
2804         "<code>$GIT_DIR/logs/&lt;ref&gt;</code>", by appending the new and old
2805         SHA-1, the date/time and the reason of the update, but
2806         only when the file exists.  If this configuration
2807         variable is set to <code>true</code>, missing "<code>$GIT_DIR/logs/&lt;ref&gt;</code>"
2808         file is automatically created for branch heads (i.e. under
2809         <code>refs/heads/</code>), remote refs (i.e. under <code>refs/remotes/</code>),
2810         note refs (i.e. under <code>refs/notes/</code>), and the symbolic ref <code>HEAD</code>.
2811         If it is set to <code>always</code>, then a missing reflog is automatically
2812         created for any ref under <code>refs/</code>.
2813 </p>
2814 <div class="paragraph"><p>This information can be used to determine what commit
2815 was the tip of a branch "2 days ago".</p></div>
2816 <div class="paragraph"><p>This value is true by default in a repository that has
2817 a working directory associated with it, and false by
2818 default in a bare repository.</p></div>
2819 </dd>
2820 <dt class="hdlist1">
2821 core.repositoryFormatVersion
2822 </dt>
2823 <dd>
2824 <p>
2825         Internal variable identifying the repository format and layout
2826         version.
2827 </p>
2828 </dd>
2829 <dt class="hdlist1">
2830 core.sharedRepository
2831 </dt>
2832 <dd>
2833 <p>
2834         When <em>group</em> (or <em>true</em>), the repository is made shareable between
2835         several users in a group (making sure all the files and objects are
2836         group-writable). When <em>all</em> (or <em>world</em> or <em>everybody</em>), the
2837         repository will be readable by all users, additionally to being
2838         group-shareable. When <em>umask</em> (or <em>false</em>), Git will use permissions
2839         reported by umask(2). When <em>0xxx</em>, where <em>0xxx</em> is an octal number,
2840         files in the repository will have this mode value. <em>0xxx</em> will override
2841         user&#8217;s umask value (whereas the other options will only override
2842         requested parts of the user&#8217;s umask value). Examples: <em>0660</em> will make
2843         the repo read/write-able for the owner and group, but inaccessible to
2844         others (equivalent to <em>group</em> unless umask is e.g. <em>0022</em>). <em>0640</em> is a
2845         repository that is group-readable but not group-writable.
2846         See <a href="git-init.html">git-init(1)</a>. False by default.
2847 </p>
2848 </dd>
2849 <dt class="hdlist1">
2850 core.warnAmbiguousRefs
2851 </dt>
2852 <dd>
2853 <p>
2854         If true, Git will warn you if the ref name you passed it is ambiguous
2855         and might match multiple refs in the repository. True by default.
2856 </p>
2857 </dd>
2858 <dt class="hdlist1">
2859 core.compression
2860 </dt>
2861 <dd>
2862 <p>
2863         An integer -1..9, indicating a default compression level.
2864         -1 is the zlib default. 0 means no compression,
2865         and 1..9 are various speed/size tradeoffs, 9 being slowest.
2866         If set, this provides a default to other compression variables,
2867         such as <code>core.looseCompression</code> and <code>pack.compression</code>.
2868 </p>
2869 </dd>
2870 <dt class="hdlist1">
2871 core.looseCompression
2872 </dt>
2873 <dd>
2874 <p>
2875         An integer -1..9, indicating the compression level for objects that
2876         are not in a pack file. -1 is the zlib default. 0 means no
2877         compression, and 1..9 are various speed/size tradeoffs, 9 being
2878         slowest.  If not set,  defaults to core.compression.  If that is
2879         not set,  defaults to 1 (best speed).
2880 </p>
2881 </dd>
2882 <dt class="hdlist1">
2883 core.packedGitWindowSize
2884 </dt>
2885 <dd>
2886 <p>
2887         Number of bytes of a pack file to map into memory in a
2888         single mapping operation.  Larger window sizes may allow
2889         your system to process a smaller number of large pack files
2890         more quickly.  Smaller window sizes will negatively affect
2891         performance due to increased calls to the operating system&#8217;s
2892         memory manager, but may improve performance when accessing
2893         a large number of large pack files.
2894 </p>
2895 <div class="paragraph"><p>Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
2896 MiB on 32 bit platforms and 1 GiB on 64 bit platforms.  This should
2897 be reasonable for all users/operating systems.  You probably do
2898 not need to adjust this value.</p></div>
2899 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
2900 </dd>
2901 <dt class="hdlist1">
2902 core.packedGitLimit
2903 </dt>
2904 <dd>
2905 <p>
2906         Maximum number of bytes to map simultaneously into memory
2907         from pack files.  If Git needs to access more than this many
2908         bytes at once to complete an operation it will unmap existing
2909         regions to reclaim virtual address space within the process.
2910 </p>
2911 <div class="paragraph"><p>Default is 256 MiB on 32 bit platforms and 32 TiB (effectively
2912 unlimited) on 64 bit platforms.
2913 This should be reasonable for all users/operating systems, except on
2914 the largest projects.  You probably do not need to adjust this value.</p></div>
2915 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
2916 </dd>
2917 <dt class="hdlist1">
2918 core.deltaBaseCacheLimit
2919 </dt>
2920 <dd>
2921 <p>
2922         Maximum number of bytes per thread to reserve for caching base objects
2923         that may be referenced by multiple deltified objects.  By storing the
2924         entire decompressed base objects in a cache Git is able
2925         to avoid unpacking and decompressing frequently used base
2926         objects multiple times.
2927 </p>
2928 <div class="paragraph"><p>Default is 96 MiB on all platforms.  This should be reasonable
2929 for all users/operating systems, except on the largest projects.
2930 You probably do not need to adjust this value.</p></div>
2931 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
2932 </dd>
2933 <dt class="hdlist1">
2934 core.bigFileThreshold
2935 </dt>
2936 <dd>
2937 <p>
2938         The size of files considered "big", which as discussed below
2939         changes the behavior of numerous git commands, as well as how
2940         such files are stored within the repository. The default is
2941         512 MiB. Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are
2942         supported.
2943 </p>
2944 <div class="paragraph"><p>Files above the configured limit will be:</p></div>
2945 <div class="ulist"><ul>
2946 <li>
2947 <p>
2948 Stored deflated in packfiles, without attempting delta compression.
2949 </p>
2950 <div class="paragraph"><p>The default limit is primarily set with this use-case in mind. With it,
2951 most projects will have their source code and other text files delta
2952 compressed, but not larger binary media files.</p></div>
2953 <div class="paragraph"><p>Storing large files without delta compression avoids excessive memory
2954 usage, at the slight expense of increased disk usage.</p></div>
2955 </li>
2956 <li>
2957 <p>
2958 Will be treated as if they were labeled "binary" (see
2959   <a href="gitattributes.html">gitattributes(5)</a>). e.g. <a href="git-log.html">git-log(1)</a> and
2960   <a href="git-diff.html">git-diff(1)</a> will not compute diffs for files above this limit.
2961 </p>
2962 </li>
2963 <li>
2964 <p>
2965 Will generally be streamed when written, which avoids excessive
2966 memory usage, at the cost of some fixed overhead. Commands that make
2967 use of this include <a href="git-archive.html">git-archive(1)</a>,
2968 <a href="git-fast-import.html">git-fast-import(1)</a>, <a href="git-index-pack.html">git-index-pack(1)</a>,
2969 <a href="git-unpack-objects.html">git-unpack-objects(1)</a> and <a href="git-fsck.html">git-fsck(1)</a>.
2970 </p>
2971 </li>
2972 </ul></div>
2973 </dd>
2974 <dt class="hdlist1">
2975 core.excludesFile
2976 </dt>
2977 <dd>
2978 <p>
2979         Specifies the pathname to the file that contains patterns to
2980         describe paths that are not meant to be tracked, in addition
2981         to <code>.gitignore</code> (per-directory) and <code>.git/info/exclude</code>.
2982         Defaults to <code>$XDG_CONFIG_HOME/git/ignore</code>.
2983         If <code>$XDG_CONFIG_HOME</code> is either not set or empty, <code>$HOME/.config/git/ignore</code>
2984         is used instead. See <a href="gitignore.html">gitignore(5)</a>.
2985 </p>
2986 </dd>
2987 <dt class="hdlist1">
2988 core.askPass
2989 </dt>
2990 <dd>
2991 <p>
2992         Some commands (e.g. svn and http interfaces) that interactively
2993         ask for a password can be told to use an external program given
2994         via the value of this variable. Can be overridden by the <code>GIT_ASKPASS</code>
2995         environment variable. If not set, fall back to the value of the
2996         <code>SSH_ASKPASS</code> environment variable or, failing that, a simple password
2997         prompt. The external program shall be given a suitable prompt as
2998         command-line argument and write the password on its STDOUT.
2999 </p>
3000 </dd>
3001 <dt class="hdlist1">
3002 core.attributesFile
3003 </dt>
3004 <dd>
3005 <p>
3006         In addition to <code>.gitattributes</code> (per-directory) and
3007         <code>.git/info/attributes</code>, Git looks into this file for attributes
3008         (see <a href="gitattributes.html">gitattributes(5)</a>). Path expansions are made the same
3009         way as for <code>core.excludesFile</code>. Its default value is
3010         <code>$XDG_CONFIG_HOME/git/attributes</code>. If <code>$XDG_CONFIG_HOME</code> is either not
3011         set or empty, <code>$HOME/.config/git/attributes</code> is used instead.
3012 </p>
3013 </dd>
3014 <dt class="hdlist1">
3015 core.hooksPath
3016 </dt>
3017 <dd>
3018 <p>
3019         By default Git will look for your hooks in the
3020         <code>$GIT_DIR/hooks</code> directory. Set this to different path,
3021         e.g. <code>/etc/git/hooks</code>, and Git will try to find your hooks in
3022         that directory, e.g. <code>/etc/git/hooks/pre-receive</code> instead of
3023         in <code>$GIT_DIR/hooks/pre-receive</code>.
3024 </p>
3025 <div class="paragraph"><p>The path can be either absolute or relative. A relative path is
3026 taken as relative to the directory where the hooks are run (see
3027 the "DESCRIPTION" section of <a href="githooks.html">githooks(5)</a>).</p></div>
3028 <div class="paragraph"><p>This configuration variable is useful in cases where you&#8217;d like to
3029 centrally configure your Git hooks instead of configuring them on a
3030 per-repository basis, or as a more flexible and centralized
3031 alternative to having an <code>init.templateDir</code> where you&#8217;ve changed
3032 default hooks.</p></div>
3033 </dd>
3034 <dt class="hdlist1">
3035 core.editor
3036 </dt>
3037 <dd>
3038 <p>
3039         Commands such as <code>commit</code> and <code>tag</code> that let you edit
3040         messages by launching an editor use the value of this
3041         variable when it is set, and the environment variable
3042         <code>GIT_EDITOR</code> is not set.  See <a href="git-var.html">git-var(1)</a>.
3043 </p>
3044 </dd>
3045 <dt class="hdlist1">
3046 core.commentChar
3047 </dt>
3048 <dd>
3049 <p>
3050         Commands such as <code>commit</code> and <code>tag</code> that let you edit
3051         messages consider a line that begins with this character
3052         commented, and removes them after the editor returns
3053         (default <em>#</em>).
3054 </p>
3055 <div class="paragraph"><p>If set to "auto", <code>git-commit</code> would select a character that is not
3056 the beginning character of any line in existing commit messages.</p></div>
3057 </dd>
3058 <dt class="hdlist1">
3059 core.filesRefLockTimeout
3060 </dt>
3061 <dd>
3062 <p>
3063         The length of time, in milliseconds, to retry when trying to
3064         lock an individual reference. Value 0 means not to retry at
3065         all; -1 means to try indefinitely. Default is 100 (i.e.,
3066         retry for 100ms).
3067 </p>
3068 </dd>
3069 <dt class="hdlist1">
3070 core.packedRefsTimeout
3071 </dt>
3072 <dd>
3073 <p>
3074         The length of time, in milliseconds, to retry when trying to
3075         lock the <code>packed-refs</code> file. Value 0 means not to retry at
3076         all; -1 means to try indefinitely. Default is 1000 (i.e.,
3077         retry for 1 second).
3078 </p>
3079 </dd>
3080 <dt class="hdlist1">
3081 core.pager
3082 </dt>
3083 <dd>
3084 <p>
3085         Text viewer for use by Git commands (e.g., <em>less</em>).  The value
3086         is meant to be interpreted by the shell.  The order of preference
3087         is the <code>$GIT_PAGER</code> environment variable, then <code>core.pager</code>
3088         configuration, then <code>$PAGER</code>, and then the default chosen at
3089         compile time (usually <em>less</em>).
3090 </p>
3091 <div class="paragraph"><p>When the <code>LESS</code> environment variable is unset, Git sets it to <code>FRX</code>
3092 (if <code>LESS</code> environment variable is set, Git does not change it at
3093 all).  If you want to selectively override Git&#8217;s default setting
3094 for <code>LESS</code>, you can set <code>core.pager</code> to e.g. <code>less -S</code>.  This will
3095 be passed to the shell by Git, which will translate the final
3096 command to <code>LESS=FRX less -S</code>. The environment does not set the
3097 <code>S</code> option but the command line does, instructing less to truncate
3098 long lines. Similarly, setting <code>core.pager</code> to <code>less -+F</code> will
3099 deactivate the <code>F</code> option specified by the environment from the
3100 command-line, deactivating the "quit if one screen" behavior of
3101 <code>less</code>.  One can specifically activate some flags for particular
3102 commands: for example, setting <code>pager.blame</code> to <code>less -S</code> enables
3103 line truncation only for <code>git blame</code>.</p></div>
3104 <div class="paragraph"><p>Likewise, when the <code>LV</code> environment variable is unset, Git sets it
3105 to <code>-c</code>.  You can override this setting by exporting <code>LV</code> with
3106 another value or setting <code>core.pager</code> to <code>lv +c</code>.</p></div>
3107 </dd>
3108 <dt class="hdlist1">
3109 core.whitespace
3110 </dt>
3111 <dd>
3112 <p>
3113         A comma separated list of common whitespace problems to
3114         notice.  <em>git diff</em> will use <code>color.diff.whitespace</code> to
3115         highlight them, and <em>git apply --whitespace=error</em> will
3116         consider them as errors.  You can prefix <code>-</code> to disable
3117         any of them (e.g. <code>-trailing-space</code>):
3118 </p>
3119 <div class="ulist"><ul>
3120 <li>
3121 <p>
3122 <code>blank-at-eol</code> treats trailing whitespaces at the end of the line
3123   as an error (enabled by default).
3124 </p>
3125 </li>
3126 <li>
3127 <p>
3128 <code>space-before-tab</code> treats a space character that appears immediately
3129   before a tab character in the initial indent part of the line as an
3130   error (enabled by default).
3131 </p>
3132 </li>
3133 <li>
3134 <p>
3135 <code>indent-with-non-tab</code> treats a line that is indented with space
3136   characters instead of the equivalent tabs as an error (not enabled by
3137   default).
3138 </p>
3139 </li>
3140 <li>
3141 <p>
3142 <code>tab-in-indent</code> treats a tab character in the initial indent part of
3143   the line as an error (not enabled by default).
3144 </p>
3145 </li>
3146 <li>
3147 <p>
3148 <code>blank-at-eof</code> treats blank lines added at the end of file as an error
3149   (enabled by default).
3150 </p>
3151 </li>
3152 <li>
3153 <p>
3154 <code>trailing-space</code> is a short-hand to cover both <code>blank-at-eol</code> and
3155   <code>blank-at-eof</code>.
3156 </p>
3157 </li>
3158 <li>
3159 <p>
3160 <code>cr-at-eol</code> treats a carriage-return at the end of line as
3161   part of the line terminator, i.e. with it, <code>trailing-space</code>
3162   does not trigger if the character before such a carriage-return
3163   is not a whitespace (not enabled by default).
3164 </p>
3165 </li>
3166 <li>
3167 <p>
3168 <code>tabwidth=&lt;n&gt;</code> tells how many character positions a tab occupies; this
3169   is relevant for <code>indent-with-non-tab</code> and when Git fixes <code>tab-in-indent</code>
3170   errors. The default tab width is 8. Allowed values are 1 to 63.
3171 </p>
3172 </li>
3173 </ul></div>
3174 </dd>
3175 <dt class="hdlist1">
3176 core.fsync
3177 </dt>
3178 <dd>
3179 <p>
3180         A comma-separated list of components of the repository that
3181         should be hardened via the core.fsyncMethod when created or
3182         modified.  You can disable hardening of any component by
3183         prefixing it with a <em>-</em>.  Items that are not hardened may be
3184         lost in the event of an unclean system shutdown. Unless you
3185         have special requirements, it is recommended that you leave
3186         this option empty or pick one of <code>committed</code>, <code>added</code>,
3187         or <code>all</code>.
3188 </p>
3189 <div class="paragraph"><p>When this configuration is encountered, the set of components starts with
3190 the platform default value, disabled components are removed, and additional
3191 components are added. <code>none</code> resets the state so that the platform default
3192 is ignored.</p></div>
3193 <div class="paragraph"><p>The empty string resets the fsync configuration to the platform
3194 default. The default on most platforms is equivalent to
3195 <code>core.fsync=committed,-loose-object</code>, which has good performance,
3196 but risks losing recent work in the event of an unclean system shutdown.</p></div>
3197 <div class="ulist"><ul>
3198 <li>
3199 <p>
3200 <code>none</code> clears the set of fsynced components.
3201 </p>
3202 </li>
3203 <li>
3204 <p>
3205 <code>loose-object</code> hardens objects added to the repo in loose-object form.
3206 </p>
3207 </li>
3208 <li>
3209 <p>
3210 <code>pack</code> hardens objects added to the repo in packfile form.
3211 </p>
3212 </li>
3213 <li>
3214 <p>
3215 <code>pack-metadata</code> hardens packfile bitmaps and indexes.
3216 </p>
3217 </li>
3218 <li>
3219 <p>
3220 <code>commit-graph</code> hardens the commit-graph file.
3221 </p>
3222 </li>
3223 <li>
3224 <p>
3225 <code>index</code> hardens the index when it is modified.
3226 </p>
3227 </li>
3228 <li>
3229 <p>
3230 <code>objects</code> is an aggregate option that is equivalent to
3231   <code>loose-object,pack</code>.
3232 </p>
3233 </li>
3234 <li>
3235 <p>
3236 <code>reference</code> hardens references modified in the repo.
3237 </p>
3238 </li>
3239 <li>
3240 <p>
3241 <code>derived-metadata</code> is an aggregate option that is equivalent to
3242   <code>pack-metadata,commit-graph</code>.
3243 </p>
3244 </li>
3245 <li>
3246 <p>
3247 <code>committed</code> is an aggregate option that is currently equivalent to
3248   <code>objects</code>. This mode sacrifices some performance to ensure that work
3249   that is committed to the repository with <code>git commit</code> or similar commands
3250   is hardened.
3251 </p>
3252 </li>
3253 <li>
3254 <p>
3255 <code>added</code> is an aggregate option that is currently equivalent to
3256   <code>committed,index</code>. This mode sacrifices additional performance to
3257   ensure that the results of commands like <code>git add</code> and similar operations
3258   are hardened.
3259 </p>
3260 </li>
3261 <li>
3262 <p>
3263 <code>all</code> is an aggregate option that syncs all individual components above.
3264 </p>
3265 </li>
3266 </ul></div>
3267 </dd>
3268 <dt class="hdlist1">
3269 core.fsyncMethod
3270 </dt>
3271 <dd>
3272 <p>
3273         A value indicating the strategy Git will use to harden repository data
3274         using fsync and related primitives.
3275 </p>
3276 <div class="ulist"><ul>
3277 <li>
3278 <p>
3279 <code>fsync</code> uses the fsync() system call or platform equivalents.
3280 </p>
3281 </li>
3282 <li>
3283 <p>
3284 <code>writeout-only</code> issues pagecache writeback requests, but depending on the
3285   filesystem and storage hardware, data added to the repository may not be
3286   durable in the event of a system crash. This is the default mode on macOS.
3287 </p>
3288 </li>
3289 <li>
3290 <p>
3291 <code>batch</code> enables a mode that uses writeout-only flushes to stage multiple
3292   updates in the disk writeback cache and then does a single full fsync of
3293   a dummy file to trigger the disk cache flush at the end of the operation.
3294 </p>
3295 <div class="paragraph"><p>Currently <code>batch</code> mode only applies to loose-object files. Other repository
3296 data is made durable as if <code>fsync</code> was specified. This mode is expected to
3297 be as safe as <code>fsync</code> on macOS for repos stored on HFS+ or APFS filesystems
3298 and on Windows for repos stored on NTFS or ReFS filesystems.</p></div>
3299 </li>
3300 </ul></div>
3301 </dd>
3302 <dt class="hdlist1">
3303 core.fsyncObjectFiles
3304 </dt>
3305 <dd>
3306 <p>
3307         This boolean will enable <em>fsync()</em> when writing object files.
3308         This setting is deprecated. Use core.fsync instead.
3309 </p>
3310 <div class="paragraph"><p>This setting affects data added to the Git repository in loose-object
3311 form. When set to true, Git will issue an fsync or similar system call
3312 to flush caches so that loose-objects remain consistent in the face
3313 of a unclean system shutdown.</p></div>
3314 </dd>
3315 <dt class="hdlist1">
3316 core.preloadIndex
3317 </dt>
3318 <dd>
3319 <p>
3320         Enable parallel index preload for operations like <em>git diff</em>
3321 </p>
3322 <div class="paragraph"><p>This can speed up operations like <em>git diff</em> and <em>git status</em> especially
3323 on filesystems like NFS that have weak caching semantics and thus
3324 relatively high IO latencies.  When enabled, Git will do the
3325 index comparison to the filesystem data in parallel, allowing
3326 overlapping IO&#8217;s.  Defaults to true.</p></div>
3327 </dd>
3328 <dt class="hdlist1">
3329 core.unsetenvvars
3330 </dt>
3331 <dd>
3332 <p>
3333         Windows-only: comma-separated list of environment variables'
3334         names that need to be unset before spawning any other process.
3335         Defaults to <code>PERL5LIB</code> to account for the fact that Git for
3336         Windows insists on using its own Perl interpreter.
3337 </p>
3338 </dd>
3339 <dt class="hdlist1">
3340 core.restrictinheritedhandles
3341 </dt>
3342 <dd>
3343 <p>
3344         Windows-only: override whether spawned processes inherit only standard
3345         file handles (<code>stdin</code>, <code>stdout</code> and <code>stderr</code>) or all handles. Can be
3346         <code>auto</code>, <code>true</code> or <code>false</code>. Defaults to <code>auto</code>, which means <code>true</code> on
3347         Windows 7 and later, and <code>false</code> on older Windows versions.
3348 </p>
3349 </dd>
3350 <dt class="hdlist1">
3351 core.createObject
3352 </dt>
3353 <dd>
3354 <p>
3355         You can set this to <em>link</em>, in which case a hardlink followed by
3356         a delete of the source are used to make sure that object creation
3357         will not overwrite existing objects.
3358 </p>
3359 <div class="paragraph"><p>On some file system/operating system combinations, this is unreliable.
3360 Set this config setting to <em>rename</em> there; However, This will remove the
3361 check that makes sure that existing object files will not get overwritten.</p></div>
3362 </dd>
3363 <dt class="hdlist1">
3364 core.notesRef
3365 </dt>
3366 <dd>
3367 <p>
3368         When showing commit messages, also show notes which are stored in
3369         the given ref.  The ref must be fully qualified.  If the given
3370         ref does not exist, it is not an error but means that no
3371         notes should be printed.
3372 </p>
3373 <div class="paragraph"><p>This setting defaults to "refs/notes/commits", and it can be overridden by
3374 the <code>GIT_NOTES_REF</code> environment variable.  See <a href="git-notes.html">git-notes(1)</a>.</p></div>
3375 </dd>
3376 <dt class="hdlist1">
3377 core.commitGraph
3378 </dt>
3379 <dd>
3380 <p>
3381         If true, then git will read the commit-graph file (if it exists)
3382         to parse the graph structure of commits. Defaults to true. See
3383         <a href="git-commit-graph.html">git-commit-graph(1)</a> for more information.
3384 </p>
3385 </dd>
3386 <dt class="hdlist1">
3387 core.useReplaceRefs
3388 </dt>
3389 <dd>
3390 <p>
3391         If set to <code>false</code>, behave as if the <code>--no-replace-objects</code>
3392         option was given on the command line. See <a href="git.html">git(1)</a> and
3393         <a href="git-replace.html">git-replace(1)</a> for more information.
3394 </p>
3395 </dd>
3396 <dt class="hdlist1">
3397 core.multiPackIndex
3398 </dt>
3399 <dd>
3400 <p>
3401         Use the multi-pack-index file to track multiple packfiles using a
3402         single index. See <a href="git-multi-pack-index.html">git-multi-pack-index(1)</a> for more
3403         information. Defaults to true.
3404 </p>
3405 </dd>
3406 <dt class="hdlist1">
3407 core.sparseCheckout
3408 </dt>
3409 <dd>
3410 <p>
3411         Enable "sparse checkout" feature. See <a href="git-sparse-checkout.html">git-sparse-checkout(1)</a>
3412         for more information.
3413 </p>
3414 </dd>
3415 <dt class="hdlist1">
3416 core.sparseCheckoutCone
3417 </dt>
3418 <dd>
3419 <p>
3420         Enables the "cone mode" of the sparse checkout feature. When the
3421         sparse-checkout file contains a limited set of patterns, this
3422         mode provides significant performance advantages. The "non-cone
3423         mode" can be requested to allow specifying more flexible
3424         patterns by setting this variable to <em>false</em>. See
3425         <a href="git-sparse-checkout.html">git-sparse-checkout(1)</a> for more information.
3426 </p>
3427 </dd>
3428 <dt class="hdlist1">
3429 core.abbrev
3430 </dt>
3431 <dd>
3432 <p>
3433         Set the length object names are abbreviated to.  If
3434         unspecified or set to "auto", an appropriate value is
3435         computed based on the approximate number of packed objects
3436         in your repository, which hopefully is enough for
3437         abbreviated object names to stay unique for some time.
3438         If set to "no", no abbreviation is made and the object names
3439         are shown in their full length.
3440         The minimum length is 4.
3441 </p>
3442 </dd>
3443 <dt class="hdlist1">
3444 core.maxTreeDepth
3445 </dt>
3446 <dd>
3447 <p>
3448         The maximum depth Git is willing to recurse while traversing a
3449         tree (e.g., "a/b/cde/f" has a depth of 4). This is a fail-safe
3450         to allow Git to abort cleanly, and should not generally need to
3451         be adjusted. The default is 4096.
3452 </p>
3453 </dd>
3454 <dt class="hdlist1">
3455 add.ignoreErrors
3456 </dt>
3457 <dt class="hdlist1">
3458 add.ignore-errors (deprecated)
3459 </dt>
3460 <dd>
3461 <p>
3462         Tells <em>git add</em> to continue adding files when some files cannot be
3463         added due to indexing errors. Equivalent to the <code>--ignore-errors</code>
3464         option of <a href="git-add.html">git-add(1)</a>.  <code>add.ignore-errors</code> is deprecated,
3465         as it does not follow the usual naming convention for configuration
3466         variables.
3467 </p>
3468 </dd>
3469 <dt class="hdlist1">
3470 add.interactive.useBuiltin
3471 </dt>
3472 <dd>
3473 <p>
3474         Unused configuration variable. Used in Git versions v2.25.0 to
3475         v2.36.0 to enable the built-in version of <a href="git-add.html">git-add(1)</a>'s
3476         interactive mode, which then became the default in Git
3477         versions v2.37.0 to v2.39.0.
3478 </p>
3479 </dd>
3480 <dt class="hdlist1">
3481 alias.*
3482 </dt>
3483 <dd>
3484 <p>
3485         Command aliases for the <a href="git.html">git(1)</a> command wrapper - e.g.
3486         after defining <code>alias.last = cat-file commit HEAD</code>, the invocation
3487         <code>git last</code> is equivalent to <code>git cat-file commit HEAD</code>. To avoid
3488         confusion and troubles with script usage, aliases that
3489         hide existing Git commands are ignored. Arguments are split by
3490         spaces, the usual shell quoting and escaping is supported.
3491         A quote pair or a backslash can be used to quote them.
3492 </p>
3493 <div class="paragraph"><p>Note that the first word of an alias does not necessarily have to be a
3494 command. It can be a command-line option that will be passed into the
3495 invocation of <code>git</code>. In particular, this is useful when used with <code>-c</code>
3496 to pass in one-time configurations or <code>-p</code> to force pagination. For example,
3497 <code>loud-rebase = -c commit.verbose=true rebase</code> can be defined such that
3498 running <code>git loud-rebase</code> would be equivalent to
3499 <code>git -c commit.verbose=true rebase</code>. Also, <code>ps = -p status</code> would be a
3500 helpful alias since <code>git ps</code> would paginate the output of <code>git status</code>
3501 where the original command does not.</p></div>
3502 <div class="paragraph"><p>If the alias expansion is prefixed with an exclamation point,
3503 it will be treated as a shell command.  For example, defining
3504 <code>alias.new = !gitk --all --not ORIG_HEAD</code>, the invocation
3505 <code>git new</code> is equivalent to running the shell command
3506 <code>gitk --all --not ORIG_HEAD</code>.  Note that shell commands will be
3507 executed from the top-level directory of a repository, which may
3508 not necessarily be the current directory.
3509 <code>GIT_PREFIX</code> is set as returned by running <code>git rev-parse --show-prefix</code>
3510 from the original current directory. See <a href="git-rev-parse.html">git-rev-parse(1)</a>.</p></div>
3511 </dd>
3512 <dt class="hdlist1">
3513 am.keepcr
3514 </dt>
3515 <dd>
3516 <p>
3517         If true, git-am will call git-mailsplit for patches in mbox format
3518         with parameter <code>--keep-cr</code>. In this case git-mailsplit will
3519         not remove <code>\r</code> from lines ending with <code>\r\n</code>. Can be overridden
3520         by giving <code>--no-keep-cr</code> from the command line.
3521         See <a href="git-am.html">git-am(1)</a>, <a href="git-mailsplit.html">git-mailsplit(1)</a>.
3522 </p>
3523 </dd>
3524 <dt class="hdlist1">
3525 am.threeWay
3526 </dt>
3527 <dd>
3528 <p>
3529         By default, <code>git am</code> will fail if the patch does not apply cleanly. When
3530         set to true, this setting tells <code>git am</code> to fall back on 3-way merge if
3531         the patch records the identity of blobs it is supposed to apply to and
3532         we have those blobs available locally (equivalent to giving the <code>--3way</code>
3533         option from the command line). Defaults to <code>false</code>.
3534         See <a href="git-am.html">git-am(1)</a>.
3535 </p>
3536 </dd>
3537 <dt class="hdlist1">
3538 apply.ignoreWhitespace
3539 </dt>
3540 <dd>
3541 <p>
3542         When set to <em>change</em>, tells <em>git apply</em> to ignore changes in
3543         whitespace, in the same way as the <code>--ignore-space-change</code>
3544         option.
3545         When set to one of: no, none, never, false tells <em>git apply</em> to
3546         respect all whitespace differences.
3547         See <a href="git-apply.html">git-apply(1)</a>.
3548 </p>
3549 </dd>
3550 <dt class="hdlist1">
3551 apply.whitespace
3552 </dt>
3553 <dd>
3554 <p>
3555         Tells <em>git apply</em> how to handle whitespaces, in the same way
3556         as the <code>--whitespace</code> option. See <a href="git-apply.html">git-apply(1)</a>.
3557 </p>
3558 </dd>
3559 <dt class="hdlist1">
3560 blame.blankBoundary
3561 </dt>
3562 <dd>
3563 <p>
3564         Show blank commit object name for boundary commits in
3565         <a href="git-blame.html">git-blame(1)</a>. This option defaults to false.
3566 </p>
3567 </dd>
3568 <dt class="hdlist1">
3569 blame.coloring
3570 </dt>
3571 <dd>
3572 <p>
3573         This determines the coloring scheme to be applied to blame
3574         output. It can be <em>repeatedLines</em>, <em>highlightRecent</em>,
3575         or <em>none</em> which is the default.
3576 </p>
3577 </dd>
3578 <dt class="hdlist1">
3579 blame.date
3580 </dt>
3581 <dd>
3582 <p>
3583         Specifies the format used to output dates in <a href="git-blame.html">git-blame(1)</a>.
3584         If unset the iso format is used. For supported values,
3585         see the discussion of the <code>--date</code> option at <a href="git-log.html">git-log(1)</a>.
3586 </p>
3587 </dd>
3588 <dt class="hdlist1">
3589 blame.showEmail
3590 </dt>
3591 <dd>
3592 <p>
3593         Show the author email instead of author name in <a href="git-blame.html">git-blame(1)</a>.
3594         This option defaults to false.
3595 </p>
3596 </dd>
3597 <dt class="hdlist1">
3598 blame.showRoot
3599 </dt>
3600 <dd>
3601 <p>
3602         Do not treat root commits as boundaries in <a href="git-blame.html">git-blame(1)</a>.
3603         This option defaults to false.
3604 </p>
3605 </dd>
3606 <dt class="hdlist1">
3607 blame.ignoreRevsFile
3608 </dt>
3609 <dd>
3610 <p>
3611         Ignore revisions listed in the file, one unabbreviated object name per
3612         line, in <a href="git-blame.html">git-blame(1)</a>.  Whitespace and comments beginning with
3613         <code>#</code> are ignored.  This option may be repeated multiple times.  Empty
3614         file names will reset the list of ignored revisions.  This option will
3615         be handled before the command line option <code>--ignore-revs-file</code>.
3616 </p>
3617 </dd>
3618 <dt class="hdlist1">
3619 blame.markUnblamableLines
3620 </dt>
3621 <dd>
3622 <p>
3623         Mark lines that were changed by an ignored revision that we could not
3624         attribute to another commit with a <em>*</em> in the output of
3625         <a href="git-blame.html">git-blame(1)</a>.
3626 </p>
3627 </dd>
3628 <dt class="hdlist1">
3629 blame.markIgnoredLines
3630 </dt>
3631 <dd>
3632 <p>
3633         Mark lines that were changed by an ignored revision that we attributed to
3634         another commit with a <em>?</em> in the output of <a href="git-blame.html">git-blame(1)</a>.
3635 </p>
3636 </dd>
3637 <dt class="hdlist1">
3638 branch.autoSetupMerge
3639 </dt>
3640 <dd>
3641 <p>
3642         Tells <em>git branch</em>, <em>git switch</em> and <em>git checkout</em> to set up new branches
3643         so that <a href="git-pull.html">git-pull(1)</a> will appropriately merge from the
3644         starting point branch. Note that even if this option is not set,
3645         this behavior can be chosen per-branch using the <code>--track</code>
3646         and <code>--no-track</code> options. The valid settings are: <code>false</code>&#8201;&#8212;&#8201;no
3647         automatic setup is done; <code>true</code>&#8201;&#8212;&#8201;automatic setup is done when the
3648         starting point is a remote-tracking branch; <code>always</code>&#8201;&#8212;&#8201;        automatic setup is done when the starting point is either a
3649         local branch or remote-tracking branch; <code>inherit</code>&#8201;&#8212;&#8201;if the starting point
3650         has a tracking configuration, it is copied to the new
3651         branch; <code>simple</code>&#8201;&#8212;&#8201;automatic setup is done only when the starting point
3652         is a remote-tracking branch and the new branch has the same name as the
3653         remote branch. This option defaults to true.
3654 </p>
3655 </dd>
3656 <dt class="hdlist1">
3657 branch.autoSetupRebase
3658 </dt>
3659 <dd>
3660 <p>
3661         When a new branch is created with <em>git branch</em>, <em>git switch</em> or <em>git checkout</em>
3662         that tracks another branch, this variable tells Git to set
3663         up pull to rebase instead of merge (see "branch.&lt;name&gt;.rebase").
3664         When <code>never</code>, rebase is never automatically set to true.
3665         When <code>local</code>, rebase is set to true for tracked branches of
3666         other local branches.
3667         When <code>remote</code>, rebase is set to true for tracked branches of
3668         remote-tracking branches.
3669         When <code>always</code>, rebase will be set to true for all tracking
3670         branches.
3671         See "branch.autoSetupMerge" for details on how to set up a
3672         branch to track another branch.
3673         This option defaults to never.
3674 </p>
3675 </dd>
3676 <dt class="hdlist1">
3677 branch.sort
3678 </dt>
3679 <dd>
3680 <p>
3681         This variable controls the sort ordering of branches when displayed by
3682         <a href="git-branch.html">git-branch(1)</a>. Without the "--sort=&lt;value&gt;" option provided, the
3683         value of this variable will be used as the default.
3684         See <a href="git-for-each-ref.html">git-for-each-ref(1)</a> field names for valid values.
3685 </p>
3686 </dd>
3687 <dt class="hdlist1">
3688 branch.&lt;name&gt;.remote
3689 </dt>
3690 <dd>
3691 <p>
3692         When on branch &lt;name&gt;, it tells <em>git fetch</em> and <em>git push</em>
3693         which remote to fetch from/push to.  The remote to push to
3694         may be overridden with <code>remote.pushDefault</code> (for all branches).
3695         The remote to push to, for the current branch, may be further
3696         overridden by <code>branch.&lt;name&gt;.pushRemote</code>.  If no remote is
3697         configured, or if you are not on any branch and there is more than
3698         one remote defined in the repository, it defaults to <code>origin</code> for
3699         fetching and <code>remote.pushDefault</code> for pushing.
3700         Additionally, <code>.</code> (a period) is the current local repository
3701         (a dot-repository), see <code>branch.&lt;name&gt;.merge</code>'s final note below.
3702 </p>
3703 </dd>
3704 <dt class="hdlist1">
3705 branch.&lt;name&gt;.pushRemote
3706 </dt>
3707 <dd>
3708 <p>
3709         When on branch &lt;name&gt;, it overrides <code>branch.&lt;name&gt;.remote</code> for
3710         pushing.  It also overrides <code>remote.pushDefault</code> for pushing
3711         from branch &lt;name&gt;.  When you pull from one place (e.g. your
3712         upstream) and push to another place (e.g. your own publishing
3713         repository), you would want to set <code>remote.pushDefault</code> to
3714         specify the remote to push to for all branches, and use this
3715         option to override it for a specific branch.
3716 </p>
3717 </dd>
3718 <dt class="hdlist1">
3719 branch.&lt;name&gt;.merge
3720 </dt>
3721 <dd>
3722 <p>
3723         Defines, together with branch.&lt;name&gt;.remote, the upstream branch
3724         for the given branch. It tells <em>git fetch</em>/<em>git pull</em>/<em>git rebase</em> which
3725         branch to merge and can also affect <em>git push</em> (see push.default).
3726         When in branch &lt;name&gt;, it tells <em>git fetch</em> the default
3727         refspec to be marked for merging in FETCH_HEAD. The value is
3728         handled like the remote part of a refspec, and must match a
3729         ref which is fetched from the remote given by
3730         "branch.&lt;name&gt;.remote".
3731         The merge information is used by <em>git pull</em> (which at first calls
3732         <em>git fetch</em>) to lookup the default branch for merging. Without
3733         this option, <em>git pull</em> defaults to merge the first refspec fetched.
3734         Specify multiple values to get an octopus merge.
3735         If you wish to setup <em>git pull</em> so that it merges into &lt;name&gt; from
3736         another branch in the local repository, you can point
3737         branch.&lt;name&gt;.merge to the desired branch, and use the relative path
3738         setting <code>.</code> (a period) for branch.&lt;name&gt;.remote.
3739 </p>
3740 </dd>
3741 <dt class="hdlist1">
3742 branch.&lt;name&gt;.mergeOptions
3743 </dt>
3744 <dd>
3745 <p>
3746         Sets default options for merging into branch &lt;name&gt;. The syntax and
3747         supported options are the same as those of <a href="git-merge.html">git-merge(1)</a>, but
3748         option values containing whitespace characters are currently not
3749         supported.
3750 </p>
3751 </dd>
3752 <dt class="hdlist1">
3753 branch.&lt;name&gt;.rebase
3754 </dt>
3755 <dd>
3756 <p>
3757         When true, rebase the branch &lt;name&gt; on top of the fetched branch,
3758         instead of merging the default branch from the default remote when
3759         "git pull" is run. See "pull.rebase" for doing this in a non
3760         branch-specific manner.
3761 </p>
3762 <div class="paragraph"><p>When <code>merges</code> (or just <em>m</em>), pass the <code>--rebase-merges</code> option to <em>git rebase</em>
3763 so that the local merge commits are included in the rebase (see
3764 <a href="git-rebase.html">git-rebase(1)</a> for details).</p></div>
3765 <div class="paragraph"><p>When the value is <code>interactive</code> (or just <em>i</em>), the rebase is run in interactive
3766 mode.</p></div>
3767 <div class="paragraph"><p><strong>NOTE</strong>: this is a possibly dangerous operation; do <strong>not</strong> use
3768 it unless you understand the implications (see <a href="git-rebase.html">git-rebase(1)</a>
3769 for details).</p></div>
3770 </dd>
3771 <dt class="hdlist1">
3772 branch.&lt;name&gt;.description
3773 </dt>
3774 <dd>
3775 <p>
3776         Branch description, can be edited with
3777         <code>git branch --edit-description</code>. Branch description is
3778         automatically added in the format-patch cover letter or
3779         request-pull summary.
3780 </p>
3781 </dd>
3782 <dt class="hdlist1">
3783 browser.&lt;tool&gt;.cmd
3784 </dt>
3785 <dd>
3786 <p>
3787         Specify the command to invoke the specified browser. The
3788         specified command is evaluated in shell with the URLs passed
3789         as arguments. (See <a href="git-web&#45;&#45;browse.html">git-web&#45;&#45;browse(1)</a>.)
3790 </p>
3791 </dd>
3792 <dt class="hdlist1">
3793 browser.&lt;tool&gt;.path
3794 </dt>
3795 <dd>
3796 <p>
3797         Override the path for the given tool that may be used to
3798         browse HTML help (see <code>-w</code> option in <a href="git-help.html">git-help(1)</a>) or a
3799         working repository in gitweb (see <a href="git-instaweb.html">git-instaweb(1)</a>).
3800 </p>
3801 </dd>
3802 <dt class="hdlist1">
3803 bundle.*
3804 </dt>
3805 <dd>
3806 <p>
3807         The <code>bundle.*</code> keys may appear in a bundle list file found via the
3808         <code>git clone --bundle-uri</code> option. These keys currently have no effect
3809         if placed in a repository config file, though this will change in the
3810         future. See <a href="technical/bundle-uri.html">the bundle URI design
3811         document</a> for more details.
3812 </p>
3813 </dd>
3814 <dt class="hdlist1">
3815 bundle.version
3816 </dt>
3817 <dd>
3818 <p>
3819         This integer value advertises the version of the bundle list format
3820         used by the bundle list. Currently, the only accepted value is <code>1</code>.
3821 </p>
3822 </dd>
3823 <dt class="hdlist1">
3824 bundle.mode
3825 </dt>
3826 <dd>
3827 <p>
3828         This string value should be either <code>all</code> or <code>any</code>. This value describes
3829         whether all of the advertised bundles are required to unbundle a
3830         complete understanding of the bundled information (<code>all</code>) or if any one
3831         of the listed bundle URIs is sufficient (<code>any</code>).
3832 </p>
3833 </dd>
3834 <dt class="hdlist1">
3835 bundle.heuristic
3836 </dt>
3837 <dd>
3838 <p>
3839         If this string-valued key exists, then the bundle list is designed to
3840         work well with incremental <code>git fetch</code> commands. The heuristic signals
3841         that there are additional keys available for each bundle that help
3842         determine which subset of bundles the client should download. The
3843         only value currently understood is <code>creationToken</code>.
3844 </p>
3845 </dd>
3846 <dt class="hdlist1">
3847 bundle.&lt;id&gt;.*
3848 </dt>
3849 <dd>
3850 <p>
3851         The <code>bundle.&lt;id&gt;.*</code> keys are used to describe a single item in the
3852         bundle list, grouped under <code>&lt;id&gt;</code> for identification purposes.
3853 </p>
3854 </dd>
3855 <dt class="hdlist1">
3856 bundle.&lt;id&gt;.uri
3857 </dt>
3858 <dd>
3859 <p>
3860         This string value defines the URI by which Git can reach the contents
3861         of this <code>&lt;id&gt;</code>. This URI may be a bundle file or another bundle list.
3862 </p>
3863 </dd>
3864 <dt class="hdlist1">
3865 checkout.defaultRemote
3866 </dt>
3867 <dd>
3868 <p>
3869         When you run <code>git checkout &lt;something&gt;</code>
3870         or <code>git switch &lt;something&gt;</code> and only have one
3871         remote, it may implicitly fall back on checking out and
3872         tracking e.g. <code>origin/&lt;something&gt;</code>. This stops working as soon
3873         as you have more than one remote with a <code>&lt;something&gt;</code>
3874         reference. This setting allows for setting the name of a
3875         preferred remote that should always win when it comes to
3876         disambiguation. The typical use-case is to set this to
3877         <code>origin</code>.
3878 </p>
3879 <div class="paragraph"><p>Currently this is used by <a href="git-switch.html">git-switch(1)</a> and
3880 <a href="git-checkout.html">git-checkout(1)</a> when <code>git checkout &lt;something&gt;</code>
3881 or <code>git switch &lt;something&gt;</code>
3882 will checkout the <code>&lt;something&gt;</code> branch on another remote,
3883 and by <a href="git-worktree.html">git-worktree(1)</a> when <code>git worktree add</code> refers to a
3884 remote branch. This setting might be used for other checkout-like
3885 commands or functionality in the future.</p></div>
3886 </dd>
3887 <dt class="hdlist1">
3888 checkout.guess
3889 </dt>
3890 <dd>
3891 <p>
3892         Provides the default value for the <code>--guess</code> or <code>--no-guess</code>
3893         option in <code>git checkout</code> and <code>git switch</code>. See
3894         <a href="git-switch.html">git-switch(1)</a> and <a href="git-checkout.html">git-checkout(1)</a>.
3895 </p>
3896 </dd>
3897 <dt class="hdlist1">
3898 checkout.workers
3899 </dt>
3900 <dd>
3901 <p>
3902         The number of parallel workers to use when updating the working tree.
3903         The default is one, i.e. sequential execution. If set to a value less
3904         than one, Git will use as many workers as the number of logical cores
3905         available. This setting and <code>checkout.thresholdForParallelism</code> affect
3906         all commands that perform checkout. E.g. checkout, clone, reset,
3907         sparse-checkout, etc.
3908 </p>
3909 <div class="paragraph"><p>Note: parallel checkout usually delivers better performance for repositories
3910 located on SSDs or over NFS. For repositories on spinning disks and/or machines
3911 with a small number of cores, the default sequential checkout often performs
3912 better. The size and compression level of a repository might also influence how
3913 well the parallel version performs.</p></div>
3914 </dd>
3915 <dt class="hdlist1">
3916 checkout.thresholdForParallelism
3917 </dt>
3918 <dd>
3919 <p>
3920         When running parallel checkout with a small number of files, the cost
3921         of subprocess spawning and inter-process communication might outweigh
3922         the parallelization gains. This setting allows to define the minimum
3923         number of files for which parallel checkout should be attempted. The
3924         default is 100.
3925 </p>
3926 </dd>
3927 <dt class="hdlist1">
3928 clean.requireForce
3929 </dt>
3930 <dd>
3931 <p>
3932         A boolean to make git-clean do nothing unless given -f,
3933         -i or -n.   Defaults to true.
3934 </p>
3935 </dd>
3936 <dt class="hdlist1">
3937 clone.defaultRemoteName
3938 </dt>
3939 <dd>
3940 <p>
3941         The name of the remote to create when cloning a repository.  Defaults to
3942         <code>origin</code>, and can be overridden by passing the <code>--origin</code> command-line
3943         option to <a href="git-clone.html">git-clone(1)</a>.
3944 </p>
3945 </dd>
3946 <dt class="hdlist1">
3947 clone.rejectShallow
3948 </dt>
3949 <dd>
3950 <p>
3951         Reject to clone a repository if it is a shallow one, can be overridden by
3952         passing option <code>--reject-shallow</code> in command line. See <a href="git-clone.html">git-clone(1)</a>
3953 </p>
3954 </dd>
3955 <dt class="hdlist1">
3956 clone.filterSubmodules
3957 </dt>
3958 <dd>
3959 <p>
3960         If a partial clone filter is provided (see <code>--filter</code> in
3961         <a href="git-rev-list.html">git-rev-list(1)</a>) and <code>--recurse-submodules</code> is used, also apply
3962         the filter to submodules.
3963 </p>
3964 </dd>
3965 <dt class="hdlist1">
3966 color.advice
3967 </dt>
3968 <dd>
3969 <p>
3970         A boolean to enable/disable color in hints (e.g. when a push
3971         failed, see <code>advice.*</code> for a list).  May be set to <code>always</code>,
3972         <code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which case colors
3973         are used only when the error output goes to a terminal. If
3974         unset, then the value of <code>color.ui</code> is used (<code>auto</code> by default).
3975 </p>
3976 </dd>
3977 <dt class="hdlist1">
3978 color.advice.hint
3979 </dt>
3980 <dd>
3981 <p>
3982         Use customized color for hints.
3983 </p>
3984 </dd>
3985 <dt class="hdlist1">
3986 color.blame.highlightRecent
3987 </dt>
3988 <dd>
3989 <p>
3990         Specify the line annotation color for <code>git blame --color-by-age</code>
3991         depending upon the age of the line.
3992 </p>
3993 <div class="paragraph"><p>This setting should be set to a comma-separated list of color and
3994 date settings, starting and ending with a color, the dates should be
3995 set from oldest to newest. The metadata will be colored with the
3996 specified colors if the line was introduced before the given
3997 timestamp, overwriting older timestamped colors.</p></div>
3998 <div class="paragraph"><p>Instead of an absolute timestamp relative timestamps work as well,
3999 e.g. <code>2.weeks.ago</code> is valid to address anything older than 2 weeks.</p></div>
4000 <div class="paragraph"><p>It defaults to <code>blue,12 month ago,white,1 month ago,red</code>, which
4001 colors everything older than one year blue, recent changes between
4002 one month and one year old are kept white, and lines introduced
4003 within the last month are colored red.</p></div>
4004 </dd>
4005 <dt class="hdlist1">
4006 color.blame.repeatedLines
4007 </dt>
4008 <dd>
4009 <p>
4010         Use the specified color to colorize line annotations for
4011         <code>git blame --color-lines</code>, if they come from the same commit as the
4012         preceding line. Defaults to cyan.
4013 </p>
4014 </dd>
4015 <dt class="hdlist1">
4016 color.branch
4017 </dt>
4018 <dd>
4019 <p>
4020         A boolean to enable/disable color in the output of
4021         <a href="git-branch.html">git-branch(1)</a>. May be set to <code>always</code>,
4022         <code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which case colors are used
4023         only when the output is to a terminal. If unset, then the
4024         value of <code>color.ui</code> is used (<code>auto</code> by default).
4025 </p>
4026 </dd>
4027 <dt class="hdlist1">
4028 color.branch.&lt;slot&gt;
4029 </dt>
4030 <dd>
4031 <p>
4032         Use customized color for branch coloration. <code>&lt;slot&gt;</code> is one of
4033         <code>current</code> (the current branch), <code>local</code> (a local branch),
4034         <code>remote</code> (a remote-tracking branch in refs/remotes/),
4035         <code>upstream</code> (upstream tracking branch), <code>plain</code> (other
4036         refs).
4037 </p>
4038 </dd>
4039 <dt class="hdlist1">
4040 color.diff
4041 </dt>
4042 <dd>
4043 <p>
4044         Whether to use ANSI escape sequences to add color to patches.
4045         If this is set to <code>always</code>, <a href="git-diff.html">git-diff(1)</a>,
4046         <a href="git-log.html">git-log(1)</a>, and <a href="git-show.html">git-show(1)</a> will use color
4047         for all patches.  If it is set to <code>true</code> or <code>auto</code>, those
4048         commands will only use color when output is to the terminal.
4049         If unset, then the value of <code>color.ui</code> is used (<code>auto</code> by
4050         default).
4051 </p>
4052 <div class="paragraph"><p>This does not affect <a href="git-format-patch.html">git-format-patch(1)</a> or the
4053 <em>git-diff-&#42;</em> plumbing commands.  Can be overridden on the
4054 command line with the <code>--color[=&lt;when&gt;]</code> option.</p></div>
4055 </dd>
4056 <dt class="hdlist1">
4057 color.diff.&lt;slot&gt;
4058 </dt>
4059 <dd>
4060 <p>
4061         Use customized color for diff colorization.  <code>&lt;slot&gt;</code> specifies
4062         which part of the patch to use the specified color, and is one
4063         of <code>context</code> (context text - <code>plain</code> is a historical synonym),
4064         <code>meta</code> (metainformation), <code>frag</code>
4065         (hunk header), <em>func</em> (function in hunk header), <code>old</code> (removed lines),
4066         <code>new</code> (added lines), <code>commit</code> (commit headers), <code>whitespace</code>
4067         (highlighting whitespace errors), <code>oldMoved</code> (deleted lines),
4068         <code>newMoved</code> (added lines), <code>oldMovedDimmed</code>, <code>oldMovedAlternative</code>,
4069         <code>oldMovedAlternativeDimmed</code>, <code>newMovedDimmed</code>, <code>newMovedAlternative</code>
4070         <code>newMovedAlternativeDimmed</code> (See the <em>&lt;mode&gt;</em>
4071         setting of <em>--color-moved</em> in <a href="git-diff.html">git-diff(1)</a> for details),
4072         <code>contextDimmed</code>, <code>oldDimmed</code>, <code>newDimmed</code>, <code>contextBold</code>,
4073         <code>oldBold</code>, and <code>newBold</code> (see <a href="git-range-diff.html">git-range-diff(1)</a> for details).
4074 </p>
4075 </dd>
4076 <dt class="hdlist1">
4077 color.decorate.&lt;slot&gt;
4078 </dt>
4079 <dd>
4080 <p>
4081         Use customized color for <em>git log --decorate</em> output.  <code>&lt;slot&gt;</code> is one
4082         of <code>branch</code>, <code>remoteBranch</code>, <code>tag</code>, <code>stash</code> or <code>HEAD</code> for local
4083         branches, remote-tracking branches, tags, stash and HEAD, respectively
4084         and <code>grafted</code> for grafted commits.
4085 </p>
4086 </dd>
4087 <dt class="hdlist1">
4088 color.grep
4089 </dt>
4090 <dd>
4091 <p>
4092         When set to <code>always</code>, always highlight matches.  When <code>false</code> (or
4093         <code>never</code>), never.  When set to <code>true</code> or <code>auto</code>, use color only
4094         when the output is written to the terminal.  If unset, then the
4095         value of <code>color.ui</code> is used (<code>auto</code> by default).
4096 </p>
4097 </dd>
4098 <dt class="hdlist1">
4099 color.grep.&lt;slot&gt;
4100 </dt>
4101 <dd>
4102 <p>
4103         Use customized color for grep colorization.  <code>&lt;slot&gt;</code> specifies which
4104         part of the line to use the specified color, and is one of
4105 </p>
4106 <div class="openblock">
4107 <div class="content">
4108 <div class="dlist"><dl>
4109 <dt class="hdlist1">
4110 <code>context</code>
4111 </dt>
4112 <dd>
4113 <p>
4114         non-matching text in context lines (when using <code>-A</code>, <code>-B</code>, or <code>-C</code>)
4115 </p>
4116 </dd>
4117 <dt class="hdlist1">
4118 <code>filename</code>
4119 </dt>
4120 <dd>
4121 <p>
4122         filename prefix (when not using <code>-h</code>)
4123 </p>
4124 </dd>
4125 <dt class="hdlist1">
4126 <code>function</code>
4127 </dt>
4128 <dd>
4129 <p>
4130         function name lines (when using <code>-p</code>)
4131 </p>
4132 </dd>
4133 <dt class="hdlist1">
4134 <code>lineNumber</code>
4135 </dt>
4136 <dd>
4137 <p>
4138         line number prefix (when using <code>-n</code>)
4139 </p>
4140 </dd>
4141 <dt class="hdlist1">
4142 <code>column</code>
4143 </dt>
4144 <dd>
4145 <p>
4146         column number prefix (when using <code>--column</code>)
4147 </p>
4148 </dd>
4149 <dt class="hdlist1">
4150 <code>match</code>
4151 </dt>
4152 <dd>
4153 <p>
4154         matching text (same as setting <code>matchContext</code> and <code>matchSelected</code>)
4155 </p>
4156 </dd>
4157 <dt class="hdlist1">
4158 <code>matchContext</code>
4159 </dt>
4160 <dd>
4161 <p>
4162         matching text in context lines
4163 </p>
4164 </dd>
4165 <dt class="hdlist1">
4166 <code>matchSelected</code>
4167 </dt>
4168 <dd>
4169 <p>
4170         matching text in selected lines. Also, used to customize the following
4171         <a href="git-log.html">git-log(1)</a> subcommands: <code>--grep</code>, <code>--author</code> and <code>--committer</code>.
4172 </p>
4173 </dd>
4174 <dt class="hdlist1">
4175 <code>selected</code>
4176 </dt>
4177 <dd>
4178 <p>
4179         non-matching text in selected lines. Also, used to customize the
4180         following <a href="git-log.html">git-log(1)</a> subcommands: <code>--grep</code>, <code>--author</code> and
4181         <code>--committer</code>.
4182 </p>
4183 </dd>
4184 <dt class="hdlist1">
4185 <code>separator</code>
4186 </dt>
4187 <dd>
4188 <p>
4189         separators between fields on a line (<code>:</code>, <code>-</code>, and <code>=</code>)
4190         and between hunks (<code>--</code>)
4191 </p>
4192 </dd>
4193 </dl></div>
4194 </div></div>
4195 </dd>
4196 <dt class="hdlist1">
4197 color.interactive
4198 </dt>
4199 <dd>
4200 <p>
4201         When set to <code>always</code>, always use colors for interactive prompts
4202         and displays (such as those used by "git-add --interactive" and
4203         "git-clean --interactive"). When false (or <code>never</code>), never.
4204         When set to <code>true</code> or <code>auto</code>, use colors only when the output is
4205         to the terminal. If unset, then the value of <code>color.ui</code> is
4206         used (<code>auto</code> by default).
4207 </p>
4208 </dd>
4209 <dt class="hdlist1">
4210 color.interactive.&lt;slot&gt;
4211 </dt>
4212 <dd>
4213 <p>
4214         Use customized color for <em>git add --interactive</em> and <em>git clean
4215         --interactive</em> output. <code>&lt;slot&gt;</code> may be <code>prompt</code>, <code>header</code>, <code>help</code>
4216         or <code>error</code>, for four distinct types of normal output from
4217         interactive commands.
4218 </p>
4219 </dd>
4220 <dt class="hdlist1">
4221 color.pager
4222 </dt>
4223 <dd>
4224 <p>
4225         A boolean to specify whether <code>auto</code> color modes should colorize
4226         output going to the pager. Defaults to true; set this to false
4227         if your pager does not understand ANSI color codes.
4228 </p>
4229 </dd>
4230 <dt class="hdlist1">
4231 color.push
4232 </dt>
4233 <dd>
4234 <p>
4235         A boolean to enable/disable color in push errors. May be set to
4236         <code>always</code>, <code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which
4237         case colors are used only when the error output goes to a terminal.
4238         If unset, then the value of <code>color.ui</code> is used (<code>auto</code> by default).
4239 </p>
4240 </dd>
4241 <dt class="hdlist1">
4242 color.push.error
4243 </dt>
4244 <dd>
4245 <p>
4246         Use customized color for push errors.
4247 </p>
4248 </dd>
4249 <dt class="hdlist1">
4250 color.remote
4251 </dt>
4252 <dd>
4253 <p>
4254         If set, keywords at the start of the line are highlighted. The
4255         keywords are "error", "warning", "hint" and "success", and are
4256         matched case-insensitively. May be set to <code>always</code>, <code>false</code> (or
4257         <code>never</code>) or <code>auto</code> (or <code>true</code>). If unset, then the value of
4258         <code>color.ui</code> is used (<code>auto</code> by default).
4259 </p>
4260 </dd>
4261 <dt class="hdlist1">
4262 color.remote.&lt;slot&gt;
4263 </dt>
4264 <dd>
4265 <p>
4266         Use customized color for each remote keyword. <code>&lt;slot&gt;</code> may be
4267         <code>hint</code>, <code>warning</code>, <code>success</code> or <code>error</code> which match the
4268         corresponding keyword.
4269 </p>
4270 </dd>
4271 <dt class="hdlist1">
4272 color.showBranch
4273 </dt>
4274 <dd>
4275 <p>
4276         A boolean to enable/disable color in the output of
4277         <a href="git-show-branch.html">git-show-branch(1)</a>. May be set to <code>always</code>,
4278         <code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which case colors are used
4279         only when the output is to a terminal. If unset, then the
4280         value of <code>color.ui</code> is used (<code>auto</code> by default).
4281 </p>
4282 </dd>
4283 <dt class="hdlist1">
4284 color.status
4285 </dt>
4286 <dd>
4287 <p>
4288         A boolean to enable/disable color in the output of
4289         <a href="git-status.html">git-status(1)</a>. May be set to <code>always</code>,
4290         <code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which case colors are used
4291         only when the output is to a terminal. If unset, then the
4292         value of <code>color.ui</code> is used (<code>auto</code> by default).
4293 </p>
4294 </dd>
4295 <dt class="hdlist1">
4296 color.status.&lt;slot&gt;
4297 </dt>
4298 <dd>
4299 <p>
4300         Use customized color for status colorization. <code>&lt;slot&gt;</code> is
4301         one of <code>header</code> (the header text of the status message),
4302         <code>added</code> or <code>updated</code> (files which are added but not committed),
4303         <code>changed</code> (files which are changed but not added in the index),
4304         <code>untracked</code> (files which are not tracked by Git),
4305         <code>branch</code> (the current branch),
4306         <code>nobranch</code> (the color the <em>no branch</em> warning is shown in, defaulting
4307         to red),
4308         <code>localBranch</code> or <code>remoteBranch</code> (the local and remote branch names,
4309         respectively, when branch and tracking information is displayed in the
4310         status short-format), or
4311         <code>unmerged</code> (files which have unmerged changes).
4312 </p>
4313 </dd>
4314 <dt class="hdlist1">
4315 color.transport
4316 </dt>
4317 <dd>
4318 <p>
4319         A boolean to enable/disable color when pushes are rejected. May be
4320         set to <code>always</code>, <code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which
4321         case colors are used only when the error output goes to a terminal.
4322         If unset, then the value of <code>color.ui</code> is used (<code>auto</code> by default).
4323 </p>
4324 </dd>
4325 <dt class="hdlist1">
4326 color.transport.rejected
4327 </dt>
4328 <dd>
4329 <p>
4330         Use customized color when a push was rejected.
4331 </p>
4332 </dd>
4333 <dt class="hdlist1">
4334 color.ui
4335 </dt>
4336 <dd>
4337 <p>
4338         This variable determines the default value for variables such
4339         as <code>color.diff</code> and <code>color.grep</code> that control the use of color
4340         per command family. Its scope will expand as more commands learn
4341         configuration to set a default for the <code>--color</code> option.  Set it
4342         to <code>false</code> or <code>never</code> if you prefer Git commands not to use
4343         color unless enabled explicitly with some other configuration
4344         or the <code>--color</code> option. Set it to <code>always</code> if you want all
4345         output not intended for machine consumption to use color, to
4346         <code>true</code> or <code>auto</code> (this is the default since Git 1.8.4) if you
4347         want such output to use color when written to the terminal.
4348 </p>
4349 </dd>
4350 <dt class="hdlist1">
4351 column.ui
4352 </dt>
4353 <dd>
4354 <p>
4355         Specify whether supported commands should output in columns.
4356         This variable consists of a list of tokens separated by spaces
4357         or commas:
4358 </p>
4359 <div class="paragraph"><p>These options control when the feature should be enabled
4360 (defaults to <em>never</em>):</p></div>
4361 <div class="openblock">
4362 <div class="content">
4363 <div class="dlist"><dl>
4364 <dt class="hdlist1">
4365 <code>always</code>
4366 </dt>
4367 <dd>
4368 <p>
4369         always show in columns
4370 </p>
4371 </dd>
4372 <dt class="hdlist1">
4373 <code>never</code>
4374 </dt>
4375 <dd>
4376 <p>
4377         never show in columns
4378 </p>
4379 </dd>
4380 <dt class="hdlist1">
4381 <code>auto</code>
4382 </dt>
4383 <dd>
4384 <p>
4385         show in columns if the output is to the terminal
4386 </p>
4387 </dd>
4388 </dl></div>
4389 </div></div>
4390 <div class="paragraph"><p>These options control layout (defaults to <em>column</em>).  Setting any
4391 of these implies <em>always</em> if none of <em>always</em>, <em>never</em>, or <em>auto</em> are
4392 specified.</p></div>
4393 <div class="openblock">
4394 <div class="content">
4395 <div class="dlist"><dl>
4396 <dt class="hdlist1">
4397 <code>column</code>
4398 </dt>
4399 <dd>
4400 <p>
4401         fill columns before rows
4402 </p>
4403 </dd>
4404 <dt class="hdlist1">
4405 <code>row</code>
4406 </dt>
4407 <dd>
4408 <p>
4409         fill rows before columns
4410 </p>
4411 </dd>
4412 <dt class="hdlist1">
4413 <code>plain</code>
4414 </dt>
4415 <dd>
4416 <p>
4417         show in one column
4418 </p>
4419 </dd>
4420 </dl></div>
4421 </div></div>
4422 <div class="paragraph"><p>Finally, these options can be combined with a layout option (defaults
4423 to <em>nodense</em>):</p></div>
4424 <div class="openblock">
4425 <div class="content">
4426 <div class="dlist"><dl>
4427 <dt class="hdlist1">
4428 <code>dense</code>
4429 </dt>
4430 <dd>
4431 <p>
4432         make unequal size columns to utilize more space
4433 </p>
4434 </dd>
4435 <dt class="hdlist1">
4436 <code>nodense</code>
4437 </dt>
4438 <dd>
4439 <p>
4440         make equal size columns
4441 </p>
4442 </dd>
4443 </dl></div>
4444 </div></div>
4445 </dd>
4446 <dt class="hdlist1">
4447 column.branch
4448 </dt>
4449 <dd>
4450 <p>
4451         Specify whether to output branch listing in <code>git branch</code> in columns.
4452         See <code>column.ui</code> for details.
4453 </p>
4454 </dd>
4455 <dt class="hdlist1">
4456 column.clean
4457 </dt>
4458 <dd>
4459 <p>
4460         Specify the layout when list items in <code>git clean -i</code>, which always
4461         shows files and directories in columns. See <code>column.ui</code> for details.
4462 </p>
4463 </dd>
4464 <dt class="hdlist1">
4465 column.status
4466 </dt>
4467 <dd>
4468 <p>
4469         Specify whether to output untracked files in <code>git status</code> in columns.
4470         See <code>column.ui</code> for details.
4471 </p>
4472 </dd>
4473 <dt class="hdlist1">
4474 column.tag
4475 </dt>
4476 <dd>
4477 <p>
4478         Specify whether to output tag listing in <code>git tag</code> in columns.
4479         See <code>column.ui</code> for details.
4480 </p>
4481 </dd>
4482 <dt class="hdlist1">
4483 commit.cleanup
4484 </dt>
4485 <dd>
4486 <p>
4487         This setting overrides the default of the <code>--cleanup</code> option in
4488         <code>git commit</code>. See <a href="git-commit.html">git-commit(1)</a> for details. Changing the
4489         default can be useful when you always want to keep lines that begin
4490         with comment character <code>#</code> in your log message, in which case you
4491         would do <code>git config commit.cleanup whitespace</code> (note that you will
4492         have to remove the help lines that begin with <code>#</code> in the commit log
4493         template yourself, if you do this).
4494 </p>
4495 </dd>
4496 <dt class="hdlist1">
4497 commit.gpgSign
4498 </dt>
4499 <dd>
4500 <p>
4501         A boolean to specify whether all commits should be GPG signed.
4502         Use of this option when doing operations such as rebase can
4503         result in a large number of commits being signed. It may be
4504         convenient to use an agent to avoid typing your GPG passphrase
4505         several times.
4506 </p>
4507 </dd>
4508 <dt class="hdlist1">
4509 commit.status
4510 </dt>
4511 <dd>
4512 <p>
4513         A boolean to enable/disable inclusion of status information in the
4514         commit message template when using an editor to prepare the commit
4515         message.  Defaults to true.
4516 </p>
4517 </dd>
4518 <dt class="hdlist1">
4519 commit.template
4520 </dt>
4521 <dd>
4522 <p>
4523         Specify the pathname of a file to use as the template for
4524         new commit messages.
4525 </p>
4526 </dd>
4527 <dt class="hdlist1">
4528 commit.verbose
4529 </dt>
4530 <dd>
4531 <p>
4532         A boolean or int to specify the level of verbose with <code>git commit</code>.
4533         See <a href="git-commit.html">git-commit(1)</a>.
4534 </p>
4535 </dd>
4536 <dt class="hdlist1">
4537 commitGraph.generationVersion
4538 </dt>
4539 <dd>
4540 <p>
4541         Specifies the type of generation number version to use when writing
4542         or reading the commit-graph file. If version 1 is specified, then
4543         the corrected commit dates will not be written or read. Defaults to
4544         2.
4545 </p>
4546 </dd>
4547 <dt class="hdlist1">
4548 commitGraph.maxNewFilters
4549 </dt>
4550 <dd>
4551 <p>
4552         Specifies the default value for the <code>--max-new-filters</code> option of <code>git
4553         commit-graph write</code> (c.f., <a href="git-commit-graph.html">git-commit-graph(1)</a>).
4554 </p>
4555 </dd>
4556 <dt class="hdlist1">
4557 commitGraph.readChangedPaths
4558 </dt>
4559 <dd>
4560 <p>
4561         If true, then git will use the changed-path Bloom filters in the
4562         commit-graph file (if it exists, and they are present). Defaults to
4563         true. See <a href="git-commit-graph.html">git-commit-graph(1)</a> for more information.
4564 </p>
4565 </dd>
4566 <dt class="hdlist1">
4567 credential.helper
4568 </dt>
4569 <dd>
4570 <p>
4571         Specify an external helper to be called when a username or
4572         password credential is needed; the helper may consult external
4573         storage to avoid prompting the user for the credentials. This is
4574         normally the name of a credential helper with possible
4575         arguments, but may also be an absolute path with arguments or, if
4576         preceded by <code>!</code>, shell commands.
4577 </p>
4578 <div class="paragraph"><p>Note that multiple helpers may be defined. See <a href="gitcredentials.html">gitcredentials(7)</a>
4579 for details and examples.</p></div>
4580 </dd>
4581 <dt class="hdlist1">
4582 credential.useHttpPath
4583 </dt>
4584 <dd>
4585 <p>
4586         When acquiring credentials, consider the "path" component of an http
4587         or https URL to be important. Defaults to false. See
4588         <a href="gitcredentials.html">gitcredentials(7)</a> for more information.
4589 </p>
4590 </dd>
4591 <dt class="hdlist1">
4592 credential.username
4593 </dt>
4594 <dd>
4595 <p>
4596         If no username is set for a network authentication, use this username
4597         by default. See credential.&lt;context&gt;.* below, and
4598         <a href="gitcredentials.html">gitcredentials(7)</a>.
4599 </p>
4600 </dd>
4601 <dt class="hdlist1">
4602 credential.&lt;url&gt;.*
4603 </dt>
4604 <dd>
4605 <p>
4606         Any of the credential.* options above can be applied selectively to
4607         some credentials. For example "credential.https://example.com.username"
4608         would set the default username only for https connections to
4609         example.com. See <a href="gitcredentials.html">gitcredentials(7)</a> for details on how URLs are
4610         matched.
4611 </p>
4612 </dd>
4613 <dt class="hdlist1">
4614 credentialCache.ignoreSIGHUP
4615 </dt>
4616 <dd>
4617 <p>
4618         Tell git-credential-cache&#8212;daemon to ignore SIGHUP, instead of quitting.
4619 </p>
4620 </dd>
4621 <dt class="hdlist1">
4622 credentialStore.lockTimeoutMS
4623 </dt>
4624 <dd>
4625 <p>
4626         The length of time, in milliseconds, for git-credential-store to retry
4627         when trying to lock the credentials file. Value 0 means not to retry at
4628         all; -1 means to try indefinitely. Default is 1000 (i.e., retry for
4629         1s).
4630 </p>
4631 </dd>
4632 <dt class="hdlist1">
4633 completion.commands
4634 </dt>
4635 <dd>
4636 <p>
4637         This is only used by git-completion.bash to add or remove
4638         commands from the list of completed commands. Normally only
4639         porcelain commands and a few select others are completed. You
4640         can add more commands, separated by space, in this
4641         variable. Prefixing the command with <em>-</em> will remove it from
4642         the existing list.
4643 </p>
4644 </dd>
4645 <dt class="hdlist1">
4646 diff.autoRefreshIndex
4647 </dt>
4648 <dd>
4649 <p>
4650         When using <em>git diff</em> to compare with work tree
4651         files, do not consider stat-only change as changed.
4652         Instead, silently run <code>git update-index --refresh</code> to
4653         update the cached stat information for paths whose
4654         contents in the work tree match the contents in the
4655         index.  This option defaults to true.  Note that this
4656         affects only <em>git diff</em> Porcelain, and not lower level
4657         <em>diff</em> commands such as <em>git diff-files</em>.
4658 </p>
4659 </dd>
4660 <dt class="hdlist1">
4661 diff.dirstat
4662 </dt>
4663 <dd>
4664 <p>
4665         A comma separated list of <code>--dirstat</code> parameters specifying the
4666         default behavior of the <code>--dirstat</code> option to <a href="git-diff.html">git-diff(1)</a>
4667         and friends. The defaults can be overridden on the command line
4668         (using <code>--dirstat=&lt;param1,param2,...&gt;</code>). The fallback defaults
4669         (when not changed by <code>diff.dirstat</code>) are <code>changes,noncumulative,3</code>.
4670         The following parameters are available:
4671 </p>
4672 <div class="openblock">
4673 <div class="content">
4674 <div class="dlist"><dl>
4675 <dt class="hdlist1">
4676 <code>changes</code>
4677 </dt>
4678 <dd>
4679 <p>
4680         Compute the dirstat numbers by counting the lines that have been
4681         removed from the source, or added to the destination. This ignores
4682         the amount of pure code movements within a file.  In other words,
4683         rearranging lines in a file is not counted as much as other changes.
4684         This is the default behavior when no parameter is given.
4685 </p>
4686 </dd>
4687 <dt class="hdlist1">
4688 <code>lines</code>
4689 </dt>
4690 <dd>
4691 <p>
4692         Compute the dirstat numbers by doing the regular line-based diff
4693         analysis, and summing the removed/added line counts. (For binary
4694         files, count 64-byte chunks instead, since binary files have no
4695         natural concept of lines). This is a more expensive <code>--dirstat</code>
4696         behavior than the <code>changes</code> behavior, but it does count rearranged
4697         lines within a file as much as other changes. The resulting output
4698         is consistent with what you get from the other <code>--*stat</code> options.
4699 </p>
4700 </dd>
4701 <dt class="hdlist1">
4702 <code>files</code>
4703 </dt>
4704 <dd>
4705 <p>
4706         Compute the dirstat numbers by counting the number of files changed.
4707         Each changed file counts equally in the dirstat analysis. This is
4708         the computationally cheapest <code>--dirstat</code> behavior, since it does
4709         not have to look at the file contents at all.
4710 </p>
4711 </dd>
4712 <dt class="hdlist1">
4713 <code>cumulative</code>
4714 </dt>
4715 <dd>
4716 <p>
4717         Count changes in a child directory for the parent directory as well.
4718         Note that when using <code>cumulative</code>, the sum of the percentages
4719         reported may exceed 100%. The default (non-cumulative) behavior can
4720         be specified with the <code>noncumulative</code> parameter.
4721 </p>
4722 </dd>
4723 <dt class="hdlist1">
4724 &lt;limit&gt;
4725 </dt>
4726 <dd>
4727 <p>
4728         An integer parameter specifies a cut-off percent (3% by default).
4729         Directories contributing less than this percentage of the changes
4730         are not shown in the output.
4731 </p>
4732 </dd>
4733 </dl></div>
4734 </div></div>
4735 <div class="paragraph"><p>Example: The following will count changed files, while ignoring
4736 directories with less than 10% of the total amount of changed files,
4737 and accumulating child directory counts in the parent directories:
4738 <code>files,10,cumulative</code>.</p></div>
4739 </dd>
4740 <dt class="hdlist1">
4741 diff.statNameWidth
4742 </dt>
4743 <dd>
4744 <p>
4745         Limit the width of the filename part in --stat output. If set, applies
4746         to all commands generating --stat output except format-patch.
4747 </p>
4748 </dd>
4749 <dt class="hdlist1">
4750 diff.statGraphWidth
4751 </dt>
4752 <dd>
4753 <p>
4754         Limit the width of the graph part in --stat output. If set, applies
4755         to all commands generating --stat output except format-patch.
4756 </p>
4757 </dd>
4758 <dt class="hdlist1">
4759 diff.context
4760 </dt>
4761 <dd>
4762 <p>
4763         Generate diffs with &lt;n&gt; lines of context instead of the default
4764         of 3. This value is overridden by the -U option.
4765 </p>
4766 </dd>
4767 <dt class="hdlist1">
4768 diff.interHunkContext
4769 </dt>
4770 <dd>
4771 <p>
4772         Show the context between diff hunks, up to the specified number
4773         of lines, thereby fusing the hunks that are close to each other.
4774         This value serves as the default for the <code>--inter-hunk-context</code>
4775         command line option.
4776 </p>
4777 </dd>
4778 <dt class="hdlist1">
4779 diff.external
4780 </dt>
4781 <dd>
4782 <p>
4783         If this config variable is set, diff generation is not
4784         performed using the internal diff machinery, but using the
4785         given command.  Can be overridden with the &#8216;GIT_EXTERNAL_DIFF&#8217;
4786         environment variable.  The command is called with parameters
4787         as described under "git Diffs" in <a href="git.html">git(1)</a>.  Note: if
4788         you want to use an external diff program only on a subset of
4789         your files, you might want to use <a href="gitattributes.html">gitattributes(5)</a> instead.
4790 </p>
4791 </dd>
4792 <dt class="hdlist1">
4793 diff.ignoreSubmodules
4794 </dt>
4795 <dd>
4796 <p>
4797         Sets the default value of --ignore-submodules. Note that this
4798         affects only <em>git diff</em> Porcelain, and not lower level <em>diff</em>
4799         commands such as <em>git diff-files</em>. <em>git checkout</em>
4800         and <em>git switch</em> also honor
4801         this setting when reporting uncommitted changes. Setting it to
4802         <em>all</em> disables the submodule summary normally shown by <em>git commit</em>
4803         and <em>git status</em> when <code>status.submoduleSummary</code> is set unless it is
4804         overridden by using the --ignore-submodules command-line option.
4805         The <em>git submodule</em> commands are not affected by this setting.
4806         By default this is set to untracked so that any untracked
4807         submodules are ignored.
4808 </p>
4809 </dd>
4810 <dt class="hdlist1">
4811 diff.mnemonicPrefix
4812 </dt>
4813 <dd>
4814 <p>
4815         If set, <em>git diff</em> uses a prefix pair that is different from the
4816         standard "a/" and "b/" depending on what is being compared.  When
4817         this configuration is in effect, reverse diff output also swaps
4818         the order of the prefixes:
4819 </p>
4820 <div class="dlist"><dl>
4821 <dt class="hdlist1">
4822 <code>git diff</code>
4823 </dt>
4824 <dd>
4825 <p>
4826         compares the (i)ndex and the (w)ork tree;
4827 </p>
4828 </dd>
4829 <dt class="hdlist1">
4830 <code>git diff HEAD</code>
4831 </dt>
4832 <dd>
4833 <p>
4834          compares a (c)ommit and the (w)ork tree;
4835 </p>
4836 </dd>
4837 <dt class="hdlist1">
4838 <code>git diff --cached</code>
4839 </dt>
4840 <dd>
4841 <p>
4842         compares a (c)ommit and the (i)ndex;
4843 </p>
4844 </dd>
4845 <dt class="hdlist1">
4846 <code>git diff HEAD:file1 file2</code>
4847 </dt>
4848 <dd>
4849 <p>
4850         compares an (o)bject and a (w)ork tree entity;
4851 </p>
4852 </dd>
4853 <dt class="hdlist1">
4854 <code>git diff --no-index a b</code>
4855 </dt>
4856 <dd>
4857 <p>
4858         compares two non-git things (1) and (2).
4859 </p>
4860 </dd>
4861 </dl></div>
4862 </dd>
4863 <dt class="hdlist1">
4864 diff.noprefix
4865 </dt>
4866 <dd>
4867 <p>
4868         If set, <em>git diff</em> does not show any source or destination prefix.
4869 </p>
4870 </dd>
4871 <dt class="hdlist1">
4872 diff.relative
4873 </dt>
4874 <dd>
4875 <p>
4876         If set to <em>true</em>, <em>git diff</em> does not show changes outside of the directory
4877         and show pathnames relative to the current directory.
4878 </p>
4879 </dd>
4880 <dt class="hdlist1">
4881 diff.orderFile
4882 </dt>
4883 <dd>
4884 <p>
4885         File indicating how to order files within a diff.
4886         See the <em>-O</em> option to <a href="git-diff.html">git-diff(1)</a> for details.
4887         If <code>diff.orderFile</code> is a relative pathname, it is treated as
4888         relative to the top of the working tree.
4889 </p>
4890 </dd>
4891 <dt class="hdlist1">
4892 diff.renameLimit
4893 </dt>
4894 <dd>
4895 <p>
4896         The number of files to consider in the exhaustive portion of
4897         copy/rename detection; equivalent to the <em>git diff</em> option
4898         <code>-l</code>.  If not set, the default value is currently 1000.  This
4899         setting has no effect if rename detection is turned off.
4900 </p>
4901 </dd>
4902 <dt class="hdlist1">
4903 diff.renames
4904 </dt>
4905 <dd>
4906 <p>
4907         Whether and how Git detects renames.  If set to "false",
4908         rename detection is disabled. If set to "true", basic rename
4909         detection is enabled.  If set to "copies" or "copy", Git will
4910         detect copies, as well.  Defaults to true.  Note that this
4911         affects only <em>git diff</em> Porcelain like <a href="git-diff.html">git-diff(1)</a> and
4912         <a href="git-log.html">git-log(1)</a>, and not lower level commands such as
4913         <a href="git-diff-files.html">git-diff-files(1)</a>.
4914 </p>
4915 </dd>
4916 <dt class="hdlist1">
4917 diff.suppressBlankEmpty
4918 </dt>
4919 <dd>
4920 <p>
4921         A boolean to inhibit the standard behavior of printing a space
4922         before each empty output line. Defaults to false.
4923 </p>
4924 </dd>
4925 <dt class="hdlist1">
4926 diff.submodule
4927 </dt>
4928 <dd>
4929 <p>
4930         Specify the format in which differences in submodules are
4931         shown.  The "short" format just shows the names of the commits
4932         at the beginning and end of the range. The "log" format lists
4933         the commits in the range like <a href="git-submodule.html">git-submodule(1)</a> <code>summary</code>
4934         does. The "diff" format shows an inline diff of the changed
4935         contents of the submodule. Defaults to "short".
4936 </p>
4937 </dd>
4938 <dt class="hdlist1">
4939 diff.wordRegex
4940 </dt>
4941 <dd>
4942 <p>
4943         A POSIX Extended Regular Expression used to determine what is a "word"
4944         when performing word-by-word difference calculations.  Character
4945         sequences that match the regular expression are "words", all other
4946         characters are <strong>ignorable</strong> whitespace.
4947 </p>
4948 </dd>
4949 <dt class="hdlist1">
4950 diff.&lt;driver&gt;.command
4951 </dt>
4952 <dd>
4953 <p>
4954         The custom diff driver command.  See <a href="gitattributes.html">gitattributes(5)</a>
4955         for details.
4956 </p>
4957 </dd>
4958 <dt class="hdlist1">
4959 diff.&lt;driver&gt;.xfuncname
4960 </dt>
4961 <dd>
4962 <p>
4963         The regular expression that the diff driver should use to
4964         recognize the hunk header.  A built-in pattern may also be used.
4965         See <a href="gitattributes.html">gitattributes(5)</a> for details.
4966 </p>
4967 </dd>
4968 <dt class="hdlist1">
4969 diff.&lt;driver&gt;.binary
4970 </dt>
4971 <dd>
4972 <p>
4973         Set this option to true to make the diff driver treat files as
4974         binary.  See <a href="gitattributes.html">gitattributes(5)</a> for details.
4975 </p>
4976 </dd>
4977 <dt class="hdlist1">
4978 diff.&lt;driver&gt;.textconv
4979 </dt>
4980 <dd>
4981 <p>
4982         The command that the diff driver should call to generate the
4983         text-converted version of a file.  The result of the
4984         conversion is used to generate a human-readable diff.  See
4985         <a href="gitattributes.html">gitattributes(5)</a> for details.
4986 </p>
4987 </dd>
4988 <dt class="hdlist1">
4989 diff.&lt;driver&gt;.wordRegex
4990 </dt>
4991 <dd>
4992 <p>
4993         The regular expression that the diff driver should use to
4994         split words in a line.  See <a href="gitattributes.html">gitattributes(5)</a> for
4995         details.
4996 </p>
4997 </dd>
4998 <dt class="hdlist1">
4999 diff.&lt;driver&gt;.cachetextconv
5000 </dt>
5001 <dd>
5002 <p>
5003         Set this option to true to make the diff driver cache the text
5004         conversion outputs.  See <a href="gitattributes.html">gitattributes(5)</a> for details.
5005 </p>
5006 <div class="dlist"><dl>
5007 <dt class="hdlist1">
5008 <code>araxis</code>
5009 </dt>
5010 <dd>
5011 <p>
5012 Use Araxis Merge (requires a graphical session)
5013 </p>
5014 </dd>
5015 <dt class="hdlist1">
5016 <code>bc</code>
5017 </dt>
5018 <dd>
5019 <p>
5020 Use Beyond Compare (requires a graphical session)
5021 </p>
5022 </dd>
5023 <dt class="hdlist1">
5024 <code>bc3</code>
5025 </dt>
5026 <dd>
5027 <p>
5028 Use Beyond Compare (requires a graphical session)
5029 </p>
5030 </dd>
5031 <dt class="hdlist1">
5032 <code>bc4</code>
5033 </dt>
5034 <dd>
5035 <p>
5036 Use Beyond Compare (requires a graphical session)
5037 </p>
5038 </dd>
5039 <dt class="hdlist1">
5040 <code>codecompare</code>
5041 </dt>
5042 <dd>
5043 <p>
5044 Use Code Compare (requires a graphical session)
5045 </p>
5046 </dd>
5047 <dt class="hdlist1">
5048 <code>deltawalker</code>
5049 </dt>
5050 <dd>
5051 <p>
5052 Use DeltaWalker (requires a graphical session)
5053 </p>
5054 </dd>
5055 <dt class="hdlist1">
5056 <code>diffmerge</code>
5057 </dt>
5058 <dd>
5059 <p>
5060 Use DiffMerge (requires a graphical session)
5061 </p>
5062 </dd>
5063 <dt class="hdlist1">
5064 <code>diffuse</code>
5065 </dt>
5066 <dd>
5067 <p>
5068 Use Diffuse (requires a graphical session)
5069 </p>
5070 </dd>
5071 <dt class="hdlist1">
5072 <code>ecmerge</code>
5073 </dt>
5074 <dd>
5075 <p>
5076 Use ECMerge (requires a graphical session)
5077 </p>
5078 </dd>
5079 <dt class="hdlist1">
5080 <code>emerge</code>
5081 </dt>
5082 <dd>
5083 <p>
5084 Use Emacs' Emerge
5085 </p>
5086 </dd>
5087 <dt class="hdlist1">
5088 <code>examdiff</code>
5089 </dt>
5090 <dd>
5091 <p>
5092 Use ExamDiff Pro (requires a graphical session)
5093 </p>
5094 </dd>
5095 <dt class="hdlist1">
5096 <code>guiffy</code>
5097 </dt>
5098 <dd>
5099 <p>
5100 Use Guiffy&#8217;s Diff Tool (requires a graphical session)
5101 </p>
5102 </dd>
5103 <dt class="hdlist1">
5104 <code>gvimdiff</code>
5105 </dt>
5106 <dd>
5107 <p>
5108 Use gVim (requires a graphical session)
5109 </p>
5110 </dd>
5111 <dt class="hdlist1">
5112 <code>kdiff3</code>
5113 </dt>
5114 <dd>
5115 <p>
5116 Use KDiff3 (requires a graphical session)
5117 </p>
5118 </dd>
5119 <dt class="hdlist1">
5120 <code>kompare</code>
5121 </dt>
5122 <dd>
5123 <p>
5124 Use Kompare (requires a graphical session)
5125 </p>
5126 </dd>
5127 <dt class="hdlist1">
5128 <code>meld</code>
5129 </dt>
5130 <dd>
5131 <p>
5132 Use Meld (requires a graphical session)
5133 </p>
5134 </dd>
5135 <dt class="hdlist1">
5136 <code>nvimdiff</code>
5137 </dt>
5138 <dd>
5139 <p>
5140 Use Neovim
5141 </p>
5142 </dd>
5143 <dt class="hdlist1">
5144 <code>opendiff</code>
5145 </dt>
5146 <dd>
5147 <p>
5148 Use FileMerge (requires a graphical session)
5149 </p>
5150 </dd>
5151 <dt class="hdlist1">
5152 <code>p4merge</code>
5153 </dt>
5154 <dd>
5155 <p>
5156 Use HelixCore P4Merge (requires a graphical session)
5157 </p>
5158 </dd>
5159 <dt class="hdlist1">
5160 <code>smerge</code>
5161 </dt>
5162 <dd>
5163 <p>
5164 Use Sublime Merge (requires a graphical session)
5165 </p>
5166 </dd>
5167 <dt class="hdlist1">
5168 <code>tkdiff</code>
5169 </dt>
5170 <dd>
5171 <p>
5172 Use TkDiff (requires a graphical session)
5173 </p>
5174 </dd>
5175 <dt class="hdlist1">
5176 <code>vimdiff</code>
5177 </dt>
5178 <dd>
5179 <p>
5180 Use Vim
5181 </p>
5182 </dd>
5183 <dt class="hdlist1">
5184 <code>winmerge</code>
5185 </dt>
5186 <dd>
5187 <p>
5188 Use WinMerge (requires a graphical session)
5189 </p>
5190 </dd>
5191 <dt class="hdlist1">
5192 <code>xxdiff</code>
5193 </dt>
5194 <dd>
5195 <p>
5196 Use xxdiff (requires a graphical session)
5197 </p>
5198 </dd>
5199 </dl></div>
5200 </dd>
5201 <dt class="hdlist1">
5202 diff.indentHeuristic
5203 </dt>
5204 <dd>
5205 <p>
5206         Set this option to <code>false</code> to disable the default heuristics
5207         that shift diff hunk boundaries to make patches easier to read.
5208 </p>
5209 </dd>
5210 <dt class="hdlist1">
5211 diff.algorithm
5212 </dt>
5213 <dd>
5214 <p>
5215         Choose a diff algorithm.  The variants are as follows:
5216 </p>
5217 <div class="openblock">
5218 <div class="content">
5219 <div class="dlist"><dl>
5220 <dt class="hdlist1">
5221 <code>default</code>, <code>myers</code>
5222 </dt>
5223 <dd>
5224 <p>
5225         The basic greedy diff algorithm. Currently, this is the default.
5226 </p>
5227 </dd>
5228 <dt class="hdlist1">
5229 <code>minimal</code>
5230 </dt>
5231 <dd>
5232 <p>
5233         Spend extra time to make sure the smallest possible diff is
5234         produced.
5235 </p>
5236 </dd>
5237 <dt class="hdlist1">
5238 <code>patience</code>
5239 </dt>
5240 <dd>
5241 <p>
5242         Use "patience diff" algorithm when generating patches.
5243 </p>
5244 </dd>
5245 <dt class="hdlist1">
5246 <code>histogram</code>
5247 </dt>
5248 <dd>
5249 <p>
5250         This algorithm extends the patience algorithm to "support
5251         low-occurrence common elements".
5252 </p>
5253 </dd>
5254 </dl></div>
5255 </div></div>
5256 </dd>
5257 <dt class="hdlist1">
5258 diff.wsErrorHighlight
5259 </dt>
5260 <dd>
5261 <p>
5262         Highlight whitespace errors in the <code>context</code>, <code>old</code> or <code>new</code>
5263         lines of the diff.  Multiple values are separated by comma,
5264         <code>none</code> resets previous values, <code>default</code> reset the list to
5265         <code>new</code> and <code>all</code> is a shorthand for <code>old,new,context</code>.  The
5266         whitespace errors are colored with <code>color.diff.whitespace</code>.
5267         The command line option <code>--ws-error-highlight=&lt;kind&gt;</code>
5268         overrides this setting.
5269 </p>
5270 </dd>
5271 <dt class="hdlist1">
5272 diff.colorMoved
5273 </dt>
5274 <dd>
5275 <p>
5276         If set to either a valid <code>&lt;mode&gt;</code> or a true value, moved lines
5277         in a diff are colored differently, for details of valid modes
5278         see <em>--color-moved</em> in <a href="git-diff.html">git-diff(1)</a>. If simply set to
5279         true the default color mode will be used. When set to false,
5280         moved lines are not colored.
5281 </p>
5282 </dd>
5283 <dt class="hdlist1">
5284 diff.colorMovedWS
5285 </dt>
5286 <dd>
5287 <p>
5288         When moved lines are colored using e.g. the <code>diff.colorMoved</code> setting,
5289         this option controls the <code>&lt;mode&gt;</code> how spaces are treated
5290         for details of valid modes see <em>--color-moved-ws</em> in <a href="git-diff.html">git-diff(1)</a>.
5291 </p>
5292 </dd>
5293 <dt class="hdlist1">
5294 diff.tool
5295 </dt>
5296 <dd>
5297 <p>
5298         Controls which diff tool is used by <a href="git-difftool.html">git-difftool(1)</a>.
5299         This variable overrides the value configured in <code>merge.tool</code>.
5300         The list below shows the valid built-in values.
5301         Any other value is treated as a custom diff tool and requires
5302         that a corresponding difftool.&lt;tool&gt;.cmd variable is defined.
5303 </p>
5304 </dd>
5305 <dt class="hdlist1">
5306 diff.guitool
5307 </dt>
5308 <dd>
5309 <p>
5310         Controls which diff tool is used by <a href="git-difftool.html">git-difftool(1)</a> when
5311         the -g/--gui flag is specified. This variable overrides the value
5312         configured in <code>merge.guitool</code>. The list below shows the valid
5313         built-in values. Any other value is treated as a custom diff tool
5314         and requires that a corresponding difftool.&lt;guitool&gt;.cmd variable
5315         is defined.
5316 </p>
5317 </dd>
5318 <dt class="hdlist1">
5319 difftool.&lt;tool&gt;.cmd
5320 </dt>
5321 <dd>
5322 <p>
5323         Specify the command to invoke the specified diff tool.
5324         The specified command is evaluated in shell with the following
5325         variables available:  <em>LOCAL</em> is set to the name of the temporary
5326         file containing the contents of the diff pre-image and <em>REMOTE</em>
5327         is set to the name of the temporary file containing the contents
5328         of the diff post-image.
5329 </p>
5330 <div class="paragraph"><p>See the <code>--tool=&lt;tool&gt;</code> option in <a href="git-difftool.html">git-difftool(1)</a> for more details.</p></div>
5331 </dd>
5332 <dt class="hdlist1">
5333 difftool.&lt;tool&gt;.path
5334 </dt>
5335 <dd>
5336 <p>
5337         Override the path for the given tool.  This is useful in case
5338         your tool is not in the PATH.
5339 </p>
5340 </dd>
5341 <dt class="hdlist1">
5342 difftool.trustExitCode
5343 </dt>
5344 <dd>
5345 <p>
5346         Exit difftool if the invoked diff tool returns a non-zero exit status.
5347 </p>
5348 <div class="paragraph"><p>See the <code>--trust-exit-code</code> option in <a href="git-difftool.html">git-difftool(1)</a> for more details.</p></div>
5349 </dd>
5350 <dt class="hdlist1">
5351 difftool.prompt
5352 </dt>
5353 <dd>
5354 <p>
5355         Prompt before each invocation of the diff tool.
5356 </p>
5357 </dd>
5358 <dt class="hdlist1">
5359 difftool.guiDefault
5360 </dt>
5361 <dd>
5362 <p>
5363         Set <code>true</code> to use the <code>diff.guitool</code> by default (equivalent to specifying
5364         the <code>--gui</code> argument), or <code>auto</code> to select <code>diff.guitool</code> or <code>diff.tool</code>
5365         depending on the presence of a <code>DISPLAY</code> environment variable value. The
5366         default is <code>false</code>, where the <code>--gui</code> argument must be provided
5367         explicitly for the <code>diff.guitool</code> to be used.
5368 </p>
5369 </dd>
5370 <dt class="hdlist1">
5371 extensions.objectFormat
5372 </dt>
5373 <dd>
5374 <p>
5375         Specify the hash algorithm to use.  The acceptable values are <code>sha1</code> and
5376         <code>sha256</code>.  If not specified, <code>sha1</code> is assumed.  It is an error to specify
5377         this key unless <code>core.repositoryFormatVersion</code> is 1.
5378 </p>
5379 <div class="paragraph"><p>Note that this setting should only be set by <a href="git-init.html">git-init(1)</a> or
5380 <a href="git-clone.html">git-clone(1)</a>.  Trying to change it after initialization will not
5381 work and will produce hard-to-diagnose issues.</p></div>
5382 </dd>
5383 <dt class="hdlist1">
5384 extensions.worktreeConfig
5385 </dt>
5386 <dd>
5387 <p>
5388         If enabled, then worktrees will load config settings from the
5389         <code>$GIT_DIR/config.worktree</code> file in addition to the
5390         <code>$GIT_COMMON_DIR/config</code> file. Note that <code>$GIT_COMMON_DIR</code> and
5391         <code>$GIT_DIR</code> are the same for the main working tree, while other
5392         working trees have <code>$GIT_DIR</code> equal to
5393         <code>$GIT_COMMON_DIR/worktrees/&lt;id&gt;/</code>. The settings in the
5394         <code>config.worktree</code> file will override settings from any other
5395         config files.
5396 </p>
5397 <div class="paragraph"><p>When enabling <code>extensions.worktreeConfig</code>, you must be careful to move
5398 certain values from the common config file to the main working tree&#8217;s
5399 <code>config.worktree</code> file, if present:</p></div>
5400 <div class="ulist"><ul>
5401 <li>
5402 <p>
5403 <code>core.worktree</code> must be moved from <code>$GIT_COMMON_DIR/config</code> to
5404   <code>$GIT_COMMON_DIR/config.worktree</code>.
5405 </p>
5406 </li>
5407 <li>
5408 <p>
5409 If <code>core.bare</code> is true, then it must be moved from <code>$GIT_COMMON_DIR/config</code>
5410   to <code>$GIT_COMMON_DIR/config.worktree</code>.
5411 </p>
5412 <div class="paragraph"><p>It may also be beneficial to adjust the locations of <code>core.sparseCheckout</code>
5413 and <code>core.sparseCheckoutCone</code> depending on your desire for customizable
5414 sparse-checkout settings for each worktree. By default, the <code>git
5415 sparse-checkout</code> builtin enables <code>extensions.worktreeConfig</code>, assigns
5416 these config values on a per-worktree basis, and uses the
5417 <code>$GIT_DIR/info/sparse-checkout</code> file to specify the sparsity for each
5418 worktree independently. See <a href="git-sparse-checkout.html">git-sparse-checkout(1)</a> for more
5419 details.</p></div>
5420 <div class="paragraph"><p>For historical reasons, <code>extensions.worktreeConfig</code> is respected
5421 regardless of the <code>core.repositoryFormatVersion</code> setting.</p></div>
5422 </li>
5423 </ul></div>
5424 </dd>
5425 <dt class="hdlist1">
5426 fastimport.unpackLimit
5427 </dt>
5428 <dd>
5429 <p>
5430         If the number of objects imported by <a href="git-fast-import.html">git-fast-import(1)</a>
5431         is below this limit, then the objects will be unpacked into
5432         loose object files.  However if the number of imported objects
5433         equals or exceeds this limit then the pack will be stored as a
5434         pack.  Storing the pack from a fast-import can make the import
5435         operation complete faster, especially on slow filesystems.  If
5436         not set, the value of <code>transfer.unpackLimit</code> is used instead.
5437 </p>
5438 </dd>
5439 <dt class="hdlist1">
5440 feature.*
5441 </dt>
5442 <dd>
5443 <p>
5444         The config settings that start with <code>feature.</code> modify the defaults of
5445         a group of other config settings. These groups are created by the Git
5446         developer community as recommended defaults and are subject to change.
5447         In particular, new config options may be added with different defaults.
5448 </p>
5449 </dd>
5450 <dt class="hdlist1">
5451 feature.experimental
5452 </dt>
5453 <dd>
5454 <p>
5455         Enable config options that are new to Git, and are being considered for
5456         future defaults. Config settings included here may be added or removed
5457         with each release, including minor version updates. These settings may
5458         have unintended interactions since they are so new. Please enable this
5459         setting if you are interested in providing feedback on experimental
5460         features. The new default values are:
5461 </p>
5462 <div class="ulist"><ul>
5463 <li>
5464 <p>
5465 <code>fetch.negotiationAlgorithm=skipping</code> may improve fetch negotiation times by
5466 skipping more commits at a time, reducing the number of round trips.
5467 </p>
5468 </li>
5469 <li>
5470 <p>
5471 <code>pack.useBitmapBoundaryTraversal=true</code> may improve bitmap traversal times by
5472 walking fewer objects.
5473 </p>
5474 </li>
5475 </ul></div>
5476 </dd>
5477 <dt class="hdlist1">
5478 feature.manyFiles
5479 </dt>
5480 <dd>
5481 <p>
5482         Enable config options that optimize for repos with many files in the
5483         working directory. With many files, commands such as <code>git status</code> and
5484         <code>git checkout</code> may be slow and these new defaults improve performance:
5485 </p>
5486 <div class="ulist"><ul>
5487 <li>
5488 <p>
5489 <code>index.skipHash=true</code> speeds up index writes by not computing a trailing
5490   checksum. Note that this will cause Git versions earlier than 2.13.0 to
5491   refuse to parse the index and Git versions earlier than 2.40.0 will report
5492   a corrupted index during <code>git fsck</code>.
5493 </p>
5494 </li>
5495 <li>
5496 <p>
5497 <code>index.version=4</code> enables path-prefix compression in the index.
5498 </p>
5499 </li>
5500 <li>
5501 <p>
5502 <code>core.untrackedCache=true</code> enables the untracked cache. This setting assumes
5503 that mtime is working on your machine.
5504 </p>
5505 </li>
5506 </ul></div>
5507 </dd>
5508 <dt class="hdlist1">
5509 fetch.recurseSubmodules
5510 </dt>
5511 <dd>
5512 <p>
5513         This option controls whether <code>git fetch</code> (and the underlying fetch
5514         in <code>git pull</code>) will recursively fetch into populated submodules.
5515         This option can be set either to a boolean value or to <em>on-demand</em>.
5516         Setting it to a boolean changes the behavior of fetch and pull to
5517         recurse unconditionally into submodules when set to true or to not
5518         recurse at all when set to false. When set to <em>on-demand</em>, fetch and
5519         pull will only recurse into a populated submodule when its
5520         superproject retrieves a commit that updates the submodule&#8217;s
5521         reference.
5522         Defaults to <em>on-demand</em>, or to the value of <em>submodule.recurse</em> if set.
5523 </p>
5524 </dd>
5525 <dt class="hdlist1">
5526 fetch.fsckObjects
5527 </dt>
5528 <dd>
5529 <p>
5530         If it is set to true, git-fetch-pack will check all fetched
5531         objects. See <code>transfer.fsckObjects</code> for what&#8217;s
5532         checked. Defaults to false. If not set, the value of
5533         <code>transfer.fsckObjects</code> is used instead.
5534 </p>
5535 </dd>
5536 <dt class="hdlist1">
5537 fetch.fsck.&lt;msg-id&gt;
5538 </dt>
5539 <dd>
5540 <p>
5541         Acts like <code>fsck.&lt;msg-id&gt;</code>, but is used by
5542         <a href="git-fetch-pack.html">git-fetch-pack(1)</a> instead of <a href="git-fsck.html">git-fsck(1)</a>. See
5543         the <code>fsck.&lt;msg-id&gt;</code> documentation for details.
5544 </p>
5545 </dd>
5546 <dt class="hdlist1">
5547 fetch.fsck.skipList
5548 </dt>
5549 <dd>
5550 <p>
5551         Acts like <code>fsck.skipList</code>, but is used by
5552         <a href="git-fetch-pack.html">git-fetch-pack(1)</a> instead of <a href="git-fsck.html">git-fsck(1)</a>. See
5553         the <code>fsck.skipList</code> documentation for details.
5554 </p>
5555 </dd>
5556 <dt class="hdlist1">
5557 fetch.unpackLimit
5558 </dt>
5559 <dd>
5560 <p>
5561         If the number of objects fetched over the Git native
5562         transfer is below this
5563         limit, then the objects will be unpacked into loose object
5564         files. However if the number of received objects equals or
5565         exceeds this limit then the received pack will be stored as
5566         a pack, after adding any missing delta bases.  Storing the
5567         pack from a push can make the push operation complete faster,
5568         especially on slow filesystems.  If not set, the value of
5569         <code>transfer.unpackLimit</code> is used instead.
5570 </p>
5571 </dd>
5572 <dt class="hdlist1">
5573 fetch.prune
5574 </dt>
5575 <dd>
5576 <p>
5577         If true, fetch will automatically behave as if the <code>--prune</code>
5578         option was given on the command line.  See also <code>remote.&lt;name&gt;.prune</code>
5579         and the PRUNING section of <a href="git-fetch.html">git-fetch(1)</a>.
5580 </p>
5581 </dd>
5582 <dt class="hdlist1">
5583 fetch.pruneTags
5584 </dt>
5585 <dd>
5586 <p>
5587         If true, fetch will automatically behave as if the
5588         <code>refs/tags/*:refs/tags/*</code> refspec was provided when pruning,
5589         if not set already. This allows for setting both this option
5590         and <code>fetch.prune</code> to maintain a 1=1 mapping to upstream
5591         refs. See also <code>remote.&lt;name&gt;.pruneTags</code> and the PRUNING
5592         section of <a href="git-fetch.html">git-fetch(1)</a>.
5593 </p>
5594 </dd>
5595 <dt class="hdlist1">
5596 fetch.output
5597 </dt>
5598 <dd>
5599 <p>
5600         Control how ref update status is printed. Valid values are
5601         <code>full</code> and <code>compact</code>. Default value is <code>full</code>. See section
5602         OUTPUT in <a href="git-fetch.html">git-fetch(1)</a> for detail.
5603 </p>
5604 </dd>
5605 <dt class="hdlist1">
5606 fetch.negotiationAlgorithm
5607 </dt>
5608 <dd>
5609 <p>
5610         Control how information about the commits in the local repository
5611         is sent when negotiating the contents of the packfile to be sent by
5612         the server.  Set to "consecutive" to use an algorithm that walks
5613         over consecutive commits checking each one.  Set to "skipping" to
5614         use an algorithm that skips commits in an effort to converge
5615         faster, but may result in a larger-than-necessary packfile; or set
5616         to "noop" to not send any information at all, which will almost
5617         certainly result in a larger-than-necessary packfile, but will skip
5618         the negotiation step.  Set to "default" to override settings made
5619         previously and use the default behaviour.  The default is normally
5620         "consecutive", but if <code>feature.experimental</code> is true, then the
5621         default is "skipping".  Unknown values will cause <em>git fetch</em> to
5622         error out.
5623 </p>
5624 <div class="paragraph"><p>See also the <code>--negotiate-only</code> and <code>--negotiation-tip</code> options to
5625 <a href="git-fetch.html">git-fetch(1)</a>.</p></div>
5626 </dd>
5627 <dt class="hdlist1">
5628 fetch.showForcedUpdates
5629 </dt>
5630 <dd>
5631 <p>
5632         Set to false to enable <code>--no-show-forced-updates</code> in
5633         <a href="git-fetch.html">git-fetch(1)</a> and <a href="git-pull.html">git-pull(1)</a> commands.
5634         Defaults to true.
5635 </p>
5636 </dd>
5637 <dt class="hdlist1">
5638 fetch.parallel
5639 </dt>
5640 <dd>
5641 <p>
5642         Specifies the maximal number of fetch operations to be run in parallel
5643         at a time (submodules, or remotes when the <code>--multiple</code> option of
5644         <a href="git-fetch.html">git-fetch(1)</a> is in effect).
5645 </p>
5646 <div class="paragraph"><p>A value of 0 will give some reasonable default. If unset, it defaults to 1.</p></div>
5647 <div class="paragraph"><p>For submodules, this setting can be overridden using the <code>submodule.fetchJobs</code>
5648 config setting.</p></div>
5649 </dd>
5650 <dt class="hdlist1">
5651 fetch.writeCommitGraph
5652 </dt>
5653 <dd>
5654 <p>
5655         Set to true to write a commit-graph after every <code>git fetch</code> command
5656         that downloads a pack-file from a remote. Using the <code>--split</code> option,
5657         most executions will create a very small commit-graph file on top of
5658         the existing commit-graph file(s). Occasionally, these files will
5659         merge and the write may take longer. Having an updated commit-graph
5660         file helps performance of many Git commands, including <code>git merge-base</code>,
5661         <code>git push -f</code>, and <code>git log --graph</code>. Defaults to false.
5662 </p>
5663 </dd>
5664 <dt class="hdlist1">
5665 fetch.bundleURI
5666 </dt>
5667 <dd>
5668 <p>
5669         This value stores a URI for downloading Git object data from a bundle
5670         URI before performing an incremental fetch from the origin Git server.
5671         This is similar to how the <code>--bundle-uri</code> option behaves in
5672         <a href="git-clone.html">git-clone(1)</a>. <code>git clone --bundle-uri</code> will set the
5673         <code>fetch.bundleURI</code> value if the supplied bundle URI contains a bundle
5674         list that is organized for incremental fetches.
5675 </p>
5676 <div class="paragraph"><p>If you modify this value and your repository has a <code>fetch.bundleCreationToken</code>
5677 value, then remove that <code>fetch.bundleCreationToken</code> value before fetching from
5678 the new bundle URI.</p></div>
5679 </dd>
5680 <dt class="hdlist1">
5681 fetch.bundleCreationToken
5682 </dt>
5683 <dd>
5684 <p>
5685         When using <code>fetch.bundleURI</code> to fetch incrementally from a bundle
5686         list that uses the "creationToken" heuristic, this config value
5687         stores the maximum <code>creationToken</code> value of the downloaded bundles.
5688         This value is used to prevent downloading bundles in the future
5689         if the advertised <code>creationToken</code> is not strictly larger than this
5690         value.
5691 </p>
5692 <div class="paragraph"><p>The creation token values are chosen by the provider serving the specific
5693 bundle URI. If you modify the URI at <code>fetch.bundleURI</code>, then be sure to
5694 remove the value for the <code>fetch.bundleCreationToken</code> value before fetching.</p></div>
5695 </dd>
5696 <dt class="hdlist1">
5697 format.attach
5698 </dt>
5699 <dd>
5700 <p>
5701         Enable multipart/mixed attachments as the default for
5702         <em>format-patch</em>.  The value can also be a double quoted string
5703         which will enable attachments as the default and set the
5704         value as the boundary.  See the --attach option in
5705         <a href="git-format-patch.html">git-format-patch(1)</a>.  To countermand an earlier
5706         value, set it to an empty string.
5707 </p>
5708 </dd>
5709 <dt class="hdlist1">
5710 format.from
5711 </dt>
5712 <dd>
5713 <p>
5714         Provides the default value for the <code>--from</code> option to format-patch.
5715         Accepts a boolean value, or a name and email address.  If false,
5716         format-patch defaults to <code>--no-from</code>, using commit authors directly in
5717         the "From:" field of patch mails.  If true, format-patch defaults to
5718         <code>--from</code>, using your committer identity in the "From:" field of patch
5719         mails and including a "From:" field in the body of the patch mail if
5720         different.  If set to a non-boolean value, format-patch uses that
5721         value instead of your committer identity.  Defaults to false.
5722 </p>
5723 </dd>
5724 <dt class="hdlist1">
5725 format.forceInBodyFrom
5726 </dt>
5727 <dd>
5728 <p>
5729         Provides the default value for the <code>--[no-]force-in-body-from</code>
5730         option to format-patch.  Defaults to false.
5731 </p>
5732 </dd>
5733 <dt class="hdlist1">
5734 format.numbered
5735 </dt>
5736 <dd>
5737 <p>
5738         A boolean which can enable or disable sequence numbers in patch
5739         subjects.  It defaults to "auto" which enables it only if there
5740         is more than one patch.  It can be enabled or disabled for all
5741         messages by setting it to "true" or "false".  See --numbered
5742         option in <a href="git-format-patch.html">git-format-patch(1)</a>.
5743 </p>
5744 </dd>
5745 <dt class="hdlist1">
5746 format.headers
5747 </dt>
5748 <dd>
5749 <p>
5750         Additional email headers to include in a patch to be submitted
5751         by mail.  See <a href="git-format-patch.html">git-format-patch(1)</a>.
5752 </p>
5753 </dd>
5754 <dt class="hdlist1">
5755 format.to
5756 </dt>
5757 <dt class="hdlist1">
5758 format.cc
5759 </dt>
5760 <dd>
5761 <p>
5762         Additional recipients to include in a patch to be submitted
5763         by mail.  See the --to and --cc options in
5764         <a href="git-format-patch.html">git-format-patch(1)</a>.
5765 </p>
5766 </dd>
5767 <dt class="hdlist1">
5768 format.subjectPrefix
5769 </dt>
5770 <dd>
5771 <p>
5772         The default for format-patch is to output files with the <em>[PATCH]</em>
5773         subject prefix. Use this variable to change that prefix.
5774 </p>
5775 </dd>
5776 <dt class="hdlist1">
5777 format.coverFromDescription
5778 </dt>
5779 <dd>
5780 <p>
5781         The default mode for format-patch to determine which parts of
5782         the cover letter will be populated using the branch&#8217;s
5783         description. See the <code>--cover-from-description</code> option in
5784         <a href="git-format-patch.html">git-format-patch(1)</a>.
5785 </p>
5786 </dd>
5787 <dt class="hdlist1">
5788 format.signature
5789 </dt>
5790 <dd>
5791 <p>
5792         The default for format-patch is to output a signature containing
5793         the Git version number. Use this variable to change that default.
5794         Set this variable to the empty string ("") to suppress
5795         signature generation.
5796 </p>
5797 </dd>
5798 <dt class="hdlist1">
5799 format.signatureFile
5800 </dt>
5801 <dd>
5802 <p>
5803         Works just like format.signature except the contents of the
5804         file specified by this variable will be used as the signature.
5805 </p>
5806 </dd>
5807 <dt class="hdlist1">
5808 format.suffix
5809 </dt>
5810 <dd>
5811 <p>
5812         The default for format-patch is to output files with the suffix
5813         <code>.patch</code>. Use this variable to change that suffix (make sure to
5814         include the dot if you want it).
5815 </p>
5816 </dd>
5817 <dt class="hdlist1">
5818 format.encodeEmailHeaders
5819 </dt>
5820 <dd>
5821 <p>
5822         Encode email headers that have non-ASCII characters with
5823         "Q-encoding" (described in RFC 2047) for email transmission.
5824         Defaults to true.
5825 </p>
5826 </dd>
5827 <dt class="hdlist1">
5828 format.pretty
5829 </dt>
5830 <dd>
5831 <p>
5832         The default pretty format for log/show/whatchanged command,
5833         See <a href="git-log.html">git-log(1)</a>, <a href="git-show.html">git-show(1)</a>,
5834         <a href="git-whatchanged.html">git-whatchanged(1)</a>.
5835 </p>
5836 </dd>
5837 <dt class="hdlist1">
5838 format.thread
5839 </dt>
5840 <dd>
5841 <p>
5842         The default threading style for <em>git format-patch</em>.  Can be
5843         a boolean value, or <code>shallow</code> or <code>deep</code>.  <code>shallow</code> threading
5844         makes every mail a reply to the head of the series,
5845         where the head is chosen from the cover letter, the
5846         <code>--in-reply-to</code>, and the first patch mail, in this order.
5847         <code>deep</code> threading makes every mail a reply to the previous one.
5848         A true boolean value is the same as <code>shallow</code>, and a false
5849         value disables threading.
5850 </p>
5851 </dd>
5852 <dt class="hdlist1">
5853 format.signOff
5854 </dt>
5855 <dd>
5856 <p>
5857         A boolean value which lets you enable the <code>-s/--signoff</code> option of
5858         format-patch by default. <strong>Note:</strong> Adding the <code>Signed-off-by</code> trailer to a
5859         patch should be a conscious act and means that you certify you have
5860         the rights to submit this work under the same open source license.
5861         Please see the <em>SubmittingPatches</em> document for further discussion.
5862 </p>
5863 </dd>
5864 <dt class="hdlist1">
5865 format.coverLetter
5866 </dt>
5867 <dd>
5868 <p>
5869         A boolean that controls whether to generate a cover-letter when
5870         format-patch is invoked, but in addition can be set to "auto", to
5871         generate a cover-letter only when there&#8217;s more than one patch.
5872         Default is false.
5873 </p>
5874 </dd>
5875 <dt class="hdlist1">
5876 format.outputDirectory
5877 </dt>
5878 <dd>
5879 <p>
5880         Set a custom directory to store the resulting files instead of the
5881         current working directory. All directory components will be created.
5882 </p>
5883 </dd>
5884 <dt class="hdlist1">
5885 format.filenameMaxLength
5886 </dt>
5887 <dd>
5888 <p>
5889         The maximum length of the output filenames generated by the
5890         <code>format-patch</code> command; defaults to 64.  Can be overridden
5891         by the <code>--filename-max-length=&lt;n&gt;</code> command line option.
5892 </p>
5893 </dd>
5894 <dt class="hdlist1">
5895 format.useAutoBase
5896 </dt>
5897 <dd>
5898 <p>
5899         A boolean value which lets you enable the <code>--base=auto</code> option of
5900         format-patch by default. Can also be set to "whenAble" to allow
5901         enabling <code>--base=auto</code> if a suitable base is available, but to skip
5902         adding base info otherwise without the format dying.
5903 </p>
5904 </dd>
5905 <dt class="hdlist1">
5906 format.notes
5907 </dt>
5908 <dd>
5909 <p>
5910         Provides the default value for the <code>--notes</code> option to
5911         format-patch. Accepts a boolean value, or a ref which specifies
5912         where to get notes. If false, format-patch defaults to
5913         <code>--no-notes</code>. If true, format-patch defaults to <code>--notes</code>. If
5914         set to a non-boolean value, format-patch defaults to
5915         <code>--notes=&lt;ref&gt;</code>, where <code>ref</code> is the non-boolean value. Defaults
5916         to false.
5917 </p>
5918 <div class="paragraph"><p>If one wishes to use the ref <code>ref/notes/true</code>, please use that literal
5919 instead.</p></div>
5920 <div class="paragraph"><p>This configuration can be specified multiple times in order to allow
5921 multiple notes refs to be included. In that case, it will behave
5922 similarly to multiple <code>--[no-]notes[=]</code> options passed in. That is, a
5923 value of <code>true</code> will show the default notes, a value of <code>&lt;ref&gt;</code> will
5924 also show notes from that notes ref and a value of <code>false</code> will negate
5925 previous configurations and not show notes.</p></div>
5926 <div class="paragraph"><p>For example,</p></div>
5927 <div class="listingblock">
5928 <div class="content">
5929 <pre><code>[format]
5930         notes = true
5931         notes = foo
5932         notes = false
5933         notes = bar</code></pre>
5934 </div></div>
5935 <div class="paragraph"><p>will only show notes from <code>refs/notes/bar</code>.</p></div>
5936 </dd>
5937 <dt class="hdlist1">
5938 format.mboxrd
5939 </dt>
5940 <dd>
5941 <p>
5942         A boolean value which enables the robust "mboxrd" format when
5943         <code>--stdout</code> is in use to escape "^&gt;+From " lines.
5944 </p>
5945 </dd>
5946 <dt class="hdlist1">
5947 format.noprefix
5948 </dt>
5949 <dd>
5950 <p>
5951         If set, do not show any source or destination prefix in patches.
5952         This is equivalent to the <code>diff.noprefix</code> option used by <code>git
5953         diff</code> (but which is not respected by <code>format-patch</code>). Note that
5954         by setting this, the receiver of any patches you generate will
5955         have to apply them using the <code>-p0</code> option.
5956 </p>
5957 </dd>
5958 <dt class="hdlist1">
5959 filter.&lt;driver&gt;.clean
5960 </dt>
5961 <dd>
5962 <p>
5963         The command which is used to convert the content of a worktree
5964         file to a blob upon checkin.  See <a href="gitattributes.html">gitattributes(5)</a> for
5965         details.
5966 </p>
5967 </dd>
5968 <dt class="hdlist1">
5969 filter.&lt;driver&gt;.smudge
5970 </dt>
5971 <dd>
5972 <p>
5973         The command which is used to convert the content of a blob
5974         object to a worktree file upon checkout.  See
5975         <a href="gitattributes.html">gitattributes(5)</a> for details.
5976 </p>
5977 </dd>
5978 <dt class="hdlist1">
5979 fsck.&lt;msg-id&gt;
5980 </dt>
5981 <dd>
5982 <p>
5983         During fsck git may find issues with legacy data which
5984         wouldn&#8217;t be generated by current versions of git, and which
5985         wouldn&#8217;t be sent over the wire if <code>transfer.fsckObjects</code> was
5986         set. This feature is intended to support working with legacy
5987         repositories containing such data.
5988 </p>
5989 <div class="paragraph"><p>Setting <code>fsck.&lt;msg-id&gt;</code> will be picked up by <a href="git-fsck.html">git-fsck(1)</a>, but
5990 to accept pushes of such data set <code>receive.fsck.&lt;msg-id&gt;</code> instead, or
5991 to clone or fetch it set <code>fetch.fsck.&lt;msg-id&gt;</code>.</p></div>
5992 <div class="paragraph"><p>The rest of the documentation discusses <code>fsck.*</code> for brevity, but the
5993 same applies for the corresponding <code>receive.fsck.*</code> and
5994 <code>fetch.&lt;msg-id&gt;.*</code>. variables.</p></div>
5995 <div class="paragraph"><p>Unlike variables like <code>color.ui</code> and <code>core.editor</code> the
5996 <code>receive.fsck.&lt;msg-id&gt;</code> and <code>fetch.fsck.&lt;msg-id&gt;</code> variables will not
5997 fall back on the <code>fsck.&lt;msg-id&gt;</code> configuration if they aren&#8217;t set. To
5998 uniformly configure the same fsck settings in different circumstances
5999 all three of them they must all set to the same values.</p></div>
6000 <div class="paragraph"><p>When <code>fsck.&lt;msg-id&gt;</code> is set, errors can be switched to warnings and
6001 vice versa by configuring the <code>fsck.&lt;msg-id&gt;</code> setting where the
6002 <code>&lt;msg-id&gt;</code> is the fsck message ID and the value is one of <code>error</code>,
6003 <code>warn</code> or <code>ignore</code>. For convenience, fsck prefixes the error/warning
6004 with the message ID, e.g. "missingEmail: invalid author/committer
6005 line - missing email" means that setting <code>fsck.missingEmail = ignore</code>
6006 will hide that issue.</p></div>
6007 <div class="paragraph"><p>In general, it is better to enumerate existing objects with problems
6008 with <code>fsck.skipList</code>, instead of listing the kind of breakages these
6009 problematic objects share to be ignored, as doing the latter will
6010 allow new instances of the same breakages go unnoticed.</p></div>
6011 <div class="paragraph"><p>Setting an unknown <code>fsck.&lt;msg-id&gt;</code> value will cause fsck to die, but
6012 doing the same for <code>receive.fsck.&lt;msg-id&gt;</code> and <code>fetch.fsck.&lt;msg-id&gt;</code>
6013 will only cause git to warn.</p></div>
6014 <div class="paragraph"><p>See <code>Fsck Messages</code> section of <a href="git-fsck.html">git-fsck(1)</a> for supported
6015 values of <code>&lt;msg-id&gt;</code>.</p></div>
6016 </dd>
6017 <dt class="hdlist1">
6018 fsck.skipList
6019 </dt>
6020 <dd>
6021 <p>
6022         The path to a list of object names (i.e. one unabbreviated SHA-1 per
6023         line) that are known to be broken in a non-fatal way and should
6024         be ignored. On versions of Git 2.20 and later comments (<em>#</em>), empty
6025         lines, and any leading and trailing whitespace is ignored. Everything
6026         but a SHA-1 per line will error out on older versions.
6027 </p>
6028 <div class="paragraph"><p>This feature is useful when an established project should be accepted
6029 despite early commits containing errors that can be safely ignored
6030 such as invalid committer email addresses.  Note: corrupt objects
6031 cannot be skipped with this setting.</p></div>
6032 <div class="paragraph"><p>Like <code>fsck.&lt;msg-id&gt;</code> this variable has corresponding
6033 <code>receive.fsck.skipList</code> and <code>fetch.fsck.skipList</code> variants.</p></div>
6034 <div class="paragraph"><p>Unlike variables like <code>color.ui</code> and <code>core.editor</code> the
6035 <code>receive.fsck.skipList</code> and <code>fetch.fsck.skipList</code> variables will not
6036 fall back on the <code>fsck.skipList</code> configuration if they aren&#8217;t set. To
6037 uniformly configure the same fsck settings in different circumstances
6038 all three of them they must all set to the same values.</p></div>
6039 <div class="paragraph"><p>Older versions of Git (before 2.20) documented that the object names
6040 list should be sorted. This was never a requirement, the object names
6041 could appear in any order, but when reading the list we tracked whether
6042 the list was sorted for the purposes of an internal binary search
6043 implementation, which could save itself some work with an already sorted
6044 list. Unless you had a humongous list there was no reason to go out of
6045 your way to pre-sort the list. After Git version 2.20 a hash implementation
6046 is used instead, so there&#8217;s now no reason to pre-sort the list.</p></div>
6047 </dd>
6048 <dt class="hdlist1">
6049 fsmonitor.allowRemote
6050 </dt>
6051 <dd>
6052 <p>
6053     By default, the fsmonitor daemon refuses to work against network-mounted
6054     repositories. Setting <code>fsmonitor.allowRemote</code> to <code>true</code> overrides this
6055     behavior.  Only respected when <code>core.fsmonitor</code> is set to <code>true</code>.
6056 </p>
6057 </dd>
6058 <dt class="hdlist1">
6059 fsmonitor.socketDir
6060 </dt>
6061 <dd>
6062 <p>
6063     This Mac OS-specific option, if set, specifies the directory in
6064     which to create the Unix domain socket used for communication
6065     between the fsmonitor daemon and various Git commands. The directory must
6066     reside on a native Mac OS filesystem.  Only respected when <code>core.fsmonitor</code>
6067     is set to <code>true</code>.
6068 </p>
6069 </dd>
6070 <dt class="hdlist1">
6071 gc.aggressiveDepth
6072 </dt>
6073 <dd>
6074 <p>
6075         The depth parameter used in the delta compression
6076         algorithm used by <em>git gc --aggressive</em>.  This defaults
6077         to 50, which is the default for the <code>--depth</code> option when
6078         <code>--aggressive</code> isn&#8217;t in use.
6079 </p>
6080 <div class="paragraph"><p>See the documentation for the <code>--depth</code> option in
6081 <a href="git-repack.html">git-repack(1)</a> for more details.</p></div>
6082 </dd>
6083 <dt class="hdlist1">
6084 gc.aggressiveWindow
6085 </dt>
6086 <dd>
6087 <p>
6088         The window size parameter used in the delta compression
6089         algorithm used by <em>git gc --aggressive</em>.  This defaults
6090         to 250, which is a much more aggressive window size than
6091         the default <code>--window</code> of 10.
6092 </p>
6093 <div class="paragraph"><p>See the documentation for the <code>--window</code> option in
6094 <a href="git-repack.html">git-repack(1)</a> for more details.</p></div>
6095 </dd>
6096 <dt class="hdlist1">
6097 gc.auto
6098 </dt>
6099 <dd>
6100 <p>
6101         When there are approximately more than this many loose
6102         objects in the repository, <code>git gc --auto</code> will pack them.
6103         Some Porcelain commands use this command to perform a
6104         light-weight garbage collection from time to time.  The
6105         default value is 6700.
6106 </p>
6107 <div class="paragraph"><p>Setting this to 0 disables not only automatic packing based on the
6108 number of loose objects, but any other heuristic <code>git gc --auto</code> will
6109 otherwise use to determine if there&#8217;s work to do, such as
6110 <code>gc.autoPackLimit</code>.</p></div>
6111 </dd>
6112 <dt class="hdlist1">
6113 gc.autoPackLimit
6114 </dt>
6115 <dd>
6116 <p>
6117         When there are more than this many packs that are not
6118         marked with <code>*.keep</code> file in the repository, <code>git gc
6119         --auto</code> consolidates them into one larger pack.  The
6120         default value is 50.  Setting this to 0 disables it.
6121         Setting <code>gc.auto</code> to 0 will also disable this.
6122 </p>
6123 <div class="paragraph"><p>See the <code>gc.bigPackThreshold</code> configuration variable below. When in
6124 use, it&#8217;ll affect how the auto pack limit works.</p></div>
6125 </dd>
6126 <dt class="hdlist1">
6127 gc.autoDetach
6128 </dt>
6129 <dd>
6130 <p>
6131         Make <code>git gc --auto</code> return immediately and run in background
6132         if the system supports it. Default is true.
6133 </p>
6134 </dd>
6135 <dt class="hdlist1">
6136 gc.bigPackThreshold
6137 </dt>
6138 <dd>
6139 <p>
6140         If non-zero, all non-cruft packs larger than this limit are kept
6141         when <code>git gc</code> is run. This is very similar to
6142         <code>--keep-largest-pack</code> except that all non-cruft packs that meet
6143         the threshold are kept, not just the largest pack. Defaults to
6144         zero. Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.
6145 </p>
6146 <div class="paragraph"><p>Note that if the number of kept packs is more than gc.autoPackLimit,
6147 this configuration variable is ignored, all packs except the base pack
6148 will be repacked. After this the number of packs should go below
6149 gc.autoPackLimit and gc.bigPackThreshold should be respected again.</p></div>
6150 <div class="paragraph"><p>If the amount of memory estimated for <code>git repack</code> to run smoothly is
6151 not available and <code>gc.bigPackThreshold</code> is not set, the largest pack
6152 will also be excluded (this is the equivalent of running <code>git gc</code> with
6153 <code>--keep-largest-pack</code>).</p></div>
6154 </dd>
6155 <dt class="hdlist1">
6156 gc.writeCommitGraph
6157 </dt>
6158 <dd>
6159 <p>
6160         If true, then gc will rewrite the commit-graph file when
6161         <a href="git-gc.html">git-gc(1)</a> is run. When using <code>git gc --auto</code>
6162         the commit-graph will be updated if housekeeping is
6163         required. Default is true. See <a href="git-commit-graph.html">git-commit-graph(1)</a>
6164         for details.
6165 </p>
6166 </dd>
6167 <dt class="hdlist1">
6168 gc.logExpiry
6169 </dt>
6170 <dd>
6171 <p>
6172         If the file gc.log exists, then <code>git gc --auto</code> will print
6173         its content and exit with status zero instead of running
6174         unless that file is more than <em>gc.logExpiry</em> old.  Default is
6175         "1.day".  See <code>gc.pruneExpire</code> for more ways to specify its
6176         value.
6177 </p>
6178 </dd>
6179 <dt class="hdlist1">
6180 gc.packRefs
6181 </dt>
6182 <dd>
6183 <p>
6184         Running <code>git pack-refs</code> in a repository renders it
6185         unclonable by Git versions prior to 1.5.1.2 over dumb
6186         transports such as HTTP.  This variable determines whether
6187         <em>git gc</em> runs <code>git pack-refs</code>. This can be set to <code>notbare</code>
6188         to enable it within all non-bare repos or it can be set to a
6189         boolean value.  The default is <code>true</code>.
6190 </p>
6191 </dd>
6192 <dt class="hdlist1">
6193 gc.cruftPacks
6194 </dt>
6195 <dd>
6196 <p>
6197         Store unreachable objects in a cruft pack (see
6198         <a href="git-repack.html">git-repack(1)</a>) instead of as loose objects. The default
6199         is <code>true</code>.
6200 </p>
6201 </dd>
6202 <dt class="hdlist1">
6203 gc.pruneExpire
6204 </dt>
6205 <dd>
6206 <p>
6207         When <em>git gc</em> is run, it will call <em>prune --expire 2.weeks.ago</em>
6208         (and <em>repack --cruft --cruft-expiration 2.weeks.ago</em> if using
6209         cruft packs via <code>gc.cruftPacks</code> or <code>--cruft</code>).  Override the
6210         grace period with this config variable.  The value "now" may be
6211         used to disable this grace period and always prune unreachable
6212         objects immediately, or "never" may be used to suppress pruning.
6213         This feature helps prevent corruption when <em>git gc</em> runs
6214         concurrently with another process writing to the repository; see
6215         the "NOTES" section of <a href="git-gc.html">git-gc(1)</a>.
6216 </p>
6217 </dd>
6218 <dt class="hdlist1">
6219 gc.worktreePruneExpire
6220 </dt>
6221 <dd>
6222 <p>
6223         When <em>git gc</em> is run, it calls
6224         <em>git worktree prune --expire 3.months.ago</em>.
6225         This config variable can be used to set a different grace
6226         period. The value "now" may be used to disable the grace
6227         period and prune <code>$GIT_DIR/worktrees</code> immediately, or "never"
6228         may be used to suppress pruning.
6229 </p>
6230 </dd>
6231 <dt class="hdlist1">
6232 gc.reflogExpire
6233 </dt>
6234 <dt class="hdlist1">
6235 gc.&lt;pattern&gt;.reflogExpire
6236 </dt>
6237 <dd>
6238 <p>
6239         <em>git reflog expire</em> removes reflog entries older than
6240         this time; defaults to 90 days. The value "now" expires all
6241         entries immediately, and "never" suppresses expiration
6242         altogether. With "&lt;pattern&gt;" (e.g.
6243         "refs/stash") in the middle the setting applies only to
6244         the refs that match the &lt;pattern&gt;.
6245 </p>
6246 </dd>
6247 <dt class="hdlist1">
6248 gc.reflogExpireUnreachable
6249 </dt>
6250 <dt class="hdlist1">
6251 gc.&lt;pattern&gt;.reflogExpireUnreachable
6252 </dt>
6253 <dd>
6254 <p>
6255         <em>git reflog expire</em> removes reflog entries older than
6256         this time and are not reachable from the current tip;
6257         defaults to 30 days. The value "now" expires all entries
6258         immediately, and "never" suppresses expiration altogether.
6259         With "&lt;pattern&gt;" (e.g. "refs/stash")
6260         in the middle, the setting applies only to the refs that
6261         match the &lt;pattern&gt;.
6262 </p>
6263 <div class="paragraph"><p>These types of entries are generally created as a result of using <code>git
6264 commit --amend</code> or <code>git rebase</code> and are the commits prior to the amend
6265 or rebase occurring.  Since these changes are not part of the current
6266 project most users will want to expire them sooner, which is why the
6267 default is more aggressive than <code>gc.reflogExpire</code>.</p></div>
6268 </dd>
6269 <dt class="hdlist1">
6270 gc.recentObjectsHook
6271 </dt>
6272 <dd>
6273 <p>
6274         When considering whether or not to remove an object (either when
6275         generating a cruft pack or storing unreachable objects as
6276         loose), use the shell to execute the specified command(s).
6277         Interpret their output as object IDs which Git will consider as
6278         "recent", regardless of their age. By treating their mtimes as
6279         "now", any objects (and their descendants) mentioned in the
6280         output will be kept regardless of their true age.
6281 </p>
6282 <div class="paragraph"><p>Output must contain exactly one hex object ID per line, and nothing
6283 else. Objects which cannot be found in the repository are ignored.
6284 Multiple hooks are supported, but all must exit successfully, else the
6285 operation (either generating a cruft pack or unpacking unreachable
6286 objects) will be halted.</p></div>
6287 </dd>
6288 <dt class="hdlist1">
6289 gc.repackFilter
6290 </dt>
6291 <dd>
6292 <p>
6293         When repacking, use the specified filter to move certain
6294         objects into a separate packfile.  See the
6295         <code>--filter=&lt;filter-spec&gt;</code> option of <a href="git-repack.html">git-repack(1)</a>.
6296 </p>
6297 </dd>
6298 <dt class="hdlist1">
6299 gc.repackFilterTo
6300 </dt>
6301 <dd>
6302 <p>
6303         When repacking and using a filter, see <code>gc.repackFilter</code>, the
6304         specified location will be used to create the packfile
6305         containing the filtered out objects. <strong>WARNING:</strong> The
6306         specified location should be accessible, using for example the
6307         Git alternates mechanism, otherwise the repo could be
6308         considered corrupt by Git as it migh not be able to access the
6309         objects in that packfile. See the <code>--filter-to=&lt;dir&gt;</code> option
6310         of <a href="git-repack.html">git-repack(1)</a> and the <code>objects/info/alternates</code>
6311         section of <a href="gitrepository-layout.html">gitrepository-layout(5)</a>.
6312 </p>
6313 </dd>
6314 <dt class="hdlist1">
6315 gc.rerereResolved
6316 </dt>
6317 <dd>
6318 <p>
6319         Records of conflicted merge you resolved earlier are
6320         kept for this many days when <em>git rerere gc</em> is run.
6321         You can also use more human-readable "1.month.ago", etc.
6322         The default is 60 days.  See <a href="git-rerere.html">git-rerere(1)</a>.
6323 </p>
6324 </dd>
6325 <dt class="hdlist1">
6326 gc.rerereUnresolved
6327 </dt>
6328 <dd>
6329 <p>
6330         Records of conflicted merge you have not resolved are
6331         kept for this many days when <em>git rerere gc</em> is run.
6332         You can also use more human-readable "1.month.ago", etc.
6333         The default is 15 days.  See <a href="git-rerere.html">git-rerere(1)</a>.
6334 </p>
6335 </dd>
6336 <dt class="hdlist1">
6337 gitcvs.commitMsgAnnotation
6338 </dt>
6339 <dd>
6340 <p>
6341         Append this string to each commit message. Set to empty string
6342         to disable this feature. Defaults to "via git-CVS emulator".
6343 </p>
6344 </dd>
6345 <dt class="hdlist1">
6346 gitcvs.enabled
6347 </dt>
6348 <dd>
6349 <p>
6350         Whether the CVS server interface is enabled for this repository.
6351         See <a href="git-cvsserver.html">git-cvsserver(1)</a>.
6352 </p>
6353 </dd>
6354 <dt class="hdlist1">
6355 gitcvs.logFile
6356 </dt>
6357 <dd>
6358 <p>
6359         Path to a log file where the CVS server interface well&#8230; logs
6360         various stuff. See <a href="git-cvsserver.html">git-cvsserver(1)</a>.
6361 </p>
6362 </dd>
6363 <dt class="hdlist1">
6364 gitcvs.usecrlfattr
6365 </dt>
6366 <dd>
6367 <p>
6368         If true, the server will look up the end-of-line conversion
6369         attributes for files to determine the <code>-k</code> modes to use. If
6370         the attributes force Git to treat a file as text,
6371         the <code>-k</code> mode will be left blank so CVS clients will
6372         treat it as text. If they suppress text conversion, the file
6373         will be set with <em>-kb</em> mode, which suppresses any newline munging
6374         the client might otherwise do. If the attributes do not allow
6375         the file type to be determined, then <code>gitcvs.allBinary</code> is
6376         used. See <a href="gitattributes.html">gitattributes(5)</a>.
6377 </p>
6378 </dd>
6379 <dt class="hdlist1">
6380 gitcvs.allBinary
6381 </dt>
6382 <dd>
6383 <p>
6384         This is used if <code>gitcvs.usecrlfattr</code> does not resolve
6385         the correct <em>-kb</em> mode to use. If true, all
6386         unresolved files are sent to the client in
6387         mode <em>-kb</em>. This causes the client to treat them
6388         as binary files, which suppresses any newline munging it
6389         otherwise might do. Alternatively, if it is set to "guess",
6390         then the contents of the file are examined to decide if
6391         it is binary, similar to <code>core.autocrlf</code>.
6392 </p>
6393 </dd>
6394 <dt class="hdlist1">
6395 gitcvs.dbName
6396 </dt>
6397 <dd>
6398 <p>
6399         Database used by git-cvsserver to cache revision information
6400         derived from the Git repository. The exact meaning depends on the
6401         used database driver, for SQLite (which is the default driver) this
6402         is a filename. Supports variable substitution (see
6403         <a href="git-cvsserver.html">git-cvsserver(1)</a> for details). May not contain semicolons (<code>;</code>).
6404         Default: <em>%Ggitcvs.%m.sqlite</em>
6405 </p>
6406 </dd>
6407 <dt class="hdlist1">
6408 gitcvs.dbDriver
6409 </dt>
6410 <dd>
6411 <p>
6412         Used Perl DBI driver. You can specify any available driver
6413         for this here, but it might not work. git-cvsserver is tested
6414         with <em>DBD::SQLite</em>, reported to work with <em>DBD::Pg</em>, and
6415         reported <strong>not</strong> to work with <em>DBD::mysql</em>. Experimental feature.
6416         May not contain double colons (<code>:</code>). Default: <em>SQLite</em>.
6417         See <a href="git-cvsserver.html">git-cvsserver(1)</a>.
6418 </p>
6419 </dd>
6420 <dt class="hdlist1">
6421 gitcvs.dbUser, gitcvs.dbPass
6422 </dt>
6423 <dd>
6424 <p>
6425         Database user and password. Only useful if setting <code>gitcvs.dbDriver</code>,
6426         since SQLite has no concept of database users and/or passwords.
6427         <em>gitcvs.dbUser</em> supports variable substitution (see
6428         <a href="git-cvsserver.html">git-cvsserver(1)</a> for details).
6429 </p>
6430 </dd>
6431 <dt class="hdlist1">
6432 gitcvs.dbTableNamePrefix
6433 </dt>
6434 <dd>
6435 <p>
6436         Database table name prefix.  Prepended to the names of any
6437         database tables used, allowing a single database to be used
6438         for several repositories.  Supports variable substitution (see
6439         <a href="git-cvsserver.html">git-cvsserver(1)</a> for details).  Any non-alphabetic
6440         characters will be replaced with underscores.
6441 </p>
6442 </dd>
6443 </dl></div>
6444 <div class="paragraph"><p>All gitcvs variables except for <code>gitcvs.usecrlfattr</code> and
6445 <code>gitcvs.allBinary</code> can also be specified as
6446 <em>gitcvs.&lt;access_method&gt;.&lt;varname&gt;</em> (where <em>access_method</em>
6447 is one of "ext" and "pserver") to make them apply only for the given
6448 access method.</p></div>
6449 <div class="dlist"><dl>
6450 <dt class="hdlist1">
6451 gitweb.category
6452 </dt>
6453 <dt class="hdlist1">
6454 gitweb.description
6455 </dt>
6456 <dt class="hdlist1">
6457 gitweb.owner
6458 </dt>
6459 <dt class="hdlist1">
6460 gitweb.url
6461 </dt>
6462 <dd>
6463 <p>
6464         See <a href="gitweb.html">gitweb(1)</a> for description.
6465 </p>
6466 </dd>
6467 <dt class="hdlist1">
6468 gitweb.avatar
6469 </dt>
6470 <dt class="hdlist1">
6471 gitweb.blame
6472 </dt>
6473 <dt class="hdlist1">
6474 gitweb.grep
6475 </dt>
6476 <dt class="hdlist1">
6477 gitweb.highlight
6478 </dt>
6479 <dt class="hdlist1">
6480 gitweb.patches
6481 </dt>
6482 <dt class="hdlist1">
6483 gitweb.pickaxe
6484 </dt>
6485 <dt class="hdlist1">
6486 gitweb.remote_heads
6487 </dt>
6488 <dt class="hdlist1">
6489 gitweb.showSizes
6490 </dt>
6491 <dt class="hdlist1">
6492 gitweb.snapshot
6493 </dt>
6494 <dd>
6495 <p>
6496         See <a href="gitweb.conf.html">gitweb.conf(5)</a> for description.
6497 </p>
6498 </dd>
6499 <dt class="hdlist1">
6500 grep.lineNumber
6501 </dt>
6502 <dd>
6503 <p>
6504         If set to true, enable <code>-n</code> option by default.
6505 </p>
6506 </dd>
6507 <dt class="hdlist1">
6508 grep.column
6509 </dt>
6510 <dd>
6511 <p>
6512         If set to true, enable the <code>--column</code> option by default.
6513 </p>
6514 </dd>
6515 <dt class="hdlist1">
6516 grep.patternType
6517 </dt>
6518 <dd>
6519 <p>
6520         Set the default matching behavior. Using a value of <em>basic</em>, <em>extended</em>,
6521         <em>fixed</em>, or <em>perl</em> will enable the <code>--basic-regexp</code>, <code>--extended-regexp</code>,
6522         <code>--fixed-strings</code>, or <code>--perl-regexp</code> option accordingly, while the
6523         value <em>default</em> will use the <code>grep.extendedRegexp</code> option to choose
6524         between <em>basic</em> and <em>extended</em>.
6525 </p>
6526 </dd>
6527 <dt class="hdlist1">
6528 grep.extendedRegexp
6529 </dt>
6530 <dd>
6531 <p>
6532         If set to true, enable <code>--extended-regexp</code> option by default. This
6533         option is ignored when the <code>grep.patternType</code> option is set to a value
6534         other than <em>default</em>.
6535 </p>
6536 </dd>
6537 <dt class="hdlist1">
6538 grep.threads
6539 </dt>
6540 <dd>
6541 <p>
6542         Number of grep worker threads to use. If unset (or set to 0), Git will
6543         use as many threads as the number of logical cores available.
6544 </p>
6545 </dd>
6546 <dt class="hdlist1">
6547 grep.fullName
6548 </dt>
6549 <dd>
6550 <p>
6551         If set to true, enable <code>--full-name</code> option by default.
6552 </p>
6553 </dd>
6554 <dt class="hdlist1">
6555 grep.fallbackToNoIndex
6556 </dt>
6557 <dd>
6558 <p>
6559         If set to true, fall back to git grep --no-index if git grep
6560         is executed outside of a git repository.  Defaults to false.
6561 </p>
6562 </dd>
6563 <dt class="hdlist1">
6564 gpg.program
6565 </dt>
6566 <dd>
6567 <p>
6568         Use this custom program instead of "<code>gpg</code>" found on <code>$PATH</code> when
6569         making or verifying a PGP signature. The program must support the
6570         same command-line interface as GPG, namely, to verify a detached
6571         signature, "<code>gpg --verify $signature - &lt;$file</code>" is run, and the
6572         program is expected to signal a good signature by exiting with
6573         code 0, and to generate an ASCII-armored detached signature, the
6574         standard input of "<code>gpg -bsau $key</code>" is fed with the contents to be
6575         signed, and the program is expected to send the result to its
6576         standard output.
6577 </p>
6578 </dd>
6579 <dt class="hdlist1">
6580 gpg.format
6581 </dt>
6582 <dd>
6583 <p>
6584         Specifies which key format to use when signing with <code>--gpg-sign</code>.
6585         Default is "openpgp". Other possible values are "x509", "ssh".
6586 </p>
6587 <div class="paragraph"><p>See <a href="gitformat-signature.html">gitformat-signature(5)</a> for the signature format, which differs
6588 based on the selected <code>gpg.format</code>.</p></div>
6589 </dd>
6590 <dt class="hdlist1">
6591 gpg.&lt;format&gt;.program
6592 </dt>
6593 <dd>
6594 <p>
6595         Use this to customize the program used for the signing format you
6596         chose. (see <code>gpg.program</code> and <code>gpg.format</code>) <code>gpg.program</code> can still
6597         be used as a legacy synonym for <code>gpg.openpgp.program</code>. The default
6598         value for <code>gpg.x509.program</code> is "gpgsm" and <code>gpg.ssh.program</code> is "ssh-keygen".
6599 </p>
6600 </dd>
6601 <dt class="hdlist1">
6602 gpg.minTrustLevel
6603 </dt>
6604 <dd>
6605 <p>
6606         Specifies a minimum trust level for signature verification.  If
6607         this option is unset, then signature verification for merge
6608         operations require a key with at least <code>marginal</code> trust.  Other
6609         operations that perform signature verification require a key
6610         with at least <code>undefined</code> trust.  Setting this option overrides
6611         the required trust-level for all operations.  Supported values,
6612         in increasing order of significance:
6613 </p>
6614 <div class="ulist"><ul>
6615 <li>
6616 <p>
6617 <code>undefined</code>
6618 </p>
6619 </li>
6620 <li>
6621 <p>
6622 <code>never</code>
6623 </p>
6624 </li>
6625 <li>
6626 <p>
6627 <code>marginal</code>
6628 </p>
6629 </li>
6630 <li>
6631 <p>
6632 <code>fully</code>
6633 </p>
6634 </li>
6635 <li>
6636 <p>
6637 <code>ultimate</code>
6638 </p>
6639 </li>
6640 </ul></div>
6641 </dd>
6642 <dt class="hdlist1">
6643 gpg.ssh.defaultKeyCommand
6644 </dt>
6645 <dd>
6646 <p>
6647         This command that will be run when user.signingkey is not set and a ssh
6648         signature is requested. On successful exit a valid ssh public key
6649         prefixed with <code>key::</code> is expected in the first line of its output.
6650         This allows for a script doing a dynamic lookup of the correct public
6651         key when it is impractical to statically configure <code>user.signingKey</code>.
6652         For example when keys or SSH Certificates are rotated frequently or
6653         selection of the right key depends on external factors unknown to git.
6654 </p>
6655 </dd>
6656 <dt class="hdlist1">
6657 gpg.ssh.allowedSignersFile
6658 </dt>
6659 <dd>
6660 <p>
6661         A file containing ssh public keys which you are willing to trust.
6662         The file consists of one or more lines of principals followed by an ssh
6663         public key.
6664         e.g.: <code>user1@example.com,user2@example.com ssh-rsa AAAAX1...</code>
6665         See ssh-keygen(1) "ALLOWED SIGNERS" for details.
6666         The principal is only used to identify the key and is available when
6667         verifying a signature.
6668 </p>
6669 <div class="paragraph"><p>SSH has no concept of trust levels like gpg does. To be able to differentiate
6670 between valid signatures and trusted signatures the trust level of a signature
6671 verification is set to <code>fully</code> when the public key is present in the allowedSignersFile.
6672 Otherwise the trust level is <code>undefined</code> and git verify-commit/tag will fail.</p></div>
6673 <div class="paragraph"><p>This file can be set to a location outside of the repository and every developer
6674 maintains their own trust store. A central repository server could generate this
6675 file automatically from ssh keys with push access to verify the code against.
6676 In a corporate setting this file is probably generated at a global location
6677 from automation that already handles developer ssh keys.</p></div>
6678 <div class="paragraph"><p>A repository that only allows signed commits can store the file
6679 in the repository itself using a path relative to the top-level of the working tree.
6680 This way only committers with an already valid key can add or change keys in the keyring.</p></div>
6681 <div class="paragraph"><p>Since OpensSSH 8.8 this file allows specifying a key lifetime using valid-after &amp;
6682 valid-before options. Git will mark signatures as valid if the signing key was
6683 valid at the time of the signature&#8217;s creation. This allows users to change a
6684 signing key without invalidating all previously made signatures.</p></div>
6685 <div class="paragraph"><p>Using a SSH CA key with the cert-authority option
6686 (see ssh-keygen(1) "CERTIFICATES") is also valid.</p></div>
6687 </dd>
6688 <dt class="hdlist1">
6689 gpg.ssh.revocationFile
6690 </dt>
6691 <dd>
6692 <p>
6693         Either a SSH KRL or a list of revoked public keys (without the principal prefix).
6694         See ssh-keygen(1) for details.
6695         If a public key is found in this file then it will always be treated
6696         as having trust level "never" and signatures will show as invalid.
6697 </p>
6698 </dd>
6699 <dt class="hdlist1">
6700 gui.commitMsgWidth
6701 </dt>
6702 <dd>
6703 <p>
6704         Defines how wide the commit message window is in the
6705         <a href="git-gui.html">git-gui(1)</a>. "75" is the default.
6706 </p>
6707 </dd>
6708 <dt class="hdlist1">
6709 gui.diffContext
6710 </dt>
6711 <dd>
6712 <p>
6713         Specifies how many context lines should be used in calls to diff
6714         made by the <a href="git-gui.html">git-gui(1)</a>. The default is "5".
6715 </p>
6716 </dd>
6717 <dt class="hdlist1">
6718 gui.displayUntracked
6719 </dt>
6720 <dd>
6721 <p>
6722         Determines if <a href="git-gui.html">git-gui(1)</a> shows untracked files
6723         in the file list. The default is "true".
6724 </p>
6725 </dd>
6726 <dt class="hdlist1">
6727 gui.encoding
6728 </dt>
6729 <dd>
6730 <p>
6731         Specifies the default character encoding to use for displaying of
6732         file contents in <a href="git-gui.html">git-gui(1)</a> and <a href="gitk.html">gitk(1)</a>.
6733         It can be overridden by setting the <em>encoding</em> attribute
6734         for relevant files (see <a href="gitattributes.html">gitattributes(5)</a>).
6735         If this option is not set, the tools default to the
6736         locale encoding.
6737 </p>
6738 </dd>
6739 <dt class="hdlist1">
6740 gui.matchTrackingBranch
6741 </dt>
6742 <dd>
6743 <p>
6744         Determines if new branches created with <a href="git-gui.html">git-gui(1)</a> should
6745         default to tracking remote branches with matching names or
6746         not. Default: "false".
6747 </p>
6748 </dd>
6749 <dt class="hdlist1">
6750 gui.newBranchTemplate
6751 </dt>
6752 <dd>
6753 <p>
6754         Is used as suggested name when creating new branches using the
6755         <a href="git-gui.html">git-gui(1)</a>.
6756 </p>
6757 </dd>
6758 <dt class="hdlist1">
6759 gui.pruneDuringFetch
6760 </dt>
6761 <dd>
6762 <p>
6763         "true" if <a href="git-gui.html">git-gui(1)</a> should prune remote-tracking branches when
6764         performing a fetch. The default value is "false".
6765 </p>
6766 </dd>
6767 <dt class="hdlist1">
6768 gui.trustmtime
6769 </dt>
6770 <dd>
6771 <p>
6772         Determines if <a href="git-gui.html">git-gui(1)</a> should trust the file modification
6773         timestamp or not. By default the timestamps are not trusted.
6774 </p>
6775 </dd>
6776 <dt class="hdlist1">
6777 gui.spellingDictionary
6778 </dt>
6779 <dd>
6780 <p>
6781         Specifies the dictionary used for spell checking commit messages in
6782         the <a href="git-gui.html">git-gui(1)</a>. When set to "none" spell checking is turned
6783         off.
6784 </p>
6785 </dd>
6786 <dt class="hdlist1">
6787 gui.fastCopyBlame
6788 </dt>
6789 <dd>
6790 <p>
6791         If true, <em>git gui blame</em> uses <code>-C</code> instead of <code>-C -C</code> for original
6792         location detection. It makes blame significantly faster on huge
6793         repositories at the expense of less thorough copy detection.
6794 </p>
6795 </dd>
6796 <dt class="hdlist1">
6797 gui.copyBlameThreshold
6798 </dt>
6799 <dd>
6800 <p>
6801         Specifies the threshold to use in <em>git gui blame</em> original location
6802         detection, measured in alphanumeric characters. See the
6803         <a href="git-blame.html">git-blame(1)</a> manual for more information on copy detection.
6804 </p>
6805 </dd>
6806 <dt class="hdlist1">
6807 gui.blamehistoryctx
6808 </dt>
6809 <dd>
6810 <p>
6811         Specifies the radius of history context in days to show in
6812         <a href="gitk.html">gitk(1)</a> for the selected commit, when the <code>Show History
6813         Context</code> menu item is invoked from <em>git gui blame</em>. If this
6814         variable is set to zero, the whole history is shown.
6815 </p>
6816 </dd>
6817 <dt class="hdlist1">
6818 guitool.&lt;name&gt;.cmd
6819 </dt>
6820 <dd>
6821 <p>
6822         Specifies the shell command line to execute when the corresponding item
6823         of the <a href="git-gui.html">git-gui(1)</a> <code>Tools</code> menu is invoked. This option is
6824         mandatory for every tool. The command is executed from the root of
6825         the working directory, and in the environment it receives the name of
6826         the tool as <code>GIT_GUITOOL</code>, the name of the currently selected file as
6827         <em>FILENAME</em>, and the name of the current branch as <em>CUR_BRANCH</em> (if
6828         the head is detached, <em>CUR_BRANCH</em> is empty).
6829 </p>
6830 </dd>
6831 <dt class="hdlist1">
6832 guitool.&lt;name&gt;.needsFile
6833 </dt>
6834 <dd>
6835 <p>
6836         Run the tool only if a diff is selected in the GUI. It guarantees
6837         that <em>FILENAME</em> is not empty.
6838 </p>
6839 </dd>
6840 <dt class="hdlist1">
6841 guitool.&lt;name&gt;.noConsole
6842 </dt>
6843 <dd>
6844 <p>
6845         Run the command silently, without creating a window to display its
6846         output.
6847 </p>
6848 </dd>
6849 <dt class="hdlist1">
6850 guitool.&lt;name&gt;.noRescan
6851 </dt>
6852 <dd>
6853 <p>
6854         Don&#8217;t rescan the working directory for changes after the tool
6855         finishes execution.
6856 </p>
6857 </dd>
6858 <dt class="hdlist1">
6859 guitool.&lt;name&gt;.confirm
6860 </dt>
6861 <dd>
6862 <p>
6863         Show a confirmation dialog before actually running the tool.
6864 </p>
6865 </dd>
6866 <dt class="hdlist1">
6867 guitool.&lt;name&gt;.argPrompt
6868 </dt>
6869 <dd>
6870 <p>
6871         Request a string argument from the user, and pass it to the tool
6872         through the <code>ARGS</code> environment variable. Since requesting an
6873         argument implies confirmation, the <em>confirm</em> option has no effect
6874         if this is enabled. If the option is set to <em>true</em>, <em>yes</em>, or <em>1</em>,
6875         the dialog uses a built-in generic prompt; otherwise the exact
6876         value of the variable is used.
6877 </p>
6878 </dd>
6879 <dt class="hdlist1">
6880 guitool.&lt;name&gt;.revPrompt
6881 </dt>
6882 <dd>
6883 <p>
6884         Request a single valid revision from the user, and set the
6885         <code>REVISION</code> environment variable. In other aspects this option
6886         is similar to <em>argPrompt</em>, and can be used together with it.
6887 </p>
6888 </dd>
6889 <dt class="hdlist1">
6890 guitool.&lt;name&gt;.revUnmerged
6891 </dt>
6892 <dd>
6893 <p>
6894         Show only unmerged branches in the <em>revPrompt</em> subdialog.
6895         This is useful for tools similar to merge or rebase, but not
6896         for things like checkout or reset.
6897 </p>
6898 </dd>
6899 <dt class="hdlist1">
6900 guitool.&lt;name&gt;.title
6901 </dt>
6902 <dd>
6903 <p>
6904         Specifies the title to use for the prompt dialog. The default
6905         is the tool name.
6906 </p>
6907 </dd>
6908 <dt class="hdlist1">
6909 guitool.&lt;name&gt;.prompt
6910 </dt>
6911 <dd>
6912 <p>
6913         Specifies the general prompt string to display at the top of
6914         the dialog, before subsections for <em>argPrompt</em> and <em>revPrompt</em>.
6915         The default value includes the actual command.
6916 </p>
6917 </dd>
6918 <dt class="hdlist1">
6919 help.browser
6920 </dt>
6921 <dd>
6922 <p>
6923         Specify the browser that will be used to display help in the
6924         <em>web</em> format. See <a href="git-help.html">git-help(1)</a>.
6925 </p>
6926 </dd>
6927 <dt class="hdlist1">
6928 help.format
6929 </dt>
6930 <dd>
6931 <p>
6932         Override the default help format used by <a href="git-help.html">git-help(1)</a>.
6933         Values <em>man</em>, <em>info</em>, <em>web</em> and <em>html</em> are supported. <em>man</em> is
6934         the default. <em>web</em> and <em>html</em> are the same.
6935 </p>
6936 </dd>
6937 <dt class="hdlist1">
6938 help.autoCorrect
6939 </dt>
6940 <dd>
6941 <p>
6942         If git detects typos and can identify exactly one valid command similar
6943         to the error, git will try to suggest the correct command or even
6944         run the suggestion automatically. Possible config values are:
6945 </p>
6946 <div class="ulist"><ul>
6947 <li>
6948 <p>
6949 0 (default): show the suggested command.
6950 </p>
6951 </li>
6952 <li>
6953 <p>
6954 positive number: run the suggested command after specified
6955 deciseconds (0.1 sec).
6956 </p>
6957 </li>
6958 <li>
6959 <p>
6960 "immediate": run the suggested command immediately.
6961 </p>
6962 </li>
6963 <li>
6964 <p>
6965 "prompt": show the suggestion and prompt for confirmation to run
6966 the command.
6967 </p>
6968 </li>
6969 <li>
6970 <p>
6971 "never": don&#8217;t run or show any suggested command.
6972 </p>
6973 </li>
6974 </ul></div>
6975 </dd>
6976 <dt class="hdlist1">
6977 help.htmlPath
6978 </dt>
6979 <dd>
6980 <p>
6981         Specify the path where the HTML documentation resides. File system paths
6982         and URLs are supported. HTML pages will be prefixed with this path when
6983         help is displayed in the <em>web</em> format. This defaults to the documentation
6984         path of your Git installation.
6985 </p>
6986 </dd>
6987 <dt class="hdlist1">
6988 http.proxy
6989 </dt>
6990 <dd>
6991 <p>
6992         Override the HTTP proxy, normally configured using the <em>http_proxy</em>,
6993         <em>https_proxy</em>, and <em>all_proxy</em> environment variables (see <code>curl(1)</code>). In
6994         addition to the syntax understood by curl, it is possible to specify a
6995         proxy string with a user name but no password, in which case git will
6996         attempt to acquire one in the same way it does for other credentials. See
6997         <a href="gitcredentials.html">gitcredentials(7)</a> for more information. The syntax thus is
6998         <em>[protocol://][user[:password]@]proxyhost[:port]</em>. This can be overridden
6999         on a per-remote basis; see remote.&lt;name&gt;.proxy
7000 </p>
7001 </dd>
7002 <dt class="hdlist1">
7003 http.proxyAuthMethod
7004 </dt>
7005 <dd>
7006 <p>
7007         Set the method with which to authenticate against the HTTP proxy. This
7008         only takes effect if the configured proxy string contains a user name part
7009         (i.e. is of the form <em>user@host</em> or <em>user@host:port</em>). This can be
7010         overridden on a per-remote basis; see <code>remote.&lt;name&gt;.proxyAuthMethod</code>.
7011         Both can be overridden by the <code>GIT_HTTP_PROXY_AUTHMETHOD</code> environment
7012         variable.  Possible values are:
7013 </p>
7014 <div class="openblock">
7015 <div class="content">
7016 <div class="ulist"><ul>
7017 <li>
7018 <p>
7019 <code>anyauth</code> - Automatically pick a suitable authentication method. It is
7020   assumed that the proxy answers an unauthenticated request with a 407
7021   status code and one or more Proxy-authenticate headers with supported
7022   authentication methods. This is the default.
7023 </p>
7024 </li>
7025 <li>
7026 <p>
7027 <code>basic</code> - HTTP Basic authentication
7028 </p>
7029 </li>
7030 <li>
7031 <p>
7032 <code>digest</code> - HTTP Digest authentication; this prevents the password from being
7033   transmitted to the proxy in clear text
7034 </p>
7035 </li>
7036 <li>
7037 <p>
7038 <code>negotiate</code> - GSS-Negotiate authentication (compare the --negotiate option
7039   of <code>curl(1)</code>)
7040 </p>
7041 </li>
7042 <li>
7043 <p>
7044 <code>ntlm</code> - NTLM authentication (compare the --ntlm option of <code>curl(1)</code>)
7045 </p>
7046 </li>
7047 </ul></div>
7048 </div></div>
7049 </dd>
7050 <dt class="hdlist1">
7051 http.proxySSLCert
7052 </dt>
7053 <dd>
7054 <p>
7055         The pathname of a file that stores a client certificate to use to authenticate
7056         with an HTTPS proxy. Can be overridden by the <code>GIT_PROXY_SSL_CERT</code> environment
7057         variable.
7058 </p>
7059 </dd>
7060 <dt class="hdlist1">
7061 http.proxySSLKey
7062 </dt>
7063 <dd>
7064 <p>
7065         The pathname of a file that stores a private key to use to authenticate with
7066         an HTTPS proxy. Can be overridden by the <code>GIT_PROXY_SSL_KEY</code> environment
7067         variable.
7068 </p>
7069 </dd>
7070 <dt class="hdlist1">
7071 http.proxySSLCertPasswordProtected
7072 </dt>
7073 <dd>
7074 <p>
7075         Enable Git&#8217;s password prompt for the proxy SSL certificate.  Otherwise OpenSSL
7076         will prompt the user, possibly many times, if the certificate or private key
7077         is encrypted. Can be overridden by the <code>GIT_PROXY_SSL_CERT_PASSWORD_PROTECTED</code>
7078         environment variable.
7079 </p>
7080 </dd>
7081 <dt class="hdlist1">
7082 http.proxySSLCAInfo
7083 </dt>
7084 <dd>
7085 <p>
7086         Pathname to the file containing the certificate bundle that should be used to
7087         verify the proxy with when using an HTTPS proxy. Can be overridden by the
7088         <code>GIT_PROXY_SSL_CAINFO</code> environment variable.
7089 </p>
7090 </dd>
7091 <dt class="hdlist1">
7092 http.emptyAuth
7093 </dt>
7094 <dd>
7095 <p>
7096         Attempt authentication without seeking a username or password.  This
7097         can be used to attempt GSS-Negotiate authentication without specifying
7098         a username in the URL, as libcurl normally requires a username for
7099         authentication.
7100 </p>
7101 </dd>
7102 <dt class="hdlist1">
7103 http.delegation
7104 </dt>
7105 <dd>
7106 <p>
7107         Control GSSAPI credential delegation. The delegation is disabled
7108         by default in libcurl since version 7.21.7. Set parameter to tell
7109         the server what it is allowed to delegate when it comes to user
7110         credentials. Used with GSS/kerberos. Possible values are:
7111 </p>
7112 <div class="openblock">
7113 <div class="content">
7114 <div class="ulist"><ul>
7115 <li>
7116 <p>
7117 <code>none</code> - Don&#8217;t allow any delegation.
7118 </p>
7119 </li>
7120 <li>
7121 <p>
7122 <code>policy</code> - Delegates if and only if the OK-AS-DELEGATE flag is set in the
7123   Kerberos service ticket, which is a matter of realm policy.
7124 </p>
7125 </li>
7126 <li>
7127 <p>
7128 <code>always</code> - Unconditionally allow the server to delegate.
7129 </p>
7130 </li>
7131 </ul></div>
7132 </div></div>
7133 </dd>
7134 <dt class="hdlist1">
7135 http.extraHeader
7136 </dt>
7137 <dd>
7138 <p>
7139         Pass an additional HTTP header when communicating with a server.  If
7140         more than one such entry exists, all of them are added as extra
7141         headers.  To allow overriding the settings inherited from the system
7142         config, an empty value will reset the extra headers to the empty list.
7143 </p>
7144 </dd>
7145 <dt class="hdlist1">
7146 http.cookieFile
7147 </dt>
7148 <dd>
7149 <p>
7150         The pathname of a file containing previously stored cookie lines,
7151         which should be used
7152         in the Git http session, if they match the server. The file format
7153         of the file to read cookies from should be plain HTTP headers or
7154         the Netscape/Mozilla cookie file format (see <code>curl(1)</code>).
7155         NOTE that the file specified with http.cookieFile is used only as
7156         input unless http.saveCookies is set.
7157 </p>
7158 </dd>
7159 <dt class="hdlist1">
7160 http.saveCookies
7161 </dt>
7162 <dd>
7163 <p>
7164         If set, store cookies received during requests to the file specified by
7165         http.cookieFile. Has no effect if http.cookieFile is unset.
7166 </p>
7167 </dd>
7168 <dt class="hdlist1">
7169 http.version
7170 </dt>
7171 <dd>
7172 <p>
7173         Use the specified HTTP protocol version when communicating with a server.
7174         If you want to force the default. The available and default version depend
7175         on libcurl. Currently the possible values of
7176         this option are:
7177 </p>
7178 <div class="ulist"><ul>
7179 <li>
7180 <p>
7181 HTTP/2
7182 </p>
7183 </li>
7184 <li>
7185 <p>
7186 HTTP/1.1
7187 </p>
7188 </li>
7189 </ul></div>
7190 </dd>
7191 <dt class="hdlist1">
7192 http.curloptResolve
7193 </dt>
7194 <dd>
7195 <p>
7196         Hostname resolution information that will be used first by
7197         libcurl when sending HTTP requests.  This information should
7198         be in one of the following formats:
7199 </p>
7200 <div class="ulist"><ul>
7201 <li>
7202 <p>
7203 [+]HOST:PORT:ADDRESS[,ADDRESS]
7204 </p>
7205 </li>
7206 <li>
7207 <p>
7208 -HOST:PORT
7209 </p>
7210 </li>
7211 </ul></div>
7212 <div class="paragraph"><p>The first format redirects all requests to the given <code>HOST:PORT</code>
7213 to the provided <code>ADDRESS</code>(s). The second format clears all
7214 previous config values for that <code>HOST:PORT</code> combination.  To
7215 allow easy overriding of all the settings inherited from the
7216 system config, an empty value will reset all resolution
7217 information to the empty list.</p></div>
7218 </dd>
7219 <dt class="hdlist1">
7220 http.sslVersion
7221 </dt>
7222 <dd>
7223 <p>
7224         The SSL version to use when negotiating an SSL connection, if you
7225         want to force the default.  The available and default version
7226         depend on whether libcurl was built against NSS or OpenSSL and the
7227         particular configuration of the crypto library in use. Internally
7228         this sets the <em>CURLOPT_SSL_VERSION</em> option; see the libcurl
7229         documentation for more details on the format of this option and
7230         for the ssl version supported. Currently the possible values of
7231         this option are:
7232 </p>
7233 <div class="ulist"><ul>
7234 <li>
7235 <p>
7236 sslv2
7237 </p>
7238 </li>
7239 <li>
7240 <p>
7241 sslv3
7242 </p>
7243 </li>
7244 <li>
7245 <p>
7246 tlsv1
7247 </p>
7248 </li>
7249 <li>
7250 <p>
7251 tlsv1.0
7252 </p>
7253 </li>
7254 <li>
7255 <p>
7256 tlsv1.1
7257 </p>
7258 </li>
7259 <li>
7260 <p>
7261 tlsv1.2
7262 </p>
7263 </li>
7264 <li>
7265 <p>
7266 tlsv1.3
7267 </p>
7268 </li>
7269 </ul></div>
7270 <div class="paragraph"><p>Can be overridden by the <code>GIT_SSL_VERSION</code> environment variable.
7271 To force git to use libcurl&#8217;s default ssl version and ignore any
7272 explicit http.sslversion option, set <code>GIT_SSL_VERSION</code> to the
7273 empty string.</p></div>
7274 </dd>
7275 <dt class="hdlist1">
7276 http.sslCipherList
7277 </dt>
7278 <dd>
7279 <p>
7280   A list of SSL ciphers to use when negotiating an SSL connection.
7281   The available ciphers depend on whether libcurl was built against
7282   NSS or OpenSSL and the particular configuration of the crypto
7283   library in use.  Internally this sets the <em>CURLOPT_SSL_CIPHER_LIST</em>
7284   option; see the libcurl documentation for more details on the format
7285   of this list.
7286 </p>
7287 <div class="paragraph"><p>Can be overridden by the <code>GIT_SSL_CIPHER_LIST</code> environment variable.
7288 To force git to use libcurl&#8217;s default cipher list and ignore any
7289 explicit http.sslCipherList option, set <code>GIT_SSL_CIPHER_LIST</code> to the
7290 empty string.</p></div>
7291 </dd>
7292 <dt class="hdlist1">
7293 http.sslVerify
7294 </dt>
7295 <dd>
7296 <p>
7297         Whether to verify the SSL certificate when fetching or pushing
7298         over HTTPS. Defaults to true. Can be overridden by the
7299         <code>GIT_SSL_NO_VERIFY</code> environment variable.
7300 </p>
7301 </dd>
7302 <dt class="hdlist1">
7303 http.sslCert
7304 </dt>
7305 <dd>
7306 <p>
7307         File containing the SSL certificate when fetching or pushing
7308         over HTTPS. Can be overridden by the <code>GIT_SSL_CERT</code> environment
7309         variable.
7310 </p>
7311 </dd>
7312 <dt class="hdlist1">
7313 http.sslKey
7314 </dt>
7315 <dd>
7316 <p>
7317         File containing the SSL private key when fetching or pushing
7318         over HTTPS. Can be overridden by the <code>GIT_SSL_KEY</code> environment
7319         variable.
7320 </p>
7321 </dd>
7322 <dt class="hdlist1">
7323 http.sslCertPasswordProtected
7324 </dt>
7325 <dd>
7326 <p>
7327         Enable Git&#8217;s password prompt for the SSL certificate.  Otherwise
7328         OpenSSL will prompt the user, possibly many times, if the
7329         certificate or private key is encrypted.  Can be overridden by the
7330         <code>GIT_SSL_CERT_PASSWORD_PROTECTED</code> environment variable.
7331 </p>
7332 </dd>
7333 <dt class="hdlist1">
7334 http.sslCAInfo
7335 </dt>
7336 <dd>
7337 <p>
7338         File containing the certificates to verify the peer with when
7339         fetching or pushing over HTTPS. Can be overridden by the
7340         <code>GIT_SSL_CAINFO</code> environment variable.
7341 </p>
7342 </dd>
7343 <dt class="hdlist1">
7344 http.sslCAPath
7345 </dt>
7346 <dd>
7347 <p>
7348         Path containing files with the CA certificates to verify the peer
7349         with when fetching or pushing over HTTPS. Can be overridden
7350         by the <code>GIT_SSL_CAPATH</code> environment variable.
7351 </p>
7352 </dd>
7353 <dt class="hdlist1">
7354 http.sslBackend
7355 </dt>
7356 <dd>
7357 <p>
7358         Name of the SSL backend to use (e.g. "openssl" or "schannel").
7359         This option is ignored if cURL lacks support for choosing the SSL
7360         backend at runtime.
7361 </p>
7362 </dd>
7363 <dt class="hdlist1">
7364 http.schannelCheckRevoke
7365 </dt>
7366 <dd>
7367 <p>
7368         Used to enforce or disable certificate revocation checks in cURL
7369         when http.sslBackend is set to "schannel". Defaults to <code>true</code> if
7370         unset. Only necessary to disable this if Git consistently errors
7371         and the message is about checking the revocation status of a
7372         certificate. This option is ignored if cURL lacks support for
7373         setting the relevant SSL option at runtime.
7374 </p>
7375 </dd>
7376 <dt class="hdlist1">
7377 http.schannelUseSSLCAInfo
7378 </dt>
7379 <dd>
7380 <p>
7381         As of cURL v7.60.0, the Secure Channel backend can use the
7382         certificate bundle provided via <code>http.sslCAInfo</code>, but that would
7383         override the Windows Certificate Store. Since this is not desirable
7384         by default, Git will tell cURL not to use that bundle by default
7385         when the <code>schannel</code> backend was configured via <code>http.sslBackend</code>,
7386         unless <code>http.schannelUseSSLCAInfo</code> overrides this behavior.
7387 </p>
7388 </dd>
7389 <dt class="hdlist1">
7390 http.pinnedPubkey
7391 </dt>
7392 <dd>
7393 <p>
7394         Public key of the https service. It may either be the filename of
7395         a PEM or DER encoded public key file or a string starting with
7396         <em>sha256//</em> followed by the base64 encoded sha256 hash of the
7397         public key. See also libcurl <em>CURLOPT_PINNEDPUBLICKEY</em>. git will
7398         exit with an error if this option is set but not supported by
7399         cURL.
7400 </p>
7401 </dd>
7402 <dt class="hdlist1">
7403 http.sslTry
7404 </dt>
7405 <dd>
7406 <p>
7407         Attempt to use AUTH SSL/TLS and encrypted data transfers
7408         when connecting via regular FTP protocol. This might be needed
7409         if the FTP server requires it for security reasons or you wish
7410         to connect securely whenever remote FTP server supports it.
7411         Default is false since it might trigger certificate verification
7412         errors on misconfigured servers.
7413 </p>
7414 </dd>
7415 <dt class="hdlist1">
7416 http.maxRequests
7417 </dt>
7418 <dd>
7419 <p>
7420         How many HTTP requests to launch in parallel. Can be overridden
7421         by the <code>GIT_HTTP_MAX_REQUESTS</code> environment variable. Default is 5.
7422 </p>
7423 </dd>
7424 <dt class="hdlist1">
7425 http.minSessions
7426 </dt>
7427 <dd>
7428 <p>
7429         The number of curl sessions (counted across slots) to be kept across
7430         requests. They will not be ended with curl_easy_cleanup() until
7431         http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
7432         value will be capped at 1. Defaults to 1.
7433 </p>
7434 </dd>
7435 <dt class="hdlist1">
7436 http.postBuffer
7437 </dt>
7438 <dd>
7439 <p>
7440         Maximum size in bytes of the buffer used by smart HTTP
7441         transports when POSTing data to the remote system.
7442         For requests larger than this buffer size, HTTP/1.1 and
7443         Transfer-Encoding: chunked is used to avoid creating a
7444         massive pack file locally.  Default is 1 MiB, which is
7445         sufficient for most requests.
7446 </p>
7447 <div class="paragraph"><p>Note that raising this limit is only effective for disabling chunked
7448 transfer encoding and therefore should be used only where the remote
7449 server or a proxy only supports HTTP/1.0 or is noncompliant with the
7450 HTTP standard.  Raising this is not, in general, an effective solution
7451 for most push problems, but can increase memory consumption
7452 significantly since the entire buffer is allocated even for small
7453 pushes.</p></div>
7454 </dd>
7455 <dt class="hdlist1">
7456 http.lowSpeedLimit, http.lowSpeedTime
7457 </dt>
7458 <dd>
7459 <p>
7460         If the HTTP transfer speed, in bytes per second, is less than
7461         <em>http.lowSpeedLimit</em> for longer than <em>http.lowSpeedTime</em> seconds,
7462         the transfer is aborted.
7463         Can be overridden by the <code>GIT_HTTP_LOW_SPEED_LIMIT</code> and
7464         <code>GIT_HTTP_LOW_SPEED_TIME</code> environment variables.
7465 </p>
7466 </dd>
7467 <dt class="hdlist1">
7468 http.noEPSV
7469 </dt>
7470 <dd>
7471 <p>
7472         A boolean which disables using of EPSV ftp command by curl.
7473         This can helpful with some "poor" ftp servers which don&#8217;t
7474         support EPSV mode. Can be overridden by the <code>GIT_CURL_FTP_NO_EPSV</code>
7475         environment variable. Default is false (curl will use EPSV).
7476 </p>
7477 </dd>
7478 <dt class="hdlist1">
7479 http.userAgent
7480 </dt>
7481 <dd>
7482 <p>
7483         The HTTP USER_AGENT string presented to an HTTP server.  The default
7484         value represents the version of the client Git such as git/1.7.1.
7485         This option allows you to override this value to a more common value
7486         such as Mozilla/4.0.  This may be necessary, for instance, if
7487         connecting through a firewall that restricts HTTP connections to a set
7488         of common USER_AGENT strings (but not including those like git/1.7.1).
7489         Can be overridden by the <code>GIT_HTTP_USER_AGENT</code> environment variable.
7490 </p>
7491 </dd>
7492 <dt class="hdlist1">
7493 http.followRedirects
7494 </dt>
7495 <dd>
7496 <p>
7497         Whether git should follow HTTP redirects. If set to <code>true</code>, git
7498         will transparently follow any redirect issued by a server it
7499         encounters. If set to <code>false</code>, git will treat all redirects as
7500         errors. If set to <code>initial</code>, git will follow redirects only for
7501         the initial request to a remote, but not for subsequent
7502         follow-up HTTP requests. Since git uses the redirected URL as
7503         the base for the follow-up requests, this is generally
7504         sufficient. The default is <code>initial</code>.
7505 </p>
7506 </dd>
7507 <dt class="hdlist1">
7508 http.&lt;url&gt;.*
7509 </dt>
7510 <dd>
7511 <p>
7512         Any of the http.* options above can be applied selectively to some URLs.
7513         For a config key to match a URL, each element of the config key is
7514         compared to that of the URL, in the following order:
7515 </p>
7516 <div class="openblock">
7517 <div class="content">
7518 <div class="olist arabic"><ol class="arabic">
7519 <li>
7520 <p>
7521 Scheme (e.g., <code>https</code> in <code>https://example.com/</code>). This field
7522   must match exactly between the config key and the URL.
7523 </p>
7524 </li>
7525 <li>
7526 <p>
7527 Host/domain name (e.g., <code>example.com</code> in <code>https://example.com/</code>).
7528   This field must match between the config key and the URL. It is
7529   possible to specify a <code>*</code> as part of the host name to match all subdomains
7530   at this level. <code>https://*.example.com/</code> for example would match
7531   <code>https://foo.example.com/</code>, but not <code>https://foo.bar.example.com/</code>.
7532 </p>
7533 </li>
7534 <li>
7535 <p>
7536 Port number (e.g., <code>8080</code> in <code>http://example.com:8080/</code>).
7537   This field must match exactly between the config key and the URL.
7538   Omitted port numbers are automatically converted to the correct
7539   default for the scheme before matching.
7540 </p>
7541 </li>
7542 <li>
7543 <p>
7544 Path (e.g., <code>repo.git</code> in <code>https://example.com/repo.git</code>). The
7545   path field of the config key must match the path field of the URL
7546   either exactly or as a prefix of slash-delimited path elements.  This means
7547   a config key with path <code>foo/</code> matches URL path <code>foo/bar</code>.  A prefix can only
7548   match on a slash (<code>/</code>) boundary.  Longer matches take precedence (so a config
7549   key with path <code>foo/bar</code> is a better match to URL path <code>foo/bar</code> than a config
7550   key with just path <code>foo/</code>).
7551 </p>
7552 </li>
7553 <li>
7554 <p>
7555 User name (e.g., <code>user</code> in <code>https://user@example.com/repo.git</code>). If
7556   the config key has a user name it must match the user name in the
7557   URL exactly. If the config key does not have a user name, that
7558   config key will match a URL with any user name (including none),
7559   but at a lower precedence than a config key with a user name.
7560 </p>
7561 </li>
7562 </ol></div>
7563 </div></div>
7564 <div class="paragraph"><p>The list above is ordered by decreasing precedence; a URL that matches
7565 a config key&#8217;s path is preferred to one that matches its user name. For example,
7566 if the URL is <code>https://user@example.com/foo/bar</code> a config key match of
7567 <code>https://example.com/foo</code> will be preferred over a config key match of
7568 <code>https://user@example.com</code>.</p></div>
7569 <div class="paragraph"><p>All URLs are normalized before attempting any matching (the password part,
7570 if embedded in the URL, is always ignored for matching purposes) so that
7571 equivalent URLs that are simply spelled differently will match properly.
7572 Environment variable settings always override any matches.  The URLs that are
7573 matched against are those given directly to Git commands.  This means any URLs
7574 visited as a result of a redirection do not participate in matching.</p></div>
7575 </dd>
7576 <dt class="hdlist1">
7577 i18n.commitEncoding
7578 </dt>
7579 <dd>
7580 <p>
7581         Character encoding the commit messages are stored in; Git itself
7582         does not care per se, but this information is necessary e.g. when
7583         importing commits from emails or in the gitk graphical history
7584         browser (and possibly at other places in the future or in other
7585         porcelains). See e.g. <a href="git-mailinfo.html">git-mailinfo(1)</a>. Defaults to <em>utf-8</em>.
7586 </p>
7587 </dd>
7588 <dt class="hdlist1">
7589 i18n.logOutputEncoding
7590 </dt>
7591 <dd>
7592 <p>
7593         Character encoding the commit messages are converted to when
7594         running <em>git log</em> and friends.
7595 </p>
7596 </dd>
7597 <dt class="hdlist1">
7598 imap.folder
7599 </dt>
7600 <dd>
7601 <p>
7602         The folder to drop the mails into, which is typically the Drafts
7603         folder. For example: "INBOX.Drafts", "INBOX/Drafts" or
7604         "[Gmail]/Drafts". Required.
7605 </p>
7606 </dd>
7607 <dt class="hdlist1">
7608 imap.tunnel
7609 </dt>
7610 <dd>
7611 <p>
7612         Command used to setup a tunnel to the IMAP server through which
7613         commands will be piped instead of using a direct network connection
7614         to the server. Required when imap.host is not set.
7615 </p>
7616 </dd>
7617 <dt class="hdlist1">
7618 imap.host
7619 </dt>
7620 <dd>
7621 <p>
7622         A URL identifying the server. Use an <code>imap://</code> prefix for non-secure
7623         connections and an <code>imaps://</code> prefix for secure connections.
7624         Ignored when imap.tunnel is set, but required otherwise.
7625 </p>
7626 </dd>
7627 <dt class="hdlist1">
7628 imap.user
7629 </dt>
7630 <dd>
7631 <p>
7632         The username to use when logging in to the server.
7633 </p>
7634 </dd>
7635 <dt class="hdlist1">
7636 imap.pass
7637 </dt>
7638 <dd>
7639 <p>
7640         The password to use when logging in to the server.
7641 </p>
7642 </dd>
7643 <dt class="hdlist1">
7644 imap.port
7645 </dt>
7646 <dd>
7647 <p>
7648         An integer port number to connect to on the server.
7649         Defaults to 143 for imap:// hosts and 993 for imaps:// hosts.
7650         Ignored when imap.tunnel is set.
7651 </p>
7652 </dd>
7653 <dt class="hdlist1">
7654 imap.sslverify
7655 </dt>
7656 <dd>
7657 <p>
7658         A boolean to enable/disable verification of the server certificate
7659         used by the SSL/TLS connection. Default is <code>true</code>. Ignored when
7660         imap.tunnel is set.
7661 </p>
7662 </dd>
7663 <dt class="hdlist1">
7664 imap.preformattedHTML
7665 </dt>
7666 <dd>
7667 <p>
7668         A boolean to enable/disable the use of html encoding when sending
7669         a patch.  An html encoded patch will be bracketed with &lt;pre&gt;
7670         and have a content type of text/html.  Ironically, enabling this
7671         option causes Thunderbird to send the patch as a plain/text,
7672         format=fixed email.  Default is <code>false</code>.
7673 </p>
7674 </dd>
7675 <dt class="hdlist1">
7676 imap.authMethod
7677 </dt>
7678 <dd>
7679 <p>
7680         Specify authenticate method for authentication with IMAP server.
7681         If Git was built with the NO_CURL option, or if your curl version is older
7682         than 7.34.0, or if you&#8217;re running git-imap-send with the <code>--no-curl</code>
7683         option, the only supported method is <em>CRAM-MD5</em>. If this is not set
7684         then <em>git imap-send</em> uses the basic IMAP plaintext LOGIN command.
7685 </p>
7686 </dd>
7687 <dt class="hdlist1">
7688 include.path
7689 </dt>
7690 <dt class="hdlist1">
7691 includeIf.&lt;condition&gt;.path
7692 </dt>
7693 <dd>
7694 <p>
7695         Special variables to include other configuration files. See
7696         the "CONFIGURATION FILE" section in the main
7697         <a href="git-config.html">git-config(1)</a> documentation,
7698         specifically the "Includes" and "Conditional Includes" subsections.
7699 </p>
7700 </dd>
7701 <dt class="hdlist1">
7702 index.recordEndOfIndexEntries
7703 </dt>
7704 <dd>
7705 <p>
7706         Specifies whether the index file should include an "End Of Index
7707         Entry" section. This reduces index load time on multiprocessor
7708         machines but produces a message "ignoring EOIE extension" when
7709         reading the index using Git versions before 2.20. Defaults to
7710         <em>true</em> if index.threads has been explicitly enabled, <em>false</em>
7711         otherwise.
7712 </p>
7713 </dd>
7714 <dt class="hdlist1">
7715 index.recordOffsetTable
7716 </dt>
7717 <dd>
7718 <p>
7719         Specifies whether the index file should include an "Index Entry
7720         Offset Table" section. This reduces index load time on
7721         multiprocessor machines but produces a message "ignoring IEOT
7722         extension" when reading the index using Git versions before 2.20.
7723         Defaults to <em>true</em> if index.threads has been explicitly enabled,
7724         <em>false</em> otherwise.
7725 </p>
7726 </dd>
7727 <dt class="hdlist1">
7728 index.sparse
7729 </dt>
7730 <dd>
7731 <p>
7732         When enabled, write the index using sparse-directory entries. This
7733         has no effect unless <code>core.sparseCheckout</code> and
7734         <code>core.sparseCheckoutCone</code> are both enabled. Defaults to <em>false</em>.
7735 </p>
7736 </dd>
7737 <dt class="hdlist1">
7738 index.threads
7739 </dt>
7740 <dd>
7741 <p>
7742         Specifies the number of threads to spawn when loading the index.
7743         This is meant to reduce index load time on multiprocessor machines.
7744         Specifying 0 or <em>true</em> will cause Git to auto-detect the number of
7745         CPU&#8217;s and set the number of threads accordingly. Specifying 1 or
7746         <em>false</em> will disable multithreading. Defaults to <em>true</em>.
7747 </p>
7748 </dd>
7749 <dt class="hdlist1">
7750 index.version
7751 </dt>
7752 <dd>
7753 <p>
7754         Specify the version with which new index files should be
7755         initialized.  This does not affect existing repositories.
7756         If <code>feature.manyFiles</code> is enabled, then the default is 4.
7757 </p>
7758 </dd>
7759 <dt class="hdlist1">
7760 index.skipHash
7761 </dt>
7762 <dd>
7763 <p>
7764         When enabled, do not compute the trailing hash for the index file.
7765         This accelerates Git commands that manipulate the index, such as
7766         <code>git add</code>, <code>git commit</code>, or <code>git status</code>. Instead of storing the
7767         checksum, write a trailing set of bytes with value zero, indicating
7768         that the computation was skipped.
7769 </p>
7770 <div class="paragraph"><p>If you enable <code>index.skipHash</code>, then Git clients older than 2.13.0 will
7771 refuse to parse the index and Git clients older than 2.40.0 will report an
7772 error during <code>git fsck</code>.</p></div>
7773 </dd>
7774 <dt class="hdlist1">
7775 init.templateDir
7776 </dt>
7777 <dd>
7778 <p>
7779         Specify the directory from which templates will be copied.
7780         (See the "TEMPLATE DIRECTORY" section of <a href="git-init.html">git-init(1)</a>.)
7781 </p>
7782 </dd>
7783 <dt class="hdlist1">
7784 init.defaultBranch
7785 </dt>
7786 <dd>
7787 <p>
7788         Allows overriding the default branch name e.g. when initializing
7789         a new repository.
7790 </p>
7791 </dd>
7792 <dt class="hdlist1">
7793 instaweb.browser
7794 </dt>
7795 <dd>
7796 <p>
7797         Specify the program that will be used to browse your working
7798         repository in gitweb. See <a href="git-instaweb.html">git-instaweb(1)</a>.
7799 </p>
7800 </dd>
7801 <dt class="hdlist1">
7802 instaweb.httpd
7803 </dt>
7804 <dd>
7805 <p>
7806         The HTTP daemon command-line to start gitweb on your working
7807         repository. See <a href="git-instaweb.html">git-instaweb(1)</a>.
7808 </p>
7809 </dd>
7810 <dt class="hdlist1">
7811 instaweb.local
7812 </dt>
7813 <dd>
7814 <p>
7815         If true the web server started by <a href="git-instaweb.html">git-instaweb(1)</a> will
7816         be bound to the local IP (127.0.0.1).
7817 </p>
7818 </dd>
7819 <dt class="hdlist1">
7820 instaweb.modulePath
7821 </dt>
7822 <dd>
7823 <p>
7824         The default module path for <a href="git-instaweb.html">git-instaweb(1)</a> to use
7825         instead of /usr/lib/apache2/modules.  Only used if httpd
7826         is Apache.
7827 </p>
7828 </dd>
7829 <dt class="hdlist1">
7830 instaweb.port
7831 </dt>
7832 <dd>
7833 <p>
7834         The port number to bind the gitweb httpd to. See
7835         <a href="git-instaweb.html">git-instaweb(1)</a>.
7836 </p>
7837 </dd>
7838 <dt class="hdlist1">
7839 interactive.singleKey
7840 </dt>
7841 <dd>
7842 <p>
7843         In interactive commands, allow the user to provide one-letter
7844         input with a single key (i.e., without hitting enter).
7845         Currently this is used by the <code>--patch</code> mode of
7846         <a href="git-add.html">git-add(1)</a>, <a href="git-checkout.html">git-checkout(1)</a>,
7847         <a href="git-restore.html">git-restore(1)</a>, <a href="git-commit.html">git-commit(1)</a>,
7848         <a href="git-reset.html">git-reset(1)</a>, and <a href="git-stash.html">git-stash(1)</a>. Note that this
7849         setting is silently ignored if portable keystroke input
7850         is not available; requires the Perl module Term::ReadKey.
7851 </p>
7852 </dd>
7853 <dt class="hdlist1">
7854 interactive.diffFilter
7855 </dt>
7856 <dd>
7857 <p>
7858         When an interactive command (such as <code>git add --patch</code>) shows
7859         a colorized diff, git will pipe the diff through the shell
7860         command defined by this configuration variable. The command may
7861         mark up the diff further for human consumption, provided that it
7862         retains a one-to-one correspondence with the lines in the
7863         original diff. Defaults to disabled (no filtering).
7864 </p>
7865 </dd>
7866 <dt class="hdlist1">
7867 log.abbrevCommit
7868 </dt>
7869 <dd>
7870 <p>
7871         If true, makes <a href="git-log.html">git-log(1)</a>, <a href="git-show.html">git-show(1)</a>, and
7872         <a href="git-whatchanged.html">git-whatchanged(1)</a> assume <code>--abbrev-commit</code>. You may
7873         override this option with <code>--no-abbrev-commit</code>.
7874 </p>
7875 </dd>
7876 <dt class="hdlist1">
7877 log.date
7878 </dt>
7879 <dd>
7880 <p>
7881         Set the default date-time mode for the <em>log</em> command.
7882         Setting a value for log.date is similar to using <em>git log</em>'s
7883         <code>--date</code> option.  See <a href="git-log.html">git-log(1)</a> for details.
7884 </p>
7885 <div class="paragraph"><p>If the format is set to "auto:foo" and the pager is in use, format
7886 "foo" will be the used for the date format. Otherwise "default" will
7887 be used.</p></div>
7888 </dd>
7889 <dt class="hdlist1">
7890 log.decorate
7891 </dt>
7892 <dd>
7893 <p>
7894         Print out the ref names of any commits that are shown by the log
7895         command. If <em>short</em> is specified, the ref name prefixes <em>refs/heads/</em>,
7896         <em>refs/tags/</em> and <em>refs/remotes/</em> will not be printed. If <em>full</em> is
7897         specified, the full ref name (including prefix) will be printed.
7898         If <em>auto</em> is specified, then if the output is going to a terminal,
7899         the ref names are shown as if <em>short</em> were given, otherwise no ref
7900         names are shown. This is the same as the <code>--decorate</code> option
7901         of the <code>git log</code>.
7902 </p>
7903 </dd>
7904 <dt class="hdlist1">
7905 log.initialDecorationSet
7906 </dt>
7907 <dd>
7908 <p>
7909         By default, <code>git log</code> only shows decorations for certain known ref
7910         namespaces. If <em>all</em> is specified, then show all refs as
7911         decorations.
7912 </p>
7913 </dd>
7914 <dt class="hdlist1">
7915 log.excludeDecoration
7916 </dt>
7917 <dd>
7918 <p>
7919         Exclude the specified patterns from the log decorations. This is
7920         similar to the <code>--decorate-refs-exclude</code> command-line option, but
7921         the config option can be overridden by the <code>--decorate-refs</code>
7922         option.
7923 </p>
7924 </dd>
7925 <dt class="hdlist1">
7926 log.diffMerges
7927 </dt>
7928 <dd>
7929 <p>
7930         Set diff format to be used when <code>--diff-merges=on</code> is
7931         specified, see <code>--diff-merges</code> in <a href="git-log.html">git-log(1)</a> for
7932         details. Defaults to <code>separate</code>.
7933 </p>
7934 </dd>
7935 <dt class="hdlist1">
7936 log.follow
7937 </dt>
7938 <dd>
7939 <p>
7940         If <code>true</code>, <code>git log</code> will act as if the <code>--follow</code> option was used when
7941         a single &lt;path&gt; is given.  This has the same limitations as <code>--follow</code>,
7942         i.e. it cannot be used to follow multiple files and does not work well
7943         on non-linear history.
7944 </p>
7945 </dd>
7946 <dt class="hdlist1">
7947 log.graphColors
7948 </dt>
7949 <dd>
7950 <p>
7951         A list of colors, separated by commas, that can be used to draw
7952         history lines in <code>git log --graph</code>.
7953 </p>
7954 </dd>
7955 <dt class="hdlist1">
7956 log.showRoot
7957 </dt>
7958 <dd>
7959 <p>
7960         If true, the initial commit will be shown as a big creation event.
7961         This is equivalent to a diff against an empty tree.
7962         Tools like <a href="git-log.html">git-log(1)</a> or <a href="git-whatchanged.html">git-whatchanged(1)</a>, which
7963         normally hide the root commit will now show it. True by default.
7964 </p>
7965 </dd>
7966 <dt class="hdlist1">
7967 log.showSignature
7968 </dt>
7969 <dd>
7970 <p>
7971         If true, makes <a href="git-log.html">git-log(1)</a>, <a href="git-show.html">git-show(1)</a>, and
7972         <a href="git-whatchanged.html">git-whatchanged(1)</a> assume <code>--show-signature</code>.
7973 </p>
7974 </dd>
7975 <dt class="hdlist1">
7976 log.mailmap
7977 </dt>
7978 <dd>
7979 <p>
7980         If true, makes <a href="git-log.html">git-log(1)</a>, <a href="git-show.html">git-show(1)</a>, and
7981         <a href="git-whatchanged.html">git-whatchanged(1)</a> assume <code>--use-mailmap</code>, otherwise
7982         assume <code>--no-use-mailmap</code>. True by default.
7983 </p>
7984 </dd>
7985 <dt class="hdlist1">
7986 lsrefs.unborn
7987 </dt>
7988 <dd>
7989 <p>
7990         May be "advertise" (the default), "allow", or "ignore". If "advertise",
7991         the server will respond to the client sending "unborn" (as described in
7992         <a href="gitprotocol-v2.html">gitprotocol-v2(5)</a>) and will advertise support for this feature during the
7993         protocol v2 capability advertisement. "allow" is the same as
7994         "advertise" except that the server will not advertise support for this
7995         feature; this is useful for load-balanced servers that cannot be
7996         updated atomically (for example), since the administrator could
7997         configure "allow", then after a delay, configure "advertise".
7998 </p>
7999 </dd>
8000 <dt class="hdlist1">
8001 mailinfo.scissors
8002 </dt>
8003 <dd>
8004 <p>
8005         If true, makes <a href="git-mailinfo.html">git-mailinfo(1)</a> (and therefore
8006         <a href="git-am.html">git-am(1)</a>) act by default as if the --scissors option
8007         was provided on the command-line. When active, this features
8008         removes everything from the message body before a scissors
8009         line (i.e. consisting mainly of "&gt;8", "8&lt;" and "-").
8010 </p>
8011 </dd>
8012 <dt class="hdlist1">
8013 mailmap.file
8014 </dt>
8015 <dd>
8016 <p>
8017         The location of an augmenting mailmap file. The default
8018         mailmap, located in the root of the repository, is loaded
8019         first, then the mailmap file pointed to by this variable.
8020         The location of the mailmap file may be in a repository
8021         subdirectory, or somewhere outside of the repository itself.
8022         See <a href="git-shortlog.html">git-shortlog(1)</a> and <a href="git-blame.html">git-blame(1)</a>.
8023 </p>
8024 </dd>
8025 <dt class="hdlist1">
8026 mailmap.blob
8027 </dt>
8028 <dd>
8029 <p>
8030         Like <code>mailmap.file</code>, but consider the value as a reference to a
8031         blob in the repository. If both <code>mailmap.file</code> and
8032         <code>mailmap.blob</code> are given, both are parsed, with entries from
8033         <code>mailmap.file</code> taking precedence. In a bare repository, this
8034         defaults to <code>HEAD:.mailmap</code>. In a non-bare repository, it
8035         defaults to empty.
8036 </p>
8037 </dd>
8038 <dt class="hdlist1">
8039 maintenance.auto
8040 </dt>
8041 <dd>
8042 <p>
8043         This boolean config option controls whether some commands run
8044         <code>git maintenance run --auto</code> after doing their normal work. Defaults
8045         to true.
8046 </p>
8047 </dd>
8048 <dt class="hdlist1">
8049 maintenance.strategy
8050 </dt>
8051 <dd>
8052 <p>
8053         This string config option provides a way to specify one of a few
8054         recommended schedules for background maintenance. This only affects
8055         which tasks are run during <code>git maintenance run --schedule=X</code>
8056         commands, provided no <code>--task=&lt;task&gt;</code> arguments are provided.
8057         Further, if a <code>maintenance.&lt;task&gt;.schedule</code> config value is set,
8058         then that value is used instead of the one provided by
8059         <code>maintenance.strategy</code>. The possible strategy strings are:
8060 </p>
8061 <div class="ulist"><ul>
8062 <li>
8063 <p>
8064 <code>none</code>: This default setting implies no task are run at any schedule.
8065 </p>
8066 </li>
8067 <li>
8068 <p>
8069 <code>incremental</code>: This setting optimizes for performing small maintenance
8070   activities that do not delete any data. This does not schedule the <code>gc</code>
8071   task, but runs the <code>prefetch</code> and <code>commit-graph</code> tasks hourly, the
8072   <code>loose-objects</code> and <code>incremental-repack</code> tasks daily, and the <code>pack-refs</code>
8073   task weekly.
8074 </p>
8075 </li>
8076 </ul></div>
8077 </dd>
8078 <dt class="hdlist1">
8079 maintenance.&lt;task&gt;.enabled
8080 </dt>
8081 <dd>
8082 <p>
8083         This boolean config option controls whether the maintenance task
8084         with name <code>&lt;task&gt;</code> is run when no <code>--task</code> option is specified to
8085         <code>git maintenance run</code>. These config values are ignored if a
8086         <code>--task</code> option exists. By default, only <code>maintenance.gc.enabled</code>
8087         is true.
8088 </p>
8089 </dd>
8090 <dt class="hdlist1">
8091 maintenance.&lt;task&gt;.schedule
8092 </dt>
8093 <dd>
8094 <p>
8095         This config option controls whether or not the given <code>&lt;task&gt;</code> runs
8096         during a <code>git maintenance run --schedule=&lt;frequency&gt;</code> command. The
8097         value must be one of "hourly", "daily", or "weekly".
8098 </p>
8099 </dd>
8100 <dt class="hdlist1">
8101 maintenance.commit-graph.auto
8102 </dt>
8103 <dd>
8104 <p>
8105         This integer config option controls how often the <code>commit-graph</code> task
8106         should be run as part of <code>git maintenance run --auto</code>. If zero, then
8107         the <code>commit-graph</code> task will not run with the <code>--auto</code> option. A
8108         negative value will force the task to run every time. Otherwise, a
8109         positive value implies the command should run when the number of
8110         reachable commits that are not in the commit-graph file is at least
8111         the value of <code>maintenance.commit-graph.auto</code>. The default value is
8112         100.
8113 </p>
8114 </dd>
8115 <dt class="hdlist1">
8116 maintenance.loose-objects.auto
8117 </dt>
8118 <dd>
8119 <p>
8120         This integer config option controls how often the <code>loose-objects</code> task
8121         should be run as part of <code>git maintenance run --auto</code>. If zero, then
8122         the <code>loose-objects</code> task will not run with the <code>--auto</code> option. A
8123         negative value will force the task to run every time. Otherwise, a
8124         positive value implies the command should run when the number of
8125         loose objects is at least the value of <code>maintenance.loose-objects.auto</code>.
8126         The default value is 100.
8127 </p>
8128 </dd>
8129 <dt class="hdlist1">
8130 maintenance.incremental-repack.auto
8131 </dt>
8132 <dd>
8133 <p>
8134         This integer config option controls how often the <code>incremental-repack</code>
8135         task should be run as part of <code>git maintenance run --auto</code>. If zero,
8136         then the <code>incremental-repack</code> task will not run with the <code>--auto</code>
8137         option. A negative value will force the task to run every time.
8138         Otherwise, a positive value implies the command should run when the
8139         number of pack-files not in the multi-pack-index is at least the value
8140         of <code>maintenance.incremental-repack.auto</code>. The default value is 10.
8141 </p>
8142 </dd>
8143 <dt class="hdlist1">
8144 man.viewer
8145 </dt>
8146 <dd>
8147 <p>
8148         Specify the programs that may be used to display help in the
8149         <em>man</em> format. See <a href="git-help.html">git-help(1)</a>.
8150 </p>
8151 </dd>
8152 <dt class="hdlist1">
8153 man.&lt;tool&gt;.cmd
8154 </dt>
8155 <dd>
8156 <p>
8157         Specify the command to invoke the specified man viewer. The
8158         specified command is evaluated in shell with the man page
8159         passed as argument. (See <a href="git-help.html">git-help(1)</a>.)
8160 </p>
8161 </dd>
8162 <dt class="hdlist1">
8163 man.&lt;tool&gt;.path
8164 </dt>
8165 <dd>
8166 <p>
8167         Override the path for the given tool that may be used to
8168         display help in the <em>man</em> format. See <a href="git-help.html">git-help(1)</a>.
8169 </p>
8170 </dd>
8171 <dt class="hdlist1">
8172 merge.conflictStyle
8173 </dt>
8174 <dd>
8175 <p>
8176         Specify the style in which conflicted hunks are written out to
8177         working tree files upon merge.  The default is "merge", which
8178         shows a <code>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</code> conflict marker, changes made by one side,
8179         a <code>=======</code> marker, changes made by the other side, and then
8180         a <code>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</code> marker.  An alternate style, "diff3", adds a <code>|||||||</code>
8181         marker and the original text before the <code>=======</code> marker.  The
8182         "merge" style tends to produce smaller conflict regions than diff3,
8183         both because of the exclusion of the original text, and because
8184         when a subset of lines match on the two sides they are just pulled
8185         out of the conflict region.  Another alternate style, "zdiff3", is
8186         similar to diff3 but removes matching lines on the two sides from
8187         the conflict region when those matching lines appear near either
8188         the beginning or end of a conflict region.
8189 </p>
8190 </dd>
8191 <dt class="hdlist1">
8192 merge.defaultToUpstream
8193 </dt>
8194 <dd>
8195 <p>
8196         If merge is called without any commit argument, merge the upstream
8197         branches configured for the current branch by using their last
8198         observed values stored in their remote-tracking branches.
8199         The values of the <code>branch.&lt;current branch&gt;.merge</code> that name the
8200         branches at the remote named by <code>branch.&lt;current branch&gt;.remote</code>
8201         are consulted, and then they are mapped via <code>remote.&lt;remote&gt;.fetch</code>
8202         to their corresponding remote-tracking branches, and the tips of
8203         these tracking branches are merged. Defaults to true.
8204 </p>
8205 </dd>
8206 <dt class="hdlist1">
8207 merge.ff
8208 </dt>
8209 <dd>
8210 <p>
8211         By default, Git does not create an extra merge commit when merging
8212         a commit that is a descendant of the current commit. Instead, the
8213         tip of the current branch is fast-forwarded. When set to <code>false</code>,
8214         this variable tells Git to create an extra merge commit in such
8215         a case (equivalent to giving the <code>--no-ff</code> option from the command
8216         line). When set to <code>only</code>, only such fast-forward merges are
8217         allowed (equivalent to giving the <code>--ff-only</code> option from the
8218         command line).
8219 </p>
8220 </dd>
8221 <dt class="hdlist1">
8222 merge.verifySignatures
8223 </dt>
8224 <dd>
8225 <p>
8226         If true, this is equivalent to the --verify-signatures command
8227         line option. See <a href="git-merge.html">git-merge(1)</a> for details.
8228 </p>
8229 </dd>
8230 <dt class="hdlist1">
8231 merge.branchdesc
8232 </dt>
8233 <dd>
8234 <p>
8235         In addition to branch names, populate the log message with
8236         the branch description text associated with them.  Defaults
8237         to false.
8238 </p>
8239 </dd>
8240 <dt class="hdlist1">
8241 merge.log
8242 </dt>
8243 <dd>
8244 <p>
8245         In addition to branch names, populate the log message with at
8246         most the specified number of one-line descriptions from the
8247         actual commits that are being merged.  Defaults to false, and
8248         true is a synonym for 20.
8249 </p>
8250 </dd>
8251 <dt class="hdlist1">
8252 merge.suppressDest
8253 </dt>
8254 <dd>
8255 <p>
8256         By adding a glob that matches the names of integration
8257         branches to this multi-valued configuration variable, the
8258         default merge message computed for merges into these
8259         integration branches will omit "into &lt;branch name&gt;" from
8260         its title.
8261 </p>
8262 <div class="paragraph"><p>An element with an empty value can be used to clear the list
8263 of globs accumulated from previous configuration entries.
8264 When there is no <code>merge.suppressDest</code> variable defined, the
8265 default value of <code>master</code> is used for backward compatibility.</p></div>
8266 </dd>
8267 <dt class="hdlist1">
8268 merge.renameLimit
8269 </dt>
8270 <dd>
8271 <p>
8272         The number of files to consider in the exhaustive portion of
8273         rename detection during a merge.  If not specified, defaults
8274         to the value of diff.renameLimit.  If neither
8275         merge.renameLimit nor diff.renameLimit are specified,
8276         currently defaults to 7000.  This setting has no effect if
8277         rename detection is turned off.
8278 </p>
8279 </dd>
8280 <dt class="hdlist1">
8281 merge.renames
8282 </dt>
8283 <dd>
8284 <p>
8285         Whether Git detects renames.  If set to "false", rename detection
8286         is disabled. If set to "true", basic rename detection is enabled.
8287         Defaults to the value of diff.renames.
8288 </p>
8289 </dd>
8290 <dt class="hdlist1">
8291 merge.directoryRenames
8292 </dt>
8293 <dd>
8294 <p>
8295         Whether Git detects directory renames, affecting what happens at
8296         merge time to new files added to a directory on one side of
8297         history when that directory was renamed on the other side of
8298         history.  If merge.directoryRenames is set to "false", directory
8299         rename detection is disabled, meaning that such new files will be
8300         left behind in the old directory.  If set to "true", directory
8301         rename detection is enabled, meaning that such new files will be
8302         moved into the new directory.  If set to "conflict", a conflict
8303         will be reported for such paths.  If merge.renames is false,
8304         merge.directoryRenames is ignored and treated as false.  Defaults
8305         to "conflict".
8306 </p>
8307 </dd>
8308 <dt class="hdlist1">
8309 merge.renormalize
8310 </dt>
8311 <dd>
8312 <p>
8313         Tell Git that canonical representation of files in the
8314         repository has changed over time (e.g. earlier commits record
8315         text files with CRLF line endings, but recent ones use LF line
8316         endings).  In such a repository, Git can convert the data
8317         recorded in commits to a canonical form before performing a
8318         merge to reduce unnecessary conflicts.  For more information,
8319         see section "Merging branches with differing checkin/checkout
8320         attributes" in <a href="gitattributes.html">gitattributes(5)</a>.
8321 </p>
8322 </dd>
8323 <dt class="hdlist1">
8324 merge.stat
8325 </dt>
8326 <dd>
8327 <p>
8328         Whether to print the diffstat between ORIG_HEAD and the merge result
8329         at the end of the merge.  True by default.
8330 </p>
8331 </dd>
8332 <dt class="hdlist1">
8333 merge.autoStash
8334 </dt>
8335 <dd>
8336 <p>
8337         When set to true, automatically create a temporary stash entry
8338         before the operation begins, and apply it after the operation
8339         ends.  This means that you can run merge on a dirty worktree.
8340         However, use with care: the final stash application after a
8341         successful merge might result in non-trivial conflicts.
8342         This option can be overridden by the <code>--no-autostash</code> and
8343         <code>--autostash</code> options of <a href="git-merge.html">git-merge(1)</a>.
8344         Defaults to false.
8345 </p>
8346 </dd>
8347 <dt class="hdlist1">
8348 merge.tool
8349 </dt>
8350 <dd>
8351 <p>
8352         Controls which merge tool is used by <a href="git-mergetool.html">git-mergetool(1)</a>.
8353         The list below shows the valid built-in values.
8354         Any other value is treated as a custom merge tool and requires
8355         that a corresponding mergetool.&lt;tool&gt;.cmd variable is defined.
8356 </p>
8357 </dd>
8358 <dt class="hdlist1">
8359 merge.guitool
8360 </dt>
8361 <dd>
8362 <p>
8363         Controls which merge tool is used by <a href="git-mergetool.html">git-mergetool(1)</a> when the
8364         -g/--gui flag is specified. The list below shows the valid built-in values.
8365         Any other value is treated as a custom merge tool and requires that a
8366         corresponding mergetool.&lt;guitool&gt;.cmd variable is defined.
8367 </p>
8368 <div class="dlist"><dl>
8369 <dt class="hdlist1">
8370 <code>araxis</code>
8371 </dt>
8372 <dd>
8373 <p>
8374 Use Araxis Merge (requires a graphical session)
8375 </p>
8376 </dd>
8377 <dt class="hdlist1">
8378 <code>bc</code>
8379 </dt>
8380 <dd>
8381 <p>
8382 Use Beyond Compare (requires a graphical session)
8383 </p>
8384 </dd>
8385 <dt class="hdlist1">
8386 <code>bc3</code>
8387 </dt>
8388 <dd>
8389 <p>
8390 Use Beyond Compare (requires a graphical session)
8391 </p>
8392 </dd>
8393 <dt class="hdlist1">
8394 <code>bc4</code>
8395 </dt>
8396 <dd>
8397 <p>
8398 Use Beyond Compare (requires a graphical session)
8399 </p>
8400 </dd>
8401 <dt class="hdlist1">
8402 <code>codecompare</code>
8403 </dt>
8404 <dd>
8405 <p>
8406 Use Code Compare (requires a graphical session)
8407 </p>
8408 </dd>
8409 <dt class="hdlist1">
8410 <code>deltawalker</code>
8411 </dt>
8412 <dd>
8413 <p>
8414 Use DeltaWalker (requires a graphical session)
8415 </p>
8416 </dd>
8417 <dt class="hdlist1">
8418 <code>diffmerge</code>
8419 </dt>
8420 <dd>
8421 <p>
8422 Use DiffMerge (requires a graphical session)
8423 </p>
8424 </dd>
8425 <dt class="hdlist1">
8426 <code>diffuse</code>
8427 </dt>
8428 <dd>
8429 <p>
8430 Use Diffuse (requires a graphical session)
8431 </p>
8432 </dd>
8433 <dt class="hdlist1">
8434 <code>ecmerge</code>
8435 </dt>
8436 <dd>
8437 <p>
8438 Use ECMerge (requires a graphical session)
8439 </p>
8440 </dd>
8441 <dt class="hdlist1">
8442 <code>emerge</code>
8443 </dt>
8444 <dd>
8445 <p>
8446 Use Emacs' Emerge
8447 </p>
8448 </dd>
8449 <dt class="hdlist1">
8450 <code>examdiff</code>
8451 </dt>
8452 <dd>
8453 <p>
8454 Use ExamDiff Pro (requires a graphical session)
8455 </p>
8456 </dd>
8457 <dt class="hdlist1">
8458 <code>guiffy</code>
8459 </dt>
8460 <dd>
8461 <p>
8462 Use Guiffy&#8217;s Diff Tool (requires a graphical session)
8463 </p>
8464 </dd>
8465 <dt class="hdlist1">
8466 <code>gvimdiff</code>
8467 </dt>
8468 <dd>
8469 <p>
8470 Use gVim (requires a graphical session) with a custom layout (see <code>git help mergetool</code>'s <code>BACKEND SPECIFIC HINTS</code> section)
8471 </p>
8472 </dd>
8473 <dt class="hdlist1">
8474 <code>gvimdiff1</code>
8475 </dt>
8476 <dd>
8477 <p>
8478 Use gVim (requires a graphical session) with a 2 panes layout (LOCAL and REMOTE)
8479 </p>
8480 </dd>
8481 <dt class="hdlist1">
8482 <code>gvimdiff2</code>
8483 </dt>
8484 <dd>
8485 <p>
8486 Use gVim (requires a graphical session) with a 3 panes layout (LOCAL, MERGED and REMOTE)
8487 </p>
8488 </dd>
8489 <dt class="hdlist1">
8490 <code>gvimdiff3</code>
8491 </dt>
8492 <dd>
8493 <p>
8494 Use gVim (requires a graphical session) where only the MERGED file is shown
8495 </p>
8496 </dd>
8497 <dt class="hdlist1">
8498 <code>kdiff3</code>
8499 </dt>
8500 <dd>
8501 <p>
8502 Use KDiff3 (requires a graphical session)
8503 </p>
8504 </dd>
8505 <dt class="hdlist1">
8506 <code>meld</code>
8507 </dt>
8508 <dd>
8509 <p>
8510 Use Meld (requires a graphical session) with optional <code>auto merge</code> (see <code>git help mergetool</code>'s <code>CONFIGURATION</code> section)
8511 </p>
8512 </dd>
8513 <dt class="hdlist1">
8514 <code>nvimdiff</code>
8515 </dt>
8516 <dd>
8517 <p>
8518 Use Neovim with a custom layout (see <code>git help mergetool</code>'s <code>BACKEND SPECIFIC HINTS</code> section)
8519 </p>
8520 </dd>
8521 <dt class="hdlist1">
8522 <code>nvimdiff1</code>
8523 </dt>
8524 <dd>
8525 <p>
8526 Use Neovim with a 2 panes layout (LOCAL and REMOTE)
8527 </p>
8528 </dd>
8529 <dt class="hdlist1">
8530 <code>nvimdiff2</code>
8531 </dt>
8532 <dd>
8533 <p>
8534 Use Neovim with a 3 panes layout (LOCAL, MERGED and REMOTE)
8535 </p>
8536 </dd>
8537 <dt class="hdlist1">
8538 <code>nvimdiff3</code>
8539 </dt>
8540 <dd>
8541 <p>
8542 Use Neovim where only the MERGED file is shown
8543 </p>
8544 </dd>
8545 <dt class="hdlist1">
8546 <code>opendiff</code>
8547 </dt>
8548 <dd>
8549 <p>
8550 Use FileMerge (requires a graphical session)
8551 </p>
8552 </dd>
8553 <dt class="hdlist1">
8554 <code>p4merge</code>
8555 </dt>
8556 <dd>
8557 <p>
8558 Use HelixCore P4Merge (requires a graphical session)
8559 </p>
8560 </dd>
8561 <dt class="hdlist1">
8562 <code>smerge</code>
8563 </dt>
8564 <dd>
8565 <p>
8566 Use Sublime Merge (requires a graphical session)
8567 </p>
8568 </dd>
8569 <dt class="hdlist1">
8570 <code>tkdiff</code>
8571 </dt>
8572 <dd>
8573 <p>
8574 Use TkDiff (requires a graphical session)
8575 </p>
8576 </dd>
8577 <dt class="hdlist1">
8578 <code>tortoisemerge</code>
8579 </dt>
8580 <dd>
8581 <p>
8582 Use TortoiseMerge (requires a graphical session)
8583 </p>
8584 </dd>
8585 <dt class="hdlist1">
8586 <code>vimdiff</code>
8587 </dt>
8588 <dd>
8589 <p>
8590 Use Vim with a custom layout (see <code>git help mergetool</code>'s <code>BACKEND SPECIFIC HINTS</code> section)
8591 </p>
8592 </dd>
8593 <dt class="hdlist1">
8594 <code>vimdiff1</code>
8595 </dt>
8596 <dd>
8597 <p>
8598 Use Vim with a 2 panes layout (LOCAL and REMOTE)
8599 </p>
8600 </dd>
8601 <dt class="hdlist1">
8602 <code>vimdiff2</code>
8603 </dt>
8604 <dd>
8605 <p>
8606 Use Vim with a 3 panes layout (LOCAL, MERGED and REMOTE)
8607 </p>
8608 </dd>
8609 <dt class="hdlist1">
8610 <code>vimdiff3</code>
8611 </dt>
8612 <dd>
8613 <p>
8614 Use Vim where only the MERGED file is shown
8615 </p>
8616 </dd>
8617 <dt class="hdlist1">
8618 <code>winmerge</code>
8619 </dt>
8620 <dd>
8621 <p>
8622 Use WinMerge (requires a graphical session)
8623 </p>
8624 </dd>
8625 <dt class="hdlist1">
8626 <code>xxdiff</code>
8627 </dt>
8628 <dd>
8629 <p>
8630 Use xxdiff (requires a graphical session)
8631 </p>
8632 </dd>
8633 </dl></div>
8634 </dd>
8635 <dt class="hdlist1">
8636 merge.verbosity
8637 </dt>
8638 <dd>
8639 <p>
8640         Controls the amount of output shown by the recursive merge
8641         strategy.  Level 0 outputs nothing except a final error
8642         message if conflicts were detected. Level 1 outputs only
8643         conflicts, 2 outputs conflicts and file changes.  Level 5 and
8644         above outputs debugging information.  The default is level 2.
8645         Can be overridden by the <code>GIT_MERGE_VERBOSITY</code> environment variable.
8646 </p>
8647 </dd>
8648 <dt class="hdlist1">
8649 merge.&lt;driver&gt;.name
8650 </dt>
8651 <dd>
8652 <p>
8653         Defines a human-readable name for a custom low-level
8654         merge driver.  See <a href="gitattributes.html">gitattributes(5)</a> for details.
8655 </p>
8656 </dd>
8657 <dt class="hdlist1">
8658 merge.&lt;driver&gt;.driver
8659 </dt>
8660 <dd>
8661 <p>
8662         Defines the command that implements a custom low-level
8663         merge driver.  See <a href="gitattributes.html">gitattributes(5)</a> for details.
8664 </p>
8665 </dd>
8666 <dt class="hdlist1">
8667 merge.&lt;driver&gt;.recursive
8668 </dt>
8669 <dd>
8670 <p>
8671         Names a low-level merge driver to be used when
8672         performing an internal merge between common ancestors.
8673         See <a href="gitattributes.html">gitattributes(5)</a> for details.
8674 </p>
8675 </dd>
8676 <dt class="hdlist1">
8677 mergetool.&lt;tool&gt;.path
8678 </dt>
8679 <dd>
8680 <p>
8681         Override the path for the given tool.  This is useful in case
8682         your tool is not in the PATH.
8683 </p>
8684 </dd>
8685 <dt class="hdlist1">
8686 mergetool.&lt;tool&gt;.cmd
8687 </dt>
8688 <dd>
8689 <p>
8690         Specify the command to invoke the specified merge tool.  The
8691         specified command is evaluated in shell with the following
8692         variables available: <em>BASE</em> is the name of a temporary file
8693         containing the common base of the files to be merged, if available;
8694         <em>LOCAL</em> is the name of a temporary file containing the contents of
8695         the file on the current branch; <em>REMOTE</em> is the name of a temporary
8696         file containing the contents of the file from the branch being
8697         merged; <em>MERGED</em> contains the name of the file to which the merge
8698         tool should write the results of a successful merge.
8699 </p>
8700 </dd>
8701 <dt class="hdlist1">
8702 mergetool.&lt;tool&gt;.hideResolved
8703 </dt>
8704 <dd>
8705 <p>
8706         Allows the user to override the global <code>mergetool.hideResolved</code> value
8707         for a specific tool. See <code>mergetool.hideResolved</code> for the full
8708         description.
8709 </p>
8710 </dd>
8711 <dt class="hdlist1">
8712 mergetool.&lt;tool&gt;.trustExitCode
8713 </dt>
8714 <dd>
8715 <p>
8716         For a custom merge command, specify whether the exit code of
8717         the merge command can be used to determine whether the merge was
8718         successful.  If this is not set to true then the merge target file
8719         timestamp is checked and the merge assumed to have been successful
8720         if the file has been updated, otherwise the user is prompted to
8721         indicate the success of the merge.
8722 </p>
8723 </dd>
8724 <dt class="hdlist1">
8725 mergetool.meld.hasOutput
8726 </dt>
8727 <dd>
8728 <p>
8729         Older versions of <code>meld</code> do not support the <code>--output</code> option.
8730         Git will attempt to detect whether <code>meld</code> supports <code>--output</code>
8731         by inspecting the output of <code>meld --help</code>.  Configuring
8732         <code>mergetool.meld.hasOutput</code> will make Git skip these checks and
8733         use the configured value instead.  Setting <code>mergetool.meld.hasOutput</code>
8734         to <code>true</code> tells Git to unconditionally use the <code>--output</code> option,
8735         and <code>false</code> avoids using <code>--output</code>.
8736 </p>
8737 </dd>
8738 <dt class="hdlist1">
8739 mergetool.meld.useAutoMerge
8740 </dt>
8741 <dd>
8742 <p>
8743         When the <code>--auto-merge</code> is given, meld will merge all non-conflicting
8744         parts automatically, highlight the conflicting parts and wait for
8745         user decision.  Setting <code>mergetool.meld.useAutoMerge</code> to <code>true</code> tells
8746         Git to unconditionally use the <code>--auto-merge</code> option with <code>meld</code>.
8747         Setting this value to <code>auto</code> makes git detect whether <code>--auto-merge</code>
8748         is supported and will only use <code>--auto-merge</code> when available.  A
8749         value of <code>false</code> avoids using <code>--auto-merge</code> altogether, and is the
8750         default value.
8751 </p>
8752 </dd>
8753 <dt class="hdlist1">
8754 mergetool.vimdiff.layout
8755 </dt>
8756 <dd>
8757 <p>
8758         The vimdiff backend uses this variable to control how its split
8759         windows look like. Applies even if you are using Neovim (<code>nvim</code>) or
8760         gVim (<code>gvim</code>) as the merge tool. See BACKEND SPECIFIC HINTS section
8761         in <a href="git-mergetool.html">git-mergetool(1)</a>.
8762         for details.
8763 </p>
8764 </dd>
8765 <dt class="hdlist1">
8766 mergetool.hideResolved
8767 </dt>
8768 <dd>
8769 <p>
8770         During a merge Git will automatically resolve as many conflicts as
8771         possible and write the <em>MERGED</em> file containing conflict markers around
8772         any conflicts that it cannot resolve; <em>LOCAL</em> and <em>REMOTE</em> normally
8773         represent the versions of the file from before Git&#8217;s conflict
8774         resolution. This flag causes <em>LOCAL</em> and <em>REMOTE</em> to be overwritten so
8775         that only the unresolved conflicts are presented to the merge tool. Can
8776         be configured per-tool via the <code>mergetool.&lt;tool&gt;.hideResolved</code>
8777         configuration variable. Defaults to <code>false</code>.
8778 </p>
8779 </dd>
8780 <dt class="hdlist1">
8781 mergetool.keepBackup
8782 </dt>
8783 <dd>
8784 <p>
8785         After performing a merge, the original file with conflict markers
8786         can be saved as a file with a <code>.orig</code> extension.  If this variable
8787         is set to <code>false</code> then this file is not preserved.  Defaults to
8788         <code>true</code> (i.e. keep the backup files).
8789 </p>
8790 </dd>
8791 <dt class="hdlist1">
8792 mergetool.keepTemporaries
8793 </dt>
8794 <dd>
8795 <p>
8796         When invoking a custom merge tool, Git uses a set of temporary
8797         files to pass to the tool. If the tool returns an error and this
8798         variable is set to <code>true</code>, then these temporary files will be
8799         preserved, otherwise they will be removed after the tool has
8800         exited. Defaults to <code>false</code>.
8801 </p>
8802 </dd>
8803 <dt class="hdlist1">
8804 mergetool.writeToTemp
8805 </dt>
8806 <dd>
8807 <p>
8808         Git writes temporary <em>BASE</em>, <em>LOCAL</em>, and <em>REMOTE</em> versions of
8809         conflicting files in the worktree by default.  Git will attempt
8810         to use a temporary directory for these files when set <code>true</code>.
8811         Defaults to <code>false</code>.
8812 </p>
8813 </dd>
8814 <dt class="hdlist1">
8815 mergetool.prompt
8816 </dt>
8817 <dd>
8818 <p>
8819         Prompt before each invocation of the merge resolution program.
8820 </p>
8821 </dd>
8822 <dt class="hdlist1">
8823 mergetool.guiDefault
8824 </dt>
8825 <dd>
8826 <p>
8827         Set <code>true</code> to use the <code>merge.guitool</code> by default (equivalent to
8828         specifying the <code>--gui</code> argument), or <code>auto</code> to select <code>merge.guitool</code>
8829         or <code>merge.tool</code> depending on the presence of a <code>DISPLAY</code> environment
8830         variable value. The default is <code>false</code>, where the <code>--gui</code> argument
8831         must be provided explicitly for the <code>merge.guitool</code> to be used.
8832 </p>
8833 </dd>
8834 <dt class="hdlist1">
8835 notes.mergeStrategy
8836 </dt>
8837 <dd>
8838 <p>
8839         Which merge strategy to choose by default when resolving notes
8840         conflicts.  Must be one of <code>manual</code>, <code>ours</code>, <code>theirs</code>, <code>union</code>, or
8841         <code>cat_sort_uniq</code>.  Defaults to <code>manual</code>.  See "NOTES MERGE STRATEGIES"
8842         section of <a href="git-notes.html">git-notes(1)</a> for more information on each strategy.
8843 </p>
8844 <div class="paragraph"><p>This setting can be overridden by passing the <code>--strategy</code> option to
8845 <a href="git-notes.html">git-notes(1)</a>.</p></div>
8846 </dd>
8847 <dt class="hdlist1">
8848 notes.&lt;name&gt;.mergeStrategy
8849 </dt>
8850 <dd>
8851 <p>
8852         Which merge strategy to choose when doing a notes merge into
8853         refs/notes/&lt;name&gt;.  This overrides the more general
8854         "notes.mergeStrategy".  See the "NOTES MERGE STRATEGIES" section in
8855         <a href="git-notes.html">git-notes(1)</a> for more information on the available strategies.
8856 </p>
8857 </dd>
8858 <dt class="hdlist1">
8859 notes.displayRef
8860 </dt>
8861 <dd>
8862 <p>
8863         Which ref (or refs, if a glob or specified more than once), in
8864         addition to the default set by <code>core.notesRef</code> or
8865         <code>GIT_NOTES_REF</code>, to read notes from when showing commit
8866         messages with the <em>git log</em> family of commands.
8867 </p>
8868 <div class="paragraph"><p>This setting can be overridden with the <code>GIT_NOTES_DISPLAY_REF</code>
8869 environment variable, which must be a colon separated list of refs or
8870 globs.</p></div>
8871 <div class="paragraph"><p>A warning will be issued for refs that do not exist,
8872 but a glob that does not match any refs is silently ignored.</p></div>
8873 <div class="paragraph"><p>This setting can be disabled by the <code>--no-notes</code> option to the <em>git
8874 log</em> family of commands, or by the <code>--notes=&lt;ref&gt;</code> option accepted by
8875 those commands.</p></div>
8876 <div class="paragraph"><p>The effective value of "core.notesRef" (possibly overridden by
8877 GIT_NOTES_REF) is also implicitly added to the list of refs to be
8878 displayed.</p></div>
8879 </dd>
8880 <dt class="hdlist1">
8881 notes.rewrite.&lt;command&gt;
8882 </dt>
8883 <dd>
8884 <p>
8885         When rewriting commits with &lt;command&gt; (currently <code>amend</code> or
8886         <code>rebase</code>), if this variable is <code>false</code>, git will not copy
8887         notes from the original to the rewritten commit.  Defaults to
8888         <code>true</code>.  See also "<code>notes.rewriteRef</code>" below.
8889 </p>
8890 <div class="paragraph"><p>This setting can be overridden with the <code>GIT_NOTES_REWRITE_REF</code>
8891 environment variable, which must be a colon separated list of refs or
8892 globs.</p></div>
8893 </dd>
8894 <dt class="hdlist1">
8895 notes.rewriteMode
8896 </dt>
8897 <dd>
8898 <p>
8899         When copying notes during a rewrite (see the
8900         "notes.rewrite.&lt;command&gt;" option), determines what to do if
8901         the target commit already has a note.  Must be one of
8902         <code>overwrite</code>, <code>concatenate</code>, <code>cat_sort_uniq</code>, or <code>ignore</code>.
8903         Defaults to <code>concatenate</code>.
8904 </p>
8905 <div class="paragraph"><p>This setting can be overridden with the <code>GIT_NOTES_REWRITE_MODE</code>
8906 environment variable.</p></div>
8907 </dd>
8908 <dt class="hdlist1">
8909 notes.rewriteRef
8910 </dt>
8911 <dd>
8912 <p>
8913         When copying notes during a rewrite, specifies the (fully
8914         qualified) ref whose notes should be copied.  May be a glob,
8915         in which case notes in all matching refs will be copied.  You
8916         may also specify this configuration several times.
8917 </p>
8918 <div class="paragraph"><p>Does not have a default value; you must configure this variable to
8919 enable note rewriting.  Set it to <code>refs/notes/commits</code> to enable
8920 rewriting for the default commit notes.</p></div>
8921 <div class="paragraph"><p>Can be overridden with the <code>GIT_NOTES_REWRITE_REF</code> environment variable.
8922 See <code>notes.rewrite.&lt;command&gt;</code> above for a further description of its format.</p></div>
8923 </dd>
8924 <dt class="hdlist1">
8925 pack.window
8926 </dt>
8927 <dd>
8928 <p>
8929         The size of the window used by <a href="git-pack-objects.html">git-pack-objects(1)</a> when no
8930         window size is given on the command line. Defaults to 10.
8931 </p>
8932 </dd>
8933 <dt class="hdlist1">
8934 pack.depth
8935 </dt>
8936 <dd>
8937 <p>
8938         The maximum delta depth used by <a href="git-pack-objects.html">git-pack-objects(1)</a> when no
8939         maximum depth is given on the command line. Defaults to 50.
8940         Maximum value is 4095.
8941 </p>
8942 </dd>
8943 <dt class="hdlist1">
8944 pack.windowMemory
8945 </dt>
8946 <dd>
8947 <p>
8948         The maximum size of memory that is consumed by each thread
8949         in <a href="git-pack-objects.html">git-pack-objects(1)</a> for pack window memory when
8950         no limit is given on the command line.  The value can be
8951         suffixed with "k", "m", or "g".  When left unconfigured (or
8952         set explicitly to 0), there will be no limit.
8953 </p>
8954 </dd>
8955 <dt class="hdlist1">
8956 pack.compression
8957 </dt>
8958 <dd>
8959 <p>
8960         An integer -1..9, indicating the compression level for objects
8961         in a pack file. -1 is the zlib default. 0 means no
8962         compression, and 1..9 are various speed/size tradeoffs, 9 being
8963         slowest.  If not set,  defaults to core.compression.  If that is
8964         not set,  defaults to -1, the zlib default, which is "a default
8965         compromise between speed and compression (currently equivalent
8966         to level 6)."
8967 </p>
8968 <div class="paragraph"><p>Note that changing the compression level will not automatically recompress
8969 all existing objects. You can force recompression by passing the -F option
8970 to <a href="git-repack.html">git-repack(1)</a>.</p></div>
8971 </dd>
8972 <dt class="hdlist1">
8973 pack.allowPackReuse
8974 </dt>
8975 <dd>
8976 <p>
8977         When true, and when reachability bitmaps are enabled,
8978         pack-objects will try to send parts of the bitmapped packfile
8979         verbatim. This can reduce memory and CPU usage to serve fetches,
8980         but might result in sending a slightly larger pack. Defaults to
8981         true.
8982 </p>
8983 </dd>
8984 <dt class="hdlist1">
8985 pack.island
8986 </dt>
8987 <dd>
8988 <p>
8989         An extended regular expression configuring a set of delta
8990         islands. See "DELTA ISLANDS" in <a href="git-pack-objects.html">git-pack-objects(1)</a>
8991         for details.
8992 </p>
8993 </dd>
8994 <dt class="hdlist1">
8995 pack.islandCore
8996 </dt>
8997 <dd>
8998 <p>
8999         Specify an island name which gets to have its objects be
9000         packed first. This creates a kind of pseudo-pack at the front
9001         of one pack, so that the objects from the specified island are
9002         hopefully faster to copy into any pack that should be served
9003         to a user requesting these objects. In practice this means
9004         that the island specified should likely correspond to what is
9005         the most commonly cloned in the repo. See also "DELTA ISLANDS"
9006         in <a href="git-pack-objects.html">git-pack-objects(1)</a>.
9007 </p>
9008 </dd>
9009 <dt class="hdlist1">
9010 pack.deltaCacheSize
9011 </dt>
9012 <dd>
9013 <p>
9014         The maximum memory in bytes used for caching deltas in
9015         <a href="git-pack-objects.html">git-pack-objects(1)</a> before writing them out to a pack.
9016         This cache is used to speed up the writing object phase by not
9017         having to recompute the final delta result once the best match
9018         for all objects is found.  Repacking large repositories on machines
9019         which are tight with memory might be badly impacted by this though,
9020         especially if this cache pushes the system into swapping.
9021         A value of 0 means no limit. The smallest size of 1 byte may be
9022         used to virtually disable this cache. Defaults to 256 MiB.
9023 </p>
9024 </dd>
9025 <dt class="hdlist1">
9026 pack.deltaCacheLimit
9027 </dt>
9028 <dd>
9029 <p>
9030         The maximum size of a delta, that is cached in
9031         <a href="git-pack-objects.html">git-pack-objects(1)</a>. This cache is used to speed up the
9032         writing object phase by not having to recompute the final delta
9033         result once the best match for all objects is found.
9034         Defaults to 1000. Maximum value is 65535.
9035 </p>
9036 </dd>
9037 <dt class="hdlist1">
9038 pack.threads
9039 </dt>
9040 <dd>
9041 <p>
9042         Specifies the number of threads to spawn when searching for best
9043         delta matches.  This requires that <a href="git-pack-objects.html">git-pack-objects(1)</a>
9044         be compiled with pthreads otherwise this option is ignored with a
9045         warning. This is meant to reduce packing time on multiprocessor
9046         machines. The required amount of memory for the delta search window
9047         is however multiplied by the number of threads.
9048         Specifying 0 will cause Git to auto-detect the number of CPU&#8217;s
9049         and set the number of threads accordingly.
9050 </p>
9051 </dd>
9052 <dt class="hdlist1">
9053 pack.indexVersion
9054 </dt>
9055 <dd>
9056 <p>
9057         Specify the default pack index version.  Valid values are 1 for
9058         legacy pack index used by Git versions prior to 1.5.2, and 2 for
9059         the new pack index with capabilities for packs larger than 4 GB
9060         as well as proper protection against the repacking of corrupted
9061         packs.  Version 2 is the default.  Note that version 2 is enforced
9062         and this config option ignored whenever the corresponding pack is
9063         larger than 2 GB.
9064 </p>
9065 <div class="paragraph"><p>If you have an old Git that does not understand the version 2 <code>*.idx</code> file,
9066 cloning or fetching over a non native protocol (e.g. "http")
9067 that will copy both <code>*.pack</code> file and corresponding <code>*.idx</code> file from the
9068 other side may give you a repository that cannot be accessed with your
9069 older version of Git. If the <code>*.pack</code> file is smaller than 2 GB, however,
9070 you can use <a href="git-index-pack.html">git-index-pack(1)</a> on the *.pack file to regenerate
9071 the <code>*.idx</code> file.</p></div>
9072 </dd>
9073 <dt class="hdlist1">
9074 pack.packSizeLimit
9075 </dt>
9076 <dd>
9077 <p>
9078         The maximum size of a pack.  This setting only affects
9079         packing to a file when repacking, i.e. the git:// protocol
9080         is unaffected.  It can be overridden by the <code>--max-pack-size</code>
9081         option of <a href="git-repack.html">git-repack(1)</a>.  Reaching this limit results
9082         in the creation of multiple packfiles.
9083 </p>
9084 <div class="paragraph"><p>Note that this option is rarely useful, and may result in a larger total
9085 on-disk size (because Git will not store deltas between packs), as well
9086 as worse runtime performance (object lookup within multiple packs is
9087 slower than a single pack, and optimizations like reachability bitmaps
9088 cannot cope with multiple packs).</p></div>
9089 <div class="paragraph"><p>If you need to actively run Git using smaller packfiles (e.g., because your
9090 filesystem does not support large files), this option may help. But if
9091 your goal is to transmit a packfile over a medium that supports limited
9092 sizes (e.g., removable media that cannot store the whole repository),
9093 you are likely better off creating a single large packfile and splitting
9094 it using a generic multi-volume archive tool (e.g., Unix <code>split</code>).</p></div>
9095 <div class="paragraph"><p>The minimum size allowed is limited to 1 MiB. The default is unlimited.
9096 Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
9097 </dd>
9098 <dt class="hdlist1">
9099 pack.useBitmaps
9100 </dt>
9101 <dd>
9102 <p>
9103         When true, git will use pack bitmaps (if available) when packing
9104         to stdout (e.g., during the server side of a fetch). Defaults to
9105         true. You should not generally need to turn this off unless
9106         you are debugging pack bitmaps.
9107 </p>
9108 </dd>
9109 <dt class="hdlist1">
9110 pack.useBitmapBoundaryTraversal
9111 </dt>
9112 <dd>
9113 <p>
9114         When true, Git will use an experimental algorithm for computing
9115         reachability queries with bitmaps. Instead of building up
9116         complete bitmaps for all of the negated tips and then OR-ing
9117         them together, consider negated tips with existing bitmaps as
9118         additive (i.e. OR-ing them into the result if they exist,
9119         ignoring them otherwise), and build up a bitmap at the boundary
9120         instead.
9121 </p>
9122 <div class="paragraph"><p>When using this algorithm, Git may include too many objects as a result
9123 of not opening up trees belonging to certain UNINTERESTING commits. This
9124 inexactness matches the non-bitmap traversal algorithm.</p></div>
9125 <div class="paragraph"><p>In many cases, this can provide a speed-up over the exact algorithm,
9126 particularly when there is poor bitmap coverage of the negated side of
9127 the query.</p></div>
9128 </dd>
9129 <dt class="hdlist1">
9130 pack.useSparse
9131 </dt>
9132 <dd>
9133 <p>
9134         When true, git will default to using the <em>--sparse</em> option in
9135         <em>git pack-objects</em> when the <em>--revs</em> option is present. This
9136         algorithm only walks trees that appear in paths that introduce new
9137         objects. This can have significant performance benefits when
9138         computing a pack to send a small change. However, it is possible
9139         that extra objects are added to the pack-file if the included
9140         commits contain certain types of direct renames. Default is
9141         <code>true</code>.
9142 </p>
9143 </dd>
9144 <dt class="hdlist1">
9145 pack.preferBitmapTips
9146 </dt>
9147 <dd>
9148 <p>
9149         When selecting which commits will receive bitmaps, prefer a
9150         commit at the tip of any reference that is a suffix of any value
9151         of this configuration over any other commits in the "selection
9152         window".
9153 </p>
9154 <div class="paragraph"><p>Note that setting this configuration to <code>refs/foo</code> does not mean that
9155 the commits at the tips of <code>refs/foo/bar</code> and <code>refs/foo/baz</code> will
9156 necessarily be selected. This is because commits are selected for
9157 bitmaps from within a series of windows of variable length.</p></div>
9158 <div class="paragraph"><p>If a commit at the tip of any reference which is a suffix of any value
9159 of this configuration is seen in a window, it is immediately given
9160 preference over any other commit in that window.</p></div>
9161 </dd>
9162 <dt class="hdlist1">
9163 pack.writeBitmaps (deprecated)
9164 </dt>
9165 <dd>
9166 <p>
9167         This is a deprecated synonym for <code>repack.writeBitmaps</code>.
9168 </p>
9169 </dd>
9170 <dt class="hdlist1">
9171 pack.writeBitmapHashCache
9172 </dt>
9173 <dd>
9174 <p>
9175         When true, git will include a "hash cache" section in the bitmap
9176         index (if one is written). This cache can be used to feed git&#8217;s
9177         delta heuristics, potentially leading to better deltas between
9178         bitmapped and non-bitmapped objects (e.g., when serving a fetch
9179         between an older, bitmapped pack and objects that have been
9180         pushed since the last gc). The downside is that it consumes 4
9181         bytes per object of disk space. Defaults to true.
9182 </p>
9183 <div class="paragraph"><p>When writing a multi-pack reachability bitmap, no new namehashes are
9184 computed; instead, any namehashes stored in an existing bitmap are
9185 permuted into their appropriate location when writing a new bitmap.</p></div>
9186 </dd>
9187 <dt class="hdlist1">
9188 pack.writeBitmapLookupTable
9189 </dt>
9190 <dd>
9191 <p>
9192         When true, Git will include a "lookup table" section in the
9193         bitmap index (if one is written). This table is used to defer
9194         loading individual bitmaps as late as possible. This can be
9195         beneficial in repositories that have relatively large bitmap
9196         indexes. Defaults to false.
9197 </p>
9198 </dd>
9199 <dt class="hdlist1">
9200 pack.readReverseIndex
9201 </dt>
9202 <dd>
9203 <p>
9204         When true, git will read any .rev file(s) that may be available
9205         (see: <a href="gitformat-pack.html">gitformat-pack(5)</a>). When false, the reverse index
9206         will be generated from scratch and stored in memory. Defaults to
9207         true.
9208 </p>
9209 </dd>
9210 <dt class="hdlist1">
9211 pack.writeReverseIndex
9212 </dt>
9213 <dd>
9214 <p>
9215         When true, git will write a corresponding .rev file (see:
9216         <a href="gitformat-pack.html">gitformat-pack(5)</a>)
9217         for each new packfile that it writes in all places except for
9218         <a href="git-fast-import.html">git-fast-import(1)</a> and in the bulk checkin mechanism.
9219         Defaults to true.
9220 </p>
9221 </dd>
9222 <dt class="hdlist1">
9223 pager.&lt;cmd&gt;
9224 </dt>
9225 <dd>
9226 <p>
9227         If the value is boolean, turns on or off pagination of the
9228         output of a particular Git subcommand when writing to a tty.
9229         Otherwise, turns on pagination for the subcommand using the
9230         pager specified by the value of <code>pager.&lt;cmd&gt;</code>.  If <code>--paginate</code>
9231         or <code>--no-pager</code> is specified on the command line, it takes
9232         precedence over this option.  To disable pagination for all
9233         commands, set <code>core.pager</code> or <code>GIT_PAGER</code> to <code>cat</code>.
9234 </p>
9235 </dd>
9236 <dt class="hdlist1">
9237 pretty.&lt;name&gt;
9238 </dt>
9239 <dd>
9240 <p>
9241         Alias for a --pretty= format string, as specified in
9242         <a href="git-log.html">git-log(1)</a>. Any aliases defined here can be used just
9243         as the built-in pretty formats could. For example,
9244         running <code>git config pretty.changelog "format:* %H %s"</code>
9245         would cause the invocation <code>git log --pretty=changelog</code>
9246         to be equivalent to running <code>git log "--pretty=format:* %H %s"</code>.
9247         Note that an alias with the same name as a built-in format
9248         will be silently ignored.
9249 </p>
9250 </dd>
9251 <dt class="hdlist1">
9252 protocol.allow
9253 </dt>
9254 <dd>
9255 <p>
9256         If set, provide a user defined default policy for all protocols which
9257         don&#8217;t explicitly have a policy (<code>protocol.&lt;name&gt;.allow</code>).  By default,
9258         if unset, known-safe protocols (http, https, git, ssh) have a
9259         default policy of <code>always</code>, known-dangerous protocols (ext) have a
9260         default policy of <code>never</code>, and all other protocols (including file)
9261         have a default policy of <code>user</code>.  Supported policies:
9262 </p>
9263 <div class="openblock">
9264 <div class="content">
9265 <div class="ulist"><ul>
9266 <li>
9267 <p>
9268 <code>always</code> - protocol is always able to be used.
9269 </p>
9270 </li>
9271 <li>
9272 <p>
9273 <code>never</code> - protocol is never able to be used.
9274 </p>
9275 </li>
9276 <li>
9277 <p>
9278 <code>user</code> - protocol is only able to be used when <code>GIT_PROTOCOL_FROM_USER</code> is
9279   either unset or has a value of 1.  This policy should be used when you want a
9280   protocol to be directly usable by the user but don&#8217;t want it used by commands which
9281   execute clone/fetch/push commands without user input, e.g. recursive
9282   submodule initialization.
9283 </p>
9284 </li>
9285 </ul></div>
9286 </div></div>
9287 </dd>
9288 <dt class="hdlist1">
9289 protocol.&lt;name&gt;.allow
9290 </dt>
9291 <dd>
9292 <p>
9293         Set a policy to be used by protocol <code>&lt;name&gt;</code> with clone/fetch/push
9294         commands. See <code>protocol.allow</code> above for the available policies.
9295 </p>
9296 <div class="paragraph"><p>The protocol names currently used by git are:</p></div>
9297 <div class="openblock">
9298 <div class="content">
9299 <div class="ulist"><ul>
9300 <li>
9301 <p>
9302 <code>file</code>: any local file-based path (including <code>file://</code> URLs,
9303     or local paths)
9304 </p>
9305 </li>
9306 <li>
9307 <p>
9308 <code>git</code>: the anonymous git protocol over a direct TCP
9309     connection (or proxy, if configured)
9310 </p>
9311 </li>
9312 <li>
9313 <p>
9314 <code>ssh</code>: git over ssh (including <code>host:path</code> syntax,
9315     <code>ssh://</code>, etc).
9316 </p>
9317 </li>
9318 <li>
9319 <p>
9320 <code>http</code>: git over http, both "smart http" and "dumb http".
9321     Note that this does <em>not</em> include <code>https</code>; if you want to configure
9322     both, you must do so individually.
9323 </p>
9324 </li>
9325 <li>
9326 <p>
9327 any external helpers are named by their protocol (e.g., use
9328     <code>hg</code> to allow the <code>git-remote-hg</code> helper)
9329 </p>
9330 </li>
9331 </ul></div>
9332 </div></div>
9333 </dd>
9334 <dt class="hdlist1">
9335 protocol.version
9336 </dt>
9337 <dd>
9338 <p>
9339         If set, clients will attempt to communicate with a server
9340         using the specified protocol version.  If the server does
9341         not support it, communication falls back to version 0.
9342         If unset, the default is <code>2</code>.
9343         Supported versions:
9344 </p>
9345 <div class="openblock">
9346 <div class="content">
9347 <div class="ulist"><ul>
9348 <li>
9349 <p>
9350 <code>0</code> - the original wire protocol.
9351 </p>
9352 </li>
9353 <li>
9354 <p>
9355 <code>1</code> - the original wire protocol with the addition of a version string
9356   in the initial response from the server.
9357 </p>
9358 </li>
9359 <li>
9360 <p>
9361 <code>2</code> - Wire protocol version 2, see <a href="gitprotocol-v2.html">gitprotocol-v2(5)</a>.
9362 </p>
9363 </li>
9364 </ul></div>
9365 </div></div>
9366 </dd>
9367 <dt class="hdlist1">
9368 pull.ff
9369 </dt>
9370 <dd>
9371 <p>
9372         By default, Git does not create an extra merge commit when merging
9373         a commit that is a descendant of the current commit. Instead, the
9374         tip of the current branch is fast-forwarded. When set to <code>false</code>,
9375         this variable tells Git to create an extra merge commit in such
9376         a case (equivalent to giving the <code>--no-ff</code> option from the command
9377         line). When set to <code>only</code>, only such fast-forward merges are
9378         allowed (equivalent to giving the <code>--ff-only</code> option from the
9379         command line). This setting overrides <code>merge.ff</code> when pulling.
9380 </p>
9381 </dd>
9382 <dt class="hdlist1">
9383 pull.rebase
9384 </dt>
9385 <dd>
9386 <p>
9387         When true, rebase branches on top of the fetched branch, instead
9388         of merging the default branch from the default remote when "git
9389         pull" is run. See "branch.&lt;name&gt;.rebase" for setting this on a
9390         per-branch basis.
9391 </p>
9392 <div class="paragraph"><p>When <code>merges</code> (or just <em>m</em>), pass the <code>--rebase-merges</code> option to <em>git rebase</em>
9393 so that the local merge commits are included in the rebase (see
9394 <a href="git-rebase.html">git-rebase(1)</a> for details).</p></div>
9395 <div class="paragraph"><p>When the value is <code>interactive</code> (or just <em>i</em>), the rebase is run in interactive
9396 mode.</p></div>
9397 <div class="paragraph"><p><strong>NOTE</strong>: this is a possibly dangerous operation; do <strong>not</strong> use
9398 it unless you understand the implications (see <a href="git-rebase.html">git-rebase(1)</a>
9399 for details).</p></div>
9400 </dd>
9401 <dt class="hdlist1">
9402 pull.octopus
9403 </dt>
9404 <dd>
9405 <p>
9406         The default merge strategy to use when pulling multiple branches
9407         at once.
9408 </p>
9409 </dd>
9410 <dt class="hdlist1">
9411 pull.twohead
9412 </dt>
9413 <dd>
9414 <p>
9415         The default merge strategy to use when pulling a single branch.
9416 </p>
9417 </dd>
9418 <dt class="hdlist1">
9419 push.autoSetupRemote
9420 </dt>
9421 <dd>
9422 <p>
9423         If set to "true" assume <code>--set-upstream</code> on default push when no
9424         upstream tracking exists for the current branch; this option
9425         takes effect with push.default options <em>simple</em>, <em>upstream</em>,
9426         and <em>current</em>. It is useful if by default you want new branches
9427         to be pushed to the default remote (like the behavior of
9428         <em>push.default=current</em>) and you also want the upstream tracking
9429         to be set. Workflows most likely to benefit from this option are
9430         <em>simple</em> central workflows where all branches are expected to
9431         have the same name on the remote.
9432 </p>
9433 </dd>
9434 <dt class="hdlist1">
9435 push.default
9436 </dt>
9437 <dd>
9438 <p>
9439         Defines the action <code>git push</code> should take if no refspec is
9440         given (whether from the command-line, config, or elsewhere).
9441         Different values are well-suited for
9442         specific workflows; for instance, in a purely central workflow
9443         (i.e. the fetch source is equal to the push destination),
9444         <code>upstream</code> is probably what you want.  Possible values are:
9445 </p>
9446 <div class="openblock">
9447 <div class="content">
9448 <div class="ulist"><ul>
9449 <li>
9450 <p>
9451 <code>nothing</code> - do not push anything (error out) unless a refspec is
9452   given. This is primarily meant for people who want to
9453   avoid mistakes by always being explicit.
9454 </p>
9455 </li>
9456 <li>
9457 <p>
9458 <code>current</code> - push the current branch to update a branch with the same
9459   name on the receiving end.  Works in both central and non-central
9460   workflows.
9461 </p>
9462 </li>
9463 <li>
9464 <p>
9465 <code>upstream</code> - push the current branch back to the branch whose
9466   changes are usually integrated into the current branch (which is
9467   called <code>@{upstream}</code>).  This mode only makes sense if you are
9468   pushing to the same repository you would normally pull from
9469   (i.e. central workflow).
9470 </p>
9471 </li>
9472 <li>
9473 <p>
9474 <code>tracking</code> - This is a deprecated synonym for <code>upstream</code>.
9475 </p>
9476 </li>
9477 <li>
9478 <p>
9479 <code>simple</code> - pushes the current branch with the same name on the remote.
9480 </p>
9481 <div class="paragraph"><p>If you are working on a centralized workflow (pushing to the same repository you
9482 pull from, which is typically <code>origin</code>), then you need to configure an upstream
9483 branch with the same name.</p></div>
9484 <div class="paragraph"><p>This mode is the default since Git 2.0, and is the safest option suited for
9485 beginners.</p></div>
9486 </li>
9487 <li>
9488 <p>
9489 <code>matching</code> - push all branches having the same name on both ends.
9490   This makes the repository you are pushing to remember the set of
9491   branches that will be pushed out (e.g. if you always push <em>maint</em>
9492   and <em>master</em> there and no other branches, the repository you push
9493   to will have these two branches, and your local <em>maint</em> and
9494   <em>master</em> will be pushed there).
9495 </p>
9496 <div class="paragraph"><p>To use this mode effectively, you have to make sure <em>all</em> the
9497 branches you would push out are ready to be pushed out before
9498 running <em>git push</em>, as the whole point of this mode is to allow you
9499 to push all of the branches in one go.  If you usually finish work
9500 on only one branch and push out the result, while other branches are
9501 unfinished, this mode is not for you.  Also this mode is not
9502 suitable for pushing into a shared central repository, as other
9503 people may add new branches there, or update the tip of existing
9504 branches outside your control.</p></div>
9505 <div class="paragraph"><p>This used to be the default, but not since Git 2.0 (<code>simple</code> is the
9506 new default).</p></div>
9507 </li>
9508 </ul></div>
9509 </div></div>
9510 </dd>
9511 <dt class="hdlist1">
9512 push.followTags
9513 </dt>
9514 <dd>
9515 <p>
9516         If set to true enable <code>--follow-tags</code> option by default.  You
9517         may override this configuration at time of push by specifying
9518         <code>--no-follow-tags</code>.
9519 </p>
9520 </dd>
9521 <dt class="hdlist1">
9522 push.gpgSign
9523 </dt>
9524 <dd>
9525 <p>
9526         May be set to a boolean value, or the string <em>if-asked</em>. A true
9527         value causes all pushes to be GPG signed, as if <code>--signed</code> is
9528         passed to <a href="git-push.html">git-push(1)</a>. The string <em>if-asked</em> causes
9529         pushes to be signed if the server supports it, as if
9530         <code>--signed=if-asked</code> is passed to <em>git push</em>. A false value may
9531         override a value from a lower-priority config file. An explicit
9532         command-line flag always overrides this config option.
9533 </p>
9534 </dd>
9535 <dt class="hdlist1">
9536 push.pushOption
9537 </dt>
9538 <dd>
9539 <p>
9540         When no <code>--push-option=&lt;option&gt;</code> argument is given from the
9541         command line, <code>git push</code> behaves as if each &lt;value&gt; of
9542         this variable is given as <code>--push-option=&lt;value&gt;</code>.
9543 </p>
9544 <div class="paragraph"><p>This is a multi-valued variable, and an empty value can be used in a
9545 higher priority configuration file (e.g. <code>.git/config</code> in a
9546 repository) to clear the values inherited from a lower priority
9547 configuration files (e.g. <code>$HOME/.gitconfig</code>).</p></div>
9548 <div class="listingblock">
9549 <div class="content">
9550 <pre><code>Example:
9551
9552 /etc/gitconfig
9553   push.pushoption = a
9554   push.pushoption = b
9555
9556 ~/.gitconfig
9557   push.pushoption = c
9558
9559 repo/.git/config
9560   push.pushoption =
9561   push.pushoption = b
9562
9563 This will result in only b (a and c are cleared).</code></pre>
9564 </div></div>
9565 </dd>
9566 <dt class="hdlist1">
9567 push.recurseSubmodules
9568 </dt>
9569 <dd>
9570 <p>
9571         May be "check", "on-demand", "only", or "no", with the same behavior
9572         as that of "push --recurse-submodules".
9573         If not set, <em>no</em> is used by default, unless <em>submodule.recurse</em> is
9574         set (in which case a <em>true</em> value means <em>on-demand</em>).
9575 </p>
9576 </dd>
9577 <dt class="hdlist1">
9578 push.useForceIfIncludes
9579 </dt>
9580 <dd>
9581 <p>
9582         If set to "true", it is equivalent to specifying
9583         <code>--force-if-includes</code> as an option to <a href="git-push.html">git-push(1)</a>
9584         in the command line. Adding <code>--no-force-if-includes</code> at the
9585         time of push overrides this configuration setting.
9586 </p>
9587 </dd>
9588 <dt class="hdlist1">
9589 push.negotiate
9590 </dt>
9591 <dd>
9592 <p>
9593         If set to "true", attempt to reduce the size of the packfile
9594         sent by rounds of negotiation in which the client and the
9595         server attempt to find commits in common. If "false", Git will
9596         rely solely on the server&#8217;s ref advertisement to find commits
9597         in common.
9598 </p>
9599 </dd>
9600 <dt class="hdlist1">
9601 push.useBitmaps
9602 </dt>
9603 <dd>
9604 <p>
9605         If set to "false", disable use of bitmaps for "git push" even if
9606         <code>pack.useBitmaps</code> is "true", without preventing other git operations
9607         from using bitmaps. Default is true.
9608 </p>
9609 </dd>
9610 <dt class="hdlist1">
9611 rebase.backend
9612 </dt>
9613 <dd>
9614 <p>
9615         Default backend to use for rebasing.  Possible choices are
9616         <em>apply</em> or <em>merge</em>.  In the future, if the merge backend gains
9617         all remaining capabilities of the apply backend, this setting
9618         may become unused.
9619 </p>
9620 </dd>
9621 <dt class="hdlist1">
9622 rebase.stat
9623 </dt>
9624 <dd>
9625 <p>
9626         Whether to show a diffstat of what changed upstream since the last
9627         rebase. False by default.
9628 </p>
9629 </dd>
9630 <dt class="hdlist1">
9631 rebase.autoSquash
9632 </dt>
9633 <dd>
9634 <p>
9635         If set to true enable <code>--autosquash</code> option by default.
9636 </p>
9637 </dd>
9638 <dt class="hdlist1">
9639 rebase.autoStash
9640 </dt>
9641 <dd>
9642 <p>
9643         When set to true, automatically create a temporary stash entry
9644         before the operation begins, and apply it after the operation
9645         ends.  This means that you can run rebase on a dirty worktree.
9646         However, use with care: the final stash application after a
9647         successful rebase might result in non-trivial conflicts.
9648         This option can be overridden by the <code>--no-autostash</code> and
9649         <code>--autostash</code> options of <a href="git-rebase.html">git-rebase(1)</a>.
9650         Defaults to false.
9651 </p>
9652 </dd>
9653 <dt class="hdlist1">
9654 rebase.updateRefs
9655 </dt>
9656 <dd>
9657 <p>
9658         If set to true enable <code>--update-refs</code> option by default.
9659 </p>
9660 </dd>
9661 <dt class="hdlist1">
9662 rebase.missingCommitsCheck
9663 </dt>
9664 <dd>
9665 <p>
9666         If set to "warn", git rebase -i will print a warning if some
9667         commits are removed (e.g. a line was deleted), however the
9668         rebase will still proceed. If set to "error", it will print
9669         the previous warning and stop the rebase, <em>git rebase
9670         --edit-todo</em> can then be used to correct the error. If set to
9671         "ignore", no checking is done.
9672         To drop a commit without warning or error, use the <code>drop</code>
9673         command in the todo list.
9674         Defaults to "ignore".
9675 </p>
9676 </dd>
9677 <dt class="hdlist1">
9678 rebase.instructionFormat
9679 </dt>
9680 <dd>
9681 <p>
9682         A format string, as specified in <a href="git-log.html">git-log(1)</a>, to be used for the
9683         todo list during an interactive rebase.  The format will
9684         automatically have the long commit hash prepended to the format.
9685 </p>
9686 </dd>
9687 <dt class="hdlist1">
9688 rebase.abbreviateCommands
9689 </dt>
9690 <dd>
9691 <p>
9692         If set to true, <code>git rebase</code> will use abbreviated command names in the
9693         todo list resulting in something like this:
9694 </p>
9695 <div class="listingblock">
9696 <div class="content">
9697 <pre><code>        p deadbee The oneline of the commit
9698         p fa1afe1 The oneline of the next commit
9699         ...</code></pre>
9700 </div></div>
9701 <div class="paragraph"><p>instead of:</p></div>
9702 <div class="listingblock">
9703 <div class="content">
9704 <pre><code>        pick deadbee The oneline of the commit
9705         pick fa1afe1 The oneline of the next commit
9706         ...</code></pre>
9707 </div></div>
9708 <div class="paragraph"><p>Defaults to false.</p></div>
9709 </dd>
9710 <dt class="hdlist1">
9711 rebase.rescheduleFailedExec
9712 </dt>
9713 <dd>
9714 <p>
9715         Automatically reschedule <code>exec</code> commands that failed. This only makes
9716         sense in interactive mode (or when an <code>--exec</code> option was provided).
9717         This is the same as specifying the <code>--reschedule-failed-exec</code> option.
9718 </p>
9719 </dd>
9720 <dt class="hdlist1">
9721 rebase.forkPoint
9722 </dt>
9723 <dd>
9724 <p>
9725         If set to false set <code>--no-fork-point</code> option by default.
9726 </p>
9727 </dd>
9728 <dt class="hdlist1">
9729 rebase.rebaseMerges
9730 </dt>
9731 <dd>
9732 <p>
9733         Whether and how to set the <code>--rebase-merges</code> option by default. Can
9734         be <code>rebase-cousins</code>, <code>no-rebase-cousins</code>, or a boolean. Setting to
9735         true or to <code>no-rebase-cousins</code> is equivalent to
9736         <code>--rebase-merges=no-rebase-cousins</code>, setting to <code>rebase-cousins</code> is
9737         equivalent to <code>--rebase-merges=rebase-cousins</code>, and setting to false is
9738         equivalent to <code>--no-rebase-merges</code>. Passing <code>--rebase-merges</code> on the
9739         command line, with or without an argument, overrides any
9740         <code>rebase.rebaseMerges</code> configuration.
9741 </p>
9742 </dd>
9743 <dt class="hdlist1">
9744 rebase.maxLabelLength
9745 </dt>
9746 <dd>
9747 <p>
9748         When generating label names from commit subjects, truncate the names to
9749         this length. By default, the names are truncated to a little less than
9750         <code>NAME_MAX</code> (to allow e.g. <code>.lock</code> files to be written for the
9751         corresponding loose refs).
9752 </p>
9753 </dd>
9754 <dt class="hdlist1">
9755 receive.advertiseAtomic
9756 </dt>
9757 <dd>
9758 <p>
9759         By default, git-receive-pack will advertise the atomic push
9760         capability to its clients. If you don&#8217;t want to advertise this
9761         capability, set this variable to false.
9762 </p>
9763 </dd>
9764 <dt class="hdlist1">
9765 receive.advertisePushOptions
9766 </dt>
9767 <dd>
9768 <p>
9769         When set to true, git-receive-pack will advertise the push options
9770         capability to its clients. False by default.
9771 </p>
9772 </dd>
9773 <dt class="hdlist1">
9774 receive.autogc
9775 </dt>
9776 <dd>
9777 <p>
9778         By default, git-receive-pack will run "git-gc --auto" after
9779         receiving data from git-push and updating refs.  You can stop
9780         it by setting this variable to false.
9781 </p>
9782 </dd>
9783 <dt class="hdlist1">
9784 receive.certNonceSeed
9785 </dt>
9786 <dd>
9787 <p>
9788         By setting this variable to a string, <code>git receive-pack</code>
9789         will accept a <code>git push --signed</code> and verifies it by using
9790         a "nonce" protected by HMAC using this string as a secret
9791         key.
9792 </p>
9793 </dd>
9794 <dt class="hdlist1">
9795 receive.certNonceSlop
9796 </dt>
9797 <dd>
9798 <p>
9799         When a <code>git push --signed</code> sent a push certificate with a
9800         "nonce" that was issued by a receive-pack serving the same
9801         repository within this many seconds, export the "nonce"
9802         found in the certificate to <code>GIT_PUSH_CERT_NONCE</code> to the
9803         hooks (instead of what the receive-pack asked the sending
9804         side to include).  This may allow writing checks in
9805         <code>pre-receive</code> and <code>post-receive</code> a bit easier.  Instead of
9806         checking <code>GIT_PUSH_CERT_NONCE_SLOP</code> environment variable
9807         that records by how many seconds the nonce is stale to
9808         decide if they want to accept the certificate, they only
9809         can check <code>GIT_PUSH_CERT_NONCE_STATUS</code> is <code>OK</code>.
9810 </p>
9811 </dd>
9812 <dt class="hdlist1">
9813 receive.fsckObjects
9814 </dt>
9815 <dd>
9816 <p>
9817         If it is set to true, git-receive-pack will check all received
9818         objects. See <code>transfer.fsckObjects</code> for what&#8217;s checked.
9819         Defaults to false. If not set, the value of
9820         <code>transfer.fsckObjects</code> is used instead.
9821 </p>
9822 </dd>
9823 <dt class="hdlist1">
9824 receive.fsck.&lt;msg-id&gt;
9825 </dt>
9826 <dd>
9827 <p>
9828         Acts like <code>fsck.&lt;msg-id&gt;</code>, but is used by
9829         <a href="git-receive-pack.html">git-receive-pack(1)</a> instead of
9830         <a href="git-fsck.html">git-fsck(1)</a>. See the <code>fsck.&lt;msg-id&gt;</code> documentation for
9831         details.
9832 </p>
9833 </dd>
9834 <dt class="hdlist1">
9835 receive.fsck.skipList
9836 </dt>
9837 <dd>
9838 <p>
9839         Acts like <code>fsck.skipList</code>, but is used by
9840         <a href="git-receive-pack.html">git-receive-pack(1)</a> instead of
9841         <a href="git-fsck.html">git-fsck(1)</a>. See the <code>fsck.skipList</code> documentation for
9842         details.
9843 </p>
9844 </dd>
9845 <dt class="hdlist1">
9846 receive.keepAlive
9847 </dt>
9848 <dd>
9849 <p>
9850         After receiving the pack from the client, <code>receive-pack</code> may
9851         produce no output (if <code>--quiet</code> was specified) while processing
9852         the pack, causing some networks to drop the TCP connection.
9853         With this option set, if <code>receive-pack</code> does not transmit
9854         any data in this phase for <code>receive.keepAlive</code> seconds, it will
9855         send a short keepalive packet.  The default is 5 seconds; set
9856         to 0 to disable keepalives entirely.
9857 </p>
9858 </dd>
9859 <dt class="hdlist1">
9860 receive.unpackLimit
9861 </dt>
9862 <dd>
9863 <p>
9864         If the number of objects received in a push is below this
9865         limit then the objects will be unpacked into loose object
9866         files. However if the number of received objects equals or
9867         exceeds this limit then the received pack will be stored as
9868         a pack, after adding any missing delta bases.  Storing the
9869         pack from a push can make the push operation complete faster,
9870         especially on slow filesystems.  If not set, the value of
9871         <code>transfer.unpackLimit</code> is used instead.
9872 </p>
9873 </dd>
9874 <dt class="hdlist1">
9875 receive.maxInputSize
9876 </dt>
9877 <dd>
9878 <p>
9879         If the size of the incoming pack stream is larger than this
9880         limit, then git-receive-pack will error out, instead of
9881         accepting the pack file. If not set or set to 0, then the size
9882         is unlimited.
9883 </p>
9884 </dd>
9885 <dt class="hdlist1">
9886 receive.denyDeletes
9887 </dt>
9888 <dd>
9889 <p>
9890         If set to true, git-receive-pack will deny a ref update that deletes
9891         the ref. Use this to prevent such a ref deletion via a push.
9892 </p>
9893 </dd>
9894 <dt class="hdlist1">
9895 receive.denyDeleteCurrent
9896 </dt>
9897 <dd>
9898 <p>
9899         If set to true, git-receive-pack will deny a ref update that
9900         deletes the currently checked out branch of a non-bare repository.
9901 </p>
9902 </dd>
9903 <dt class="hdlist1">
9904 receive.denyCurrentBranch
9905 </dt>
9906 <dd>
9907 <p>
9908         If set to true or "refuse", git-receive-pack will deny a ref update
9909         to the currently checked out branch of a non-bare repository.
9910         Such a push is potentially dangerous because it brings the HEAD
9911         out of sync with the index and working tree. If set to "warn",
9912         print a warning of such a push to stderr, but allow the push to
9913         proceed. If set to false or "ignore", allow such pushes with no
9914         message. Defaults to "refuse".
9915 </p>
9916 <div class="paragraph"><p>Another option is "updateInstead" which will update the working
9917 tree if pushing into the current branch.  This option is
9918 intended for synchronizing working directories when one side is not easily
9919 accessible via interactive ssh (e.g. a live web site, hence the requirement
9920 that the working directory be clean). This mode also comes in handy when
9921 developing inside a VM to test and fix code on different Operating Systems.</p></div>
9922 <div class="paragraph"><p>By default, "updateInstead" will refuse the push if the working tree or
9923 the index have any difference from the HEAD, but the <code>push-to-checkout</code>
9924 hook can be used to customize this.  See <a href="githooks.html">githooks(5)</a>.</p></div>
9925 </dd>
9926 <dt class="hdlist1">
9927 receive.denyNonFastForwards
9928 </dt>
9929 <dd>
9930 <p>
9931         If set to true, git-receive-pack will deny a ref update which is
9932         not a fast-forward. Use this to prevent such an update via a push,
9933         even if that push is forced. This configuration variable is
9934         set when initializing a shared repository.
9935 </p>
9936 </dd>
9937 <dt class="hdlist1">
9938 receive.hideRefs
9939 </dt>
9940 <dd>
9941 <p>
9942         This variable is the same as <code>transfer.hideRefs</code>, but applies
9943         only to <code>receive-pack</code> (and so affects pushes, but not fetches).
9944         An attempt to update or delete a hidden ref by <code>git push</code> is
9945         rejected.
9946 </p>
9947 </dd>
9948 <dt class="hdlist1">
9949 receive.procReceiveRefs
9950 </dt>
9951 <dd>
9952 <p>
9953         This is a multi-valued variable that defines reference prefixes
9954         to match the commands in <code>receive-pack</code>.  Commands matching the
9955         prefixes will be executed by an external hook "proc-receive",
9956         instead of the internal <code>execute_commands</code> function.  If this
9957         variable is not defined, the "proc-receive" hook will never be
9958         used, and all commands will be executed by the internal
9959         <code>execute_commands</code> function.
9960 </p>
9961 <div class="paragraph"><p>For example, if this variable is set to "refs/for", pushing to reference
9962 such as "refs/for/master" will not create or update a reference named
9963 "refs/for/master", but may create or update a pull request directly by
9964 running the hook "proc-receive".</p></div>
9965 <div class="paragraph"><p>Optional modifiers can be provided in the beginning of the value to filter
9966 commands for specific actions: create (a), modify (m), delete (d).
9967 A <code>!</code> can be included in the modifiers to negate the reference prefix entry.
9968 E.g.:</p></div>
9969 <div class="literalblock">
9970 <div class="content">
9971 <pre><code>git config --system --add receive.procReceiveRefs ad:refs/heads
9972 git config --system --add receive.procReceiveRefs !:refs/heads</code></pre>
9973 </div></div>
9974 </dd>
9975 <dt class="hdlist1">
9976 receive.updateServerInfo
9977 </dt>
9978 <dd>
9979 <p>
9980         If set to true, git-receive-pack will run git-update-server-info
9981         after receiving data from git-push and updating refs.
9982 </p>
9983 </dd>
9984 <dt class="hdlist1">
9985 receive.shallowUpdate
9986 </dt>
9987 <dd>
9988 <p>
9989         If set to true, .git/shallow can be updated when new refs
9990         require new shallow roots. Otherwise those refs are rejected.
9991 </p>
9992 </dd>
9993 <dt class="hdlist1">
9994 remote.pushDefault
9995 </dt>
9996 <dd>
9997 <p>
9998         The remote to push to by default.  Overrides
9999         <code>branch.&lt;name&gt;.remote</code> for all branches, and is overridden by
10000         <code>branch.&lt;name&gt;.pushRemote</code> for specific branches.
10001 </p>
10002 </dd>
10003 <dt class="hdlist1">
10004 remote.&lt;name&gt;.url
10005 </dt>
10006 <dd>
10007 <p>
10008         The URL of a remote repository.  See <a href="git-fetch.html">git-fetch(1)</a> or
10009         <a href="git-push.html">git-push(1)</a>.
10010 </p>
10011 </dd>
10012 <dt class="hdlist1">
10013 remote.&lt;name&gt;.pushurl
10014 </dt>
10015 <dd>
10016 <p>
10017         The push URL of a remote repository.  See <a href="git-push.html">git-push(1)</a>.
10018 </p>
10019 </dd>
10020 <dt class="hdlist1">
10021 remote.&lt;name&gt;.proxy
10022 </dt>
10023 <dd>
10024 <p>
10025         For remotes that require curl (http, https and ftp), the URL to
10026         the proxy to use for that remote.  Set to the empty string to
10027         disable proxying for that remote.
10028 </p>
10029 </dd>
10030 <dt class="hdlist1">
10031 remote.&lt;name&gt;.proxyAuthMethod
10032 </dt>
10033 <dd>
10034 <p>
10035         For remotes that require curl (http, https and ftp), the method to use for
10036         authenticating against the proxy in use (probably set in
10037         <code>remote.&lt;name&gt;.proxy</code>). See <code>http.proxyAuthMethod</code>.
10038 </p>
10039 </dd>
10040 <dt class="hdlist1">
10041 remote.&lt;name&gt;.fetch
10042 </dt>
10043 <dd>
10044 <p>
10045         The default set of "refspec" for <a href="git-fetch.html">git-fetch(1)</a>. See
10046         <a href="git-fetch.html">git-fetch(1)</a>.
10047 </p>
10048 </dd>
10049 <dt class="hdlist1">
10050 remote.&lt;name&gt;.push
10051 </dt>
10052 <dd>
10053 <p>
10054         The default set of "refspec" for <a href="git-push.html">git-push(1)</a>. See
10055         <a href="git-push.html">git-push(1)</a>.
10056 </p>
10057 </dd>
10058 <dt class="hdlist1">
10059 remote.&lt;name&gt;.mirror
10060 </dt>
10061 <dd>
10062 <p>
10063         If true, pushing to this remote will automatically behave
10064         as if the <code>--mirror</code> option was given on the command line.
10065 </p>
10066 </dd>
10067 <dt class="hdlist1">
10068 remote.&lt;name&gt;.skipDefaultUpdate
10069 </dt>
10070 <dd>
10071 <p>
10072         If true, this remote will be skipped by default when updating
10073         using <a href="git-fetch.html">git-fetch(1)</a> or the <code>update</code> subcommand of
10074         <a href="git-remote.html">git-remote(1)</a>.
10075 </p>
10076 </dd>
10077 <dt class="hdlist1">
10078 remote.&lt;name&gt;.skipFetchAll
10079 </dt>
10080 <dd>
10081 <p>
10082         If true, this remote will be skipped by default when updating
10083         using <a href="git-fetch.html">git-fetch(1)</a> or the <code>update</code> subcommand of
10084         <a href="git-remote.html">git-remote(1)</a>.
10085 </p>
10086 </dd>
10087 <dt class="hdlist1">
10088 remote.&lt;name&gt;.receivepack
10089 </dt>
10090 <dd>
10091 <p>
10092         The default program to execute on the remote side when pushing.  See
10093         option --receive-pack of <a href="git-push.html">git-push(1)</a>.
10094 </p>
10095 </dd>
10096 <dt class="hdlist1">
10097 remote.&lt;name&gt;.uploadpack
10098 </dt>
10099 <dd>
10100 <p>
10101         The default program to execute on the remote side when fetching.  See
10102         option --upload-pack of <a href="git-fetch-pack.html">git-fetch-pack(1)</a>.
10103 </p>
10104 </dd>
10105 <dt class="hdlist1">
10106 remote.&lt;name&gt;.tagOpt
10107 </dt>
10108 <dd>
10109 <p>
10110         Setting this value to --no-tags disables automatic tag following when
10111         fetching from remote &lt;name&gt;. Setting it to --tags will fetch every
10112         tag from remote &lt;name&gt;, even if they are not reachable from remote
10113         branch heads. Passing these flags directly to <a href="git-fetch.html">git-fetch(1)</a> can
10114         override this setting. See options --tags and --no-tags of
10115         <a href="git-fetch.html">git-fetch(1)</a>.
10116 </p>
10117 </dd>
10118 <dt class="hdlist1">
10119 remote.&lt;name&gt;.vcs
10120 </dt>
10121 <dd>
10122 <p>
10123         Setting this to a value &lt;vcs&gt; will cause Git to interact with
10124         the remote with the git-remote-&lt;vcs&gt; helper.
10125 </p>
10126 </dd>
10127 <dt class="hdlist1">
10128 remote.&lt;name&gt;.prune
10129 </dt>
10130 <dd>
10131 <p>
10132         When set to true, fetching from this remote by default will also
10133         remove any remote-tracking references that no longer exist on the
10134         remote (as if the <code>--prune</code> option was given on the command line).
10135         Overrides <code>fetch.prune</code> settings, if any.
10136 </p>
10137 </dd>
10138 <dt class="hdlist1">
10139 remote.&lt;name&gt;.pruneTags
10140 </dt>
10141 <dd>
10142 <p>
10143         When set to true, fetching from this remote by default will also
10144         remove any local tags that no longer exist on the remote if pruning
10145         is activated in general via <code>remote.&lt;name&gt;.prune</code>, <code>fetch.prune</code> or
10146         <code>--prune</code>. Overrides <code>fetch.pruneTags</code> settings, if any.
10147 </p>
10148 <div class="paragraph"><p>See also <code>remote.&lt;name&gt;.prune</code> and the PRUNING section of
10149 <a href="git-fetch.html">git-fetch(1)</a>.</p></div>
10150 </dd>
10151 <dt class="hdlist1">
10152 remote.&lt;name&gt;.promisor
10153 </dt>
10154 <dd>
10155 <p>
10156         When set to true, this remote will be used to fetch promisor
10157         objects.
10158 </p>
10159 </dd>
10160 <dt class="hdlist1">
10161 remote.&lt;name&gt;.partialclonefilter
10162 </dt>
10163 <dd>
10164 <p>
10165         The filter that will be applied when fetching from this promisor remote.
10166         Changing or clearing this value will only affect fetches for new commits.
10167         To fetch associated objects for commits already present in the local object
10168         database, use the <code>--refetch</code> option of <a href="git-fetch.html">git-fetch(1)</a>.
10169 </p>
10170 </dd>
10171 <dt class="hdlist1">
10172 remotes.&lt;group&gt;
10173 </dt>
10174 <dd>
10175 <p>
10176         The list of remotes which are fetched by "git remote update
10177         &lt;group&gt;".  See <a href="git-remote.html">git-remote(1)</a>.
10178 </p>
10179 </dd>
10180 <dt class="hdlist1">
10181 repack.useDeltaBaseOffset
10182 </dt>
10183 <dd>
10184 <p>
10185         By default, <a href="git-repack.html">git-repack(1)</a> creates packs that use
10186         delta-base offset. If you need to share your repository with
10187         Git older than version 1.4.4, either directly or via a dumb
10188         protocol such as http, then you need to set this option to
10189         "false" and repack. Access from old Git versions over the
10190         native protocol are unaffected by this option.
10191 </p>
10192 </dd>
10193 <dt class="hdlist1">
10194 repack.packKeptObjects
10195 </dt>
10196 <dd>
10197 <p>
10198         If set to true, makes <code>git repack</code> act as if
10199         <code>--pack-kept-objects</code> was passed. See <a href="git-repack.html">git-repack(1)</a> for
10200         details. Defaults to <code>false</code> normally, but <code>true</code> if a bitmap
10201         index is being written (either via <code>--write-bitmap-index</code> or
10202         <code>repack.writeBitmaps</code>).
10203 </p>
10204 </dd>
10205 <dt class="hdlist1">
10206 repack.useDeltaIslands
10207 </dt>
10208 <dd>
10209 <p>
10210         If set to true, makes <code>git repack</code> act as if <code>--delta-islands</code>
10211         was passed. Defaults to <code>false</code>.
10212 </p>
10213 </dd>
10214 <dt class="hdlist1">
10215 repack.writeBitmaps
10216 </dt>
10217 <dd>
10218 <p>
10219         When true, git will write a bitmap index when packing all
10220         objects to disk (e.g., when <code>git repack -a</code> is run).  This
10221         index can speed up the "counting objects" phase of subsequent
10222         packs created for clones and fetches, at the cost of some disk
10223         space and extra time spent on the initial repack.  This has
10224         no effect if multiple packfiles are created.
10225         Defaults to true on bare repos, false otherwise.
10226 </p>
10227 </dd>
10228 <dt class="hdlist1">
10229 repack.updateServerInfo
10230 </dt>
10231 <dd>
10232 <p>
10233         If set to false, <a href="git-repack.html">git-repack(1)</a> will not run
10234         <a href="git-update-server-info.html">git-update-server-info(1)</a>. Defaults to true. Can be overridden
10235         when true by the <code>-n</code> option of <a href="git-repack.html">git-repack(1)</a>.
10236 </p>
10237 </dd>
10238 <dt class="hdlist1">
10239 repack.cruftWindow
10240 </dt>
10241 <dt class="hdlist1">
10242 repack.cruftWindowMemory
10243 </dt>
10244 <dt class="hdlist1">
10245 repack.cruftDepth
10246 </dt>
10247 <dt class="hdlist1">
10248 repack.cruftThreads
10249 </dt>
10250 <dd>
10251 <p>
10252         Parameters used by <a href="git-pack-objects.html">git-pack-objects(1)</a> when generating
10253         a cruft pack and the respective parameters are not given over
10254         the command line. See similarly named <code>pack.*</code> configuration
10255         variables for defaults and meaning.
10256 </p>
10257 </dd>
10258 <dt class="hdlist1">
10259 rerere.autoUpdate
10260 </dt>
10261 <dd>
10262 <p>
10263         When set to true, <code>git-rerere</code> updates the index with the
10264         resulting contents after it cleanly resolves conflicts using
10265         previously recorded resolution.  Defaults to false.
10266 </p>
10267 </dd>
10268 <dt class="hdlist1">
10269 rerere.enabled
10270 </dt>
10271 <dd>
10272 <p>
10273         Activate recording of resolved conflicts, so that identical
10274         conflict hunks can be resolved automatically, should they be
10275         encountered again.  By default, <a href="git-rerere.html">git-rerere(1)</a> is
10276         enabled if there is an <code>rr-cache</code> directory under the
10277         <code>$GIT_DIR</code>, e.g. if "rerere" was previously used in the
10278         repository.
10279 </p>
10280 </dd>
10281 <dt class="hdlist1">
10282 revert.reference
10283 </dt>
10284 <dd>
10285 <p>
10286         Setting this variable to true makes <code>git revert</code> behave
10287         as if the <code>--reference</code> option is given.
10288 </p>
10289 </dd>
10290 <dt class="hdlist1">
10291 safe.bareRepository
10292 </dt>
10293 <dd>
10294 <p>
10295         Specifies which bare repositories Git will work with. The currently
10296         supported values are:
10297 </p>
10298 <div class="ulist"><ul>
10299 <li>
10300 <p>
10301 <code>all</code>: Git works with all bare repositories. This is the default.
10302 </p>
10303 </li>
10304 <li>
10305 <p>
10306 <code>explicit</code>: Git only works with bare repositories specified via
10307   the top-level <code>--git-dir</code> command-line option, or the <code>GIT_DIR</code>
10308   environment variable (see <a href="git.html">git(1)</a>).
10309 </p>
10310 <div class="paragraph"><p>If you do not use bare repositories in your workflow, then it may be
10311 beneficial to set <code>safe.bareRepository</code> to <code>explicit</code> in your global
10312 config. This will protect you from attacks that involve cloning a
10313 repository that contains a bare repository and running a Git command
10314 within that directory.</p></div>
10315 <div class="paragraph"><p>This config setting is only respected in protected configuration (see
10316 <a href="#SCOPES">[SCOPES]</a>). This prevents the untrusted repository from tampering with
10317 this value.</p></div>
10318 </li>
10319 </ul></div>
10320 </dd>
10321 <dt class="hdlist1">
10322 safe.directory
10323 </dt>
10324 <dd>
10325 <p>
10326         These config entries specify Git-tracked directories that are
10327         considered safe even if they are owned by someone other than the
10328         current user. By default, Git will refuse to even parse a Git
10329         config of a repository owned by someone else, let alone run its
10330         hooks, and this config setting allows users to specify exceptions,
10331         e.g. for intentionally shared repositories (see the <code>--shared</code>
10332         option in <a href="git-init.html">git-init(1)</a>).
10333 </p>
10334 <div class="paragraph"><p>This is a multi-valued setting, i.e. you can add more than one directory
10335 via <code>git config --add</code>. To reset the list of safe directories (e.g. to
10336 override any such directories specified in the system config), add a
10337 <code>safe.directory</code> entry with an empty value.</p></div>
10338 <div class="paragraph"><p>This config setting is only respected in protected configuration (see
10339 <a href="#SCOPES">[SCOPES]</a>). This prevents the untrusted repository from tampering with this
10340 value.</p></div>
10341 <div class="paragraph"><p>The value of this setting is interpolated, i.e. <code>~/&lt;path&gt;</code> expands to a
10342 path relative to the home directory and <code>%(prefix)/&lt;path&gt;</code> expands to a
10343 path relative to Git&#8217;s (runtime) prefix.</p></div>
10344 <div class="paragraph"><p>To completely opt-out of this security check, set <code>safe.directory</code> to the
10345 string <code>*</code>. This will allow all repositories to be treated as if their
10346 directory was listed in the <code>safe.directory</code> list. If <code>safe.directory=*</code>
10347 is set in system config and you want to re-enable this protection, then
10348 initialize your list with an empty value before listing the repositories
10349 that you deem safe.</p></div>
10350 <div class="paragraph"><p>As explained, Git only allows you to access repositories owned by
10351 yourself, i.e. the user who is running Git, by default.  When Git
10352 is running as <em>root</em> in a non Windows platform that provides sudo,
10353 however, git checks the SUDO_UID environment variable that sudo creates
10354 and will allow access to the uid recorded as its value in addition to
10355 the id from <em>root</em>.
10356 This is to make it easy to perform a common sequence during installation
10357 "make &amp;&amp; sudo make install".  A git process running under <em>sudo</em> runs as
10358 <em>root</em> but the <em>sudo</em> command exports the environment variable to record
10359 which id the original user has.
10360 If that is not what you would prefer and want git to only trust
10361 repositories that are owned by root instead, then you can remove
10362 the <code>SUDO_UID</code> variable from root&#8217;s environment before invoking git.</p></div>
10363 </dd>
10364 <dt class="hdlist1">
10365 sendemail.identity
10366 </dt>
10367 <dd>
10368 <p>
10369         A configuration identity. When given, causes values in the
10370         <em>sendemail.&lt;identity&gt;</em> subsection to take precedence over
10371         values in the <em>sendemail</em> section. The default identity is
10372         the value of <code>sendemail.identity</code>.
10373 </p>
10374 </dd>
10375 <dt class="hdlist1">
10376 sendemail.smtpEncryption
10377 </dt>
10378 <dd>
10379 <p>
10380         See <a href="git-send-email.html">git-send-email(1)</a> for description.  Note that this
10381         setting is not subject to the <em>identity</em> mechanism.
10382 </p>
10383 </dd>
10384 <dt class="hdlist1">
10385 sendemail.smtpsslcertpath
10386 </dt>
10387 <dd>
10388 <p>
10389         Path to ca-certificates (either a directory or a single file).
10390         Set it to an empty string to disable certificate verification.
10391 </p>
10392 </dd>
10393 <dt class="hdlist1">
10394 sendemail.&lt;identity&gt;.*
10395 </dt>
10396 <dd>
10397 <p>
10398         Identity-specific versions of the <em>sendemail.*</em> parameters
10399         found below, taking precedence over those when this
10400         identity is selected, through either the command-line or
10401         <code>sendemail.identity</code>.
10402 </p>
10403 </dd>
10404 <dt class="hdlist1">
10405 sendemail.multiEdit
10406 </dt>
10407 <dd>
10408 <p>
10409         If true (default), a single editor instance will be spawned to edit
10410         files you have to edit (patches when <code>--annotate</code> is used, and the
10411         summary when <code>--compose</code> is used). If false, files will be edited one
10412         after the other, spawning a new editor each time.
10413 </p>
10414 </dd>
10415 <dt class="hdlist1">
10416 sendemail.confirm
10417 </dt>
10418 <dd>
10419 <p>
10420         Sets the default for whether to confirm before sending. Must be
10421         one of <em>always</em>, <em>never</em>, <em>cc</em>, <em>compose</em>, or <em>auto</em>. See <code>--confirm</code>
10422         in the <a href="git-send-email.html">git-send-email(1)</a> documentation for the meaning of these
10423         values.
10424 </p>
10425 </dd>
10426 <dt class="hdlist1">
10427 sendemail.aliasesFile
10428 </dt>
10429 <dd>
10430 <p>
10431         To avoid typing long email addresses, point this to one or more
10432         email aliases files.  You must also supply <code>sendemail.aliasFileType</code>.
10433 </p>
10434 </dd>
10435 <dt class="hdlist1">
10436 sendemail.aliasFileType
10437 </dt>
10438 <dd>
10439 <p>
10440         Format of the file(s) specified in sendemail.aliasesFile. Must be
10441         one of <em>mutt</em>, <em>mailrc</em>, <em>pine</em>, <em>elm</em>, or <em>gnus</em>, or <em>sendmail</em>.
10442 </p>
10443 <div class="paragraph"><p>What an alias file in each format looks like can be found in
10444 the documentation of the email program of the same name. The
10445 differences and limitations from the standard formats are
10446 described below:</p></div>
10447 <div class="openblock">
10448 <div class="content">
10449 <div class="dlist"><dl>
10450 <dt class="hdlist1">
10451 sendmail
10452 </dt>
10453 <dd>
10454 <div class="ulist"><ul>
10455 <li>
10456 <p>
10457 Quoted aliases and quoted addresses are not supported: lines that
10458         contain a <code>"</code> symbol are ignored.
10459 </p>
10460 </li>
10461 <li>
10462 <p>
10463 Redirection to a file (<code>/path/name</code>) or pipe (<code>|command</code>) is not
10464         supported.
10465 </p>
10466 </li>
10467 <li>
10468 <p>
10469 File inclusion (<code>:include: /path/name</code>) is not supported.
10470 </p>
10471 </li>
10472 <li>
10473 <p>
10474 Warnings are printed on the standard error output for any
10475         explicitly unsupported constructs, and any other lines that are not
10476         recognized by the parser.
10477 </p>
10478 </li>
10479 </ul></div>
10480 </dd>
10481 </dl></div>
10482 </div></div>
10483 </dd>
10484 <dt class="hdlist1">
10485 sendemail.annotate
10486 </dt>
10487 <dt class="hdlist1">
10488 sendemail.bcc
10489 </dt>
10490 <dt class="hdlist1">
10491 sendemail.cc
10492 </dt>
10493 <dt class="hdlist1">
10494 sendemail.ccCmd
10495 </dt>
10496 <dt class="hdlist1">
10497 sendemail.chainReplyTo
10498 </dt>
10499 <dt class="hdlist1">
10500 sendemail.envelopeSender
10501 </dt>
10502 <dt class="hdlist1">
10503 sendemail.from
10504 </dt>
10505 <dt class="hdlist1">
10506 sendemail.headerCmd
10507 </dt>
10508 <dt class="hdlist1">
10509 sendemail.signedoffbycc
10510 </dt>
10511 <dt class="hdlist1">
10512 sendemail.smtpPass
10513 </dt>
10514 <dt class="hdlist1">
10515 sendemail.suppresscc
10516 </dt>
10517 <dt class="hdlist1">
10518 sendemail.suppressFrom
10519 </dt>
10520 <dt class="hdlist1">
10521 sendemail.to
10522 </dt>
10523 <dt class="hdlist1">
10524 sendemail.tocmd
10525 </dt>
10526 <dt class="hdlist1">
10527 sendemail.smtpDomain
10528 </dt>
10529 <dt class="hdlist1">
10530 sendemail.smtpServer
10531 </dt>
10532 <dt class="hdlist1">
10533 sendemail.smtpServerPort
10534 </dt>
10535 <dt class="hdlist1">
10536 sendemail.smtpServerOption
10537 </dt>
10538 <dt class="hdlist1">
10539 sendemail.smtpUser
10540 </dt>
10541 <dt class="hdlist1">
10542 sendemail.thread
10543 </dt>
10544 <dt class="hdlist1">
10545 sendemail.transferEncoding
10546 </dt>
10547 <dt class="hdlist1">
10548 sendemail.validate
10549 </dt>
10550 <dt class="hdlist1">
10551 sendemail.xmailer
10552 </dt>
10553 <dd>
10554 <p>
10555         These configuration variables all provide a default for
10556         <a href="git-send-email.html">git-send-email(1)</a> command-line options. See its
10557         documentation for details.
10558 </p>
10559 </dd>
10560 <dt class="hdlist1">
10561 sendemail.signedoffcc (deprecated)
10562 </dt>
10563 <dd>
10564 <p>
10565         Deprecated alias for <code>sendemail.signedoffbycc</code>.
10566 </p>
10567 </dd>
10568 <dt class="hdlist1">
10569 sendemail.smtpBatchSize
10570 </dt>
10571 <dd>
10572 <p>
10573         Number of messages to be sent per connection, after that a relogin
10574         will happen.  If the value is 0 or undefined, send all messages in
10575         one connection.
10576         See also the <code>--batch-size</code> option of <a href="git-send-email.html">git-send-email(1)</a>.
10577 </p>
10578 </dd>
10579 <dt class="hdlist1">
10580 sendemail.smtpReloginDelay
10581 </dt>
10582 <dd>
10583 <p>
10584         Seconds wait before reconnecting to smtp server.
10585         See also the <code>--relogin-delay</code> option of <a href="git-send-email.html">git-send-email(1)</a>.
10586 </p>
10587 </dd>
10588 <dt class="hdlist1">
10589 sendemail.forbidSendmailVariables
10590 </dt>
10591 <dd>
10592 <p>
10593         To avoid common misconfiguration mistakes, <a href="git-send-email.html">git-send-email(1)</a>
10594         will abort with a warning if any configuration options for "sendmail"
10595         exist. Set this variable to bypass the check.
10596 </p>
10597 </dd>
10598 <dt class="hdlist1">
10599 sequence.editor
10600 </dt>
10601 <dd>
10602 <p>
10603         Text editor used by <code>git rebase -i</code> for editing the rebase instruction file.
10604         The value is meant to be interpreted by the shell when it is used.
10605         It can be overridden by the <code>GIT_SEQUENCE_EDITOR</code> environment variable.
10606         When not configured the default commit message editor is used instead.
10607 </p>
10608 </dd>
10609 <dt class="hdlist1">
10610 showBranch.default
10611 </dt>
10612 <dd>
10613 <p>
10614         The default set of branches for <a href="git-show-branch.html">git-show-branch(1)</a>.
10615         See <a href="git-show-branch.html">git-show-branch(1)</a>.
10616 </p>
10617 </dd>
10618 <dt class="hdlist1">
10619 sparse.expectFilesOutsideOfPatterns
10620 </dt>
10621 <dd>
10622 <p>
10623         Typically with sparse checkouts, files not matching any
10624         sparsity patterns are marked with a SKIP_WORKTREE bit in the
10625         index and are missing from the working tree.  Accordingly, Git
10626         will ordinarily check whether files with the SKIP_WORKTREE bit
10627         are in fact present in the working tree contrary to
10628         expectations.  If Git finds any, it marks those paths as
10629         present by clearing the relevant SKIP_WORKTREE bits.  This
10630         option can be used to tell Git that such
10631         present-despite-skipped files are expected and to stop
10632         checking for them.
10633 </p>
10634 <div class="paragraph"><p>The default is <code>false</code>, which allows Git to automatically recover
10635 from the list of files in the index and working tree falling out of
10636 sync.</p></div>
10637 <div class="paragraph"><p>Set this to <code>true</code> if you are in a setup where some external factor
10638 relieves Git of the responsibility for maintaining the consistency
10639 between the presence of working tree files and sparsity patterns.  For
10640 example, if you have a Git-aware virtual file system that has a robust
10641 mechanism for keeping the working tree and the sparsity patterns up to
10642 date based on access patterns.</p></div>
10643 <div class="paragraph"><p>Regardless of this setting, Git does not check for
10644 present-despite-skipped files unless sparse checkout is enabled, so
10645 this config option has no effect unless <code>core.sparseCheckout</code> is
10646 <code>true</code>.</p></div>
10647 </dd>
10648 <dt class="hdlist1">
10649 splitIndex.maxPercentChange
10650 </dt>
10651 <dd>
10652 <p>
10653         When the split index feature is used, this specifies the
10654         percent of entries the split index can contain compared to the
10655         total number of entries in both the split index and the shared
10656         index before a new shared index is written.
10657         The value should be between 0 and 100. If the value is 0 then
10658         a new shared index is always written, if it is 100 a new
10659         shared index is never written.
10660         By default the value is 20, so a new shared index is written
10661         if the number of entries in the split index would be greater
10662         than 20 percent of the total number of entries.
10663         See <a href="git-update-index.html">git-update-index(1)</a>.
10664 </p>
10665 </dd>
10666 <dt class="hdlist1">
10667 splitIndex.sharedIndexExpire
10668 </dt>
10669 <dd>
10670 <p>
10671         When the split index feature is used, shared index files that
10672         were not modified since the time this variable specifies will
10673         be removed when a new shared index file is created. The value
10674         "now" expires all entries immediately, and "never" suppresses
10675         expiration altogether.
10676         The default value is "2.weeks.ago".
10677         Note that a shared index file is considered modified (for the
10678         purpose of expiration) each time a new split-index file is
10679         either created based on it or read from it.
10680         See <a href="git-update-index.html">git-update-index(1)</a>.
10681 </p>
10682 </dd>
10683 <dt class="hdlist1">
10684 ssh.variant
10685 </dt>
10686 <dd>
10687 <p>
10688         By default, Git determines the command line arguments to use
10689         based on the basename of the configured SSH command (configured
10690         using the environment variable <code>GIT_SSH</code> or <code>GIT_SSH_COMMAND</code> or
10691         the config setting <code>core.sshCommand</code>). If the basename is
10692         unrecognized, Git will attempt to detect support of OpenSSH
10693         options by first invoking the configured SSH command with the
10694         <code>-G</code> (print configuration) option and will subsequently use
10695         OpenSSH options (if that is successful) or no options besides
10696         the host and remote command (if it fails).
10697 </p>
10698 <div class="paragraph"><p>The config variable <code>ssh.variant</code> can be set to override this detection.
10699 Valid values are <code>ssh</code> (to use OpenSSH options), <code>plink</code>, <code>putty</code>,
10700 <code>tortoiseplink</code>, <code>simple</code> (no options except the host and remote command).
10701 The default auto-detection can be explicitly requested using the value
10702 <code>auto</code>.  Any other value is treated as <code>ssh</code>.  This setting can also be
10703 overridden via the environment variable <code>GIT_SSH_VARIANT</code>.</p></div>
10704 <div class="paragraph"><p>The current command-line parameters used for each variant are as
10705 follows:</p></div>
10706 <div class="openblock">
10707 <div class="content">
10708 <div class="ulist"><ul>
10709 <li>
10710 <p>
10711 <code>ssh</code> - [-p port] [-4] [-6] [-o option] [username@]host command
10712 </p>
10713 </li>
10714 <li>
10715 <p>
10716 <code>simple</code> - [username@]host command
10717 </p>
10718 </li>
10719 <li>
10720 <p>
10721 <code>plink</code> or <code>putty</code> - [-P port] [-4] [-6] [username@]host command
10722 </p>
10723 </li>
10724 <li>
10725 <p>
10726 <code>tortoiseplink</code> - [-P port] [-4] [-6] -batch [username@]host command
10727 </p>
10728 </li>
10729 </ul></div>
10730 </div></div>
10731 <div class="paragraph"><p>Except for the <code>simple</code> variant, command-line parameters are likely to
10732 change as git gains new features.</p></div>
10733 </dd>
10734 <dt class="hdlist1">
10735 status.relativePaths
10736 </dt>
10737 <dd>
10738 <p>
10739         By default, <a href="git-status.html">git-status(1)</a> shows paths relative to the
10740         current directory. Setting this variable to <code>false</code> shows paths
10741         relative to the repository root (this was the default for Git
10742         prior to v1.5.4).
10743 </p>
10744 </dd>
10745 <dt class="hdlist1">
10746 status.short
10747 </dt>
10748 <dd>
10749 <p>
10750         Set to true to enable --short by default in <a href="git-status.html">git-status(1)</a>.
10751         The option --no-short takes precedence over this variable.
10752 </p>
10753 </dd>
10754 <dt class="hdlist1">
10755 status.branch
10756 </dt>
10757 <dd>
10758 <p>
10759         Set to true to enable --branch by default in <a href="git-status.html">git-status(1)</a>.
10760         The option --no-branch takes precedence over this variable.
10761 </p>
10762 </dd>
10763 <dt class="hdlist1">
10764 status.aheadBehind
10765 </dt>
10766 <dd>
10767 <p>
10768         Set to true to enable <code>--ahead-behind</code> and false to enable
10769         <code>--no-ahead-behind</code> by default in <a href="git-status.html">git-status(1)</a> for
10770         non-porcelain status formats.  Defaults to true.
10771 </p>
10772 </dd>
10773 <dt class="hdlist1">
10774 status.displayCommentPrefix
10775 </dt>
10776 <dd>
10777 <p>
10778         If set to true, <a href="git-status.html">git-status(1)</a> will insert a comment
10779         prefix before each output line (starting with
10780         <code>core.commentChar</code>, i.e. <code>#</code> by default). This was the
10781         behavior of <a href="git-status.html">git-status(1)</a> in Git 1.8.4 and previous.
10782         Defaults to false.
10783 </p>
10784 </dd>
10785 <dt class="hdlist1">
10786 status.renameLimit
10787 </dt>
10788 <dd>
10789 <p>
10790         The number of files to consider when performing rename detection
10791         in <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a>. Defaults to
10792         the value of diff.renameLimit.
10793 </p>
10794 </dd>
10795 <dt class="hdlist1">
10796 status.renames
10797 </dt>
10798 <dd>
10799 <p>
10800         Whether and how Git detects renames in <a href="git-status.html">git-status(1)</a> and
10801         <a href="git-commit.html">git-commit(1)</a> .  If set to "false", rename detection is
10802         disabled. If set to "true", basic rename detection is enabled.
10803         If set to "copies" or "copy", Git will detect copies, as well.
10804         Defaults to the value of diff.renames.
10805 </p>
10806 </dd>
10807 <dt class="hdlist1">
10808 status.showStash
10809 </dt>
10810 <dd>
10811 <p>
10812         If set to true, <a href="git-status.html">git-status(1)</a> will display the number of
10813         entries currently stashed away.
10814         Defaults to false.
10815 </p>
10816 </dd>
10817 <dt class="hdlist1">
10818 status.showUntrackedFiles
10819 </dt>
10820 <dd>
10821 <p>
10822         By default, <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a> show
10823         files which are not currently tracked by Git. Directories which
10824         contain only untracked files, are shown with the directory name
10825         only. Showing untracked files means that Git needs to lstat() all
10826         the files in the whole repository, which might be slow on some
10827         systems. So, this variable controls how the commands displays
10828         the untracked files. Possible values are:
10829 </p>
10830 <div class="openblock">
10831 <div class="content">
10832 <div class="ulist"><ul>
10833 <li>
10834 <p>
10835 <code>no</code> - Show no untracked files.
10836 </p>
10837 </li>
10838 <li>
10839 <p>
10840 <code>normal</code> - Show untracked files and directories.
10841 </p>
10842 </li>
10843 <li>
10844 <p>
10845 <code>all</code> - Show also individual files in untracked directories.
10846 </p>
10847 </li>
10848 </ul></div>
10849 </div></div>
10850 <div class="paragraph"><p>If this variable is not specified, it defaults to <em>normal</em>.
10851 This variable can be overridden with the -u|--untracked-files option
10852 of <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a>.</p></div>
10853 </dd>
10854 <dt class="hdlist1">
10855 status.submoduleSummary
10856 </dt>
10857 <dd>
10858 <p>
10859         Defaults to false.
10860         If this is set to a non zero number or true (identical to -1 or an
10861         unlimited number), the submodule summary will be enabled and a
10862         summary of commits for modified submodules will be shown (see
10863         --summary-limit option of <a href="git-submodule.html">git-submodule(1)</a>). Please note
10864         that the summary output command will be suppressed for all
10865         submodules when <code>diff.ignoreSubmodules</code> is set to <em>all</em> or only
10866         for those submodules where <code>submodule.&lt;name&gt;.ignore=all</code>. The only
10867         exception to that rule is that status and commit will show staged
10868         submodule changes. To
10869         also view the summary for ignored submodules you can either use
10870         the --ignore-submodules=dirty command-line option or the <em>git
10871         submodule summary</em> command, which shows a similar output but does
10872         not honor these settings.
10873 </p>
10874 </dd>
10875 <dt class="hdlist1">
10876 stash.showIncludeUntracked
10877 </dt>
10878 <dd>
10879 <p>
10880         If this is set to true, the <code>git stash show</code> command will show
10881         the untracked files of a stash entry.  Defaults to false. See
10882         description of <em>show</em> command in <a href="git-stash.html">git-stash(1)</a>.
10883 </p>
10884 </dd>
10885 <dt class="hdlist1">
10886 stash.showPatch
10887 </dt>
10888 <dd>
10889 <p>
10890         If this is set to true, the <code>git stash show</code> command without an
10891         option will show the stash entry in patch form.  Defaults to false.
10892         See description of <em>show</em> command in <a href="git-stash.html">git-stash(1)</a>.
10893 </p>
10894 </dd>
10895 <dt class="hdlist1">
10896 stash.showStat
10897 </dt>
10898 <dd>
10899 <p>
10900         If this is set to true, the <code>git stash show</code> command without an
10901         option will show diffstat of the stash entry.  Defaults to true.
10902         See description of <em>show</em> command in <a href="git-stash.html">git-stash(1)</a>.
10903 </p>
10904 </dd>
10905 <dt class="hdlist1">
10906 submodule.&lt;name&gt;.url
10907 </dt>
10908 <dd>
10909 <p>
10910         The URL for a submodule. This variable is copied from the .gitmodules
10911         file to the git config via <em>git submodule init</em>. The user can change
10912         the configured URL before obtaining the submodule via <em>git submodule
10913         update</em>. If neither submodule.&lt;name&gt;.active or submodule.active are
10914         set, the presence of this variable is used as a fallback to indicate
10915         whether the submodule is of interest to git commands.
10916         See <a href="git-submodule.html">git-submodule(1)</a> and <a href="gitmodules.html">gitmodules(5)</a> for details.
10917 </p>
10918 </dd>
10919 <dt class="hdlist1">
10920 submodule.&lt;name&gt;.update
10921 </dt>
10922 <dd>
10923 <p>
10924         The method by which a submodule is updated by <em>git submodule update</em>,
10925         which is the only affected command, others such as
10926         <em>git checkout --recurse-submodules</em> are unaffected. It exists for
10927         historical reasons, when <em>git submodule</em> was the only command to
10928         interact with submodules; settings like <code>submodule.active</code>
10929         and <code>pull.rebase</code> are more specific. It is populated by
10930         <code>git submodule init</code> from the <a href="gitmodules.html">gitmodules(5)</a> file.
10931         See description of <em>update</em> command in <a href="git-submodule.html">git-submodule(1)</a>.
10932 </p>
10933 </dd>
10934 <dt class="hdlist1">
10935 submodule.&lt;name&gt;.branch
10936 </dt>
10937 <dd>
10938 <p>
10939         The remote branch name for a submodule, used by <code>git submodule
10940         update --remote</code>.  Set this option to override the value found in
10941         the <code>.gitmodules</code> file.  See <a href="git-submodule.html">git-submodule(1)</a> and
10942         <a href="gitmodules.html">gitmodules(5)</a> for details.
10943 </p>
10944 </dd>
10945 <dt class="hdlist1">
10946 submodule.&lt;name&gt;.fetchRecurseSubmodules
10947 </dt>
10948 <dd>
10949 <p>
10950         This option can be used to control recursive fetching of this
10951         submodule. It can be overridden by using the --[no-]recurse-submodules
10952         command-line option to "git fetch" and "git pull".
10953         This setting will override that from in the <a href="gitmodules.html">gitmodules(5)</a>
10954         file.
10955 </p>
10956 </dd>
10957 <dt class="hdlist1">
10958 submodule.&lt;name&gt;.ignore
10959 </dt>
10960 <dd>
10961 <p>
10962         Defines under what circumstances "git status" and the diff family show
10963         a submodule as modified. When set to "all", it will never be considered
10964         modified (but it will nonetheless show up in the output of status and
10965         commit when it has been staged), "dirty" will ignore all changes
10966         to the submodules work tree and
10967         takes only differences between the HEAD of the submodule and the commit
10968         recorded in the superproject into account. "untracked" will additionally
10969         let submodules with modified tracked files in their work tree show up.
10970         Using "none" (the default when this option is not set) also shows
10971         submodules that have untracked files in their work tree as changed.
10972         This setting overrides any setting made in .gitmodules for this submodule,
10973         both settings can be overridden on the command line by using the
10974         "--ignore-submodules" option. The <em>git submodule</em> commands are not
10975         affected by this setting.
10976 </p>
10977 </dd>
10978 <dt class="hdlist1">
10979 submodule.&lt;name&gt;.active
10980 </dt>
10981 <dd>
10982 <p>
10983         Boolean value indicating if the submodule is of interest to git
10984         commands.  This config option takes precedence over the
10985         submodule.active config option. See <a href="gitsubmodules.html">gitsubmodules(7)</a> for
10986         details.
10987 </p>
10988 </dd>
10989 <dt class="hdlist1">
10990 submodule.active
10991 </dt>
10992 <dd>
10993 <p>
10994         A repeated field which contains a pathspec used to match against a
10995         submodule&#8217;s path to determine if the submodule is of interest to git
10996         commands. See <a href="gitsubmodules.html">gitsubmodules(7)</a> for details.
10997 </p>
10998 </dd>
10999 <dt class="hdlist1">
11000 submodule.recurse
11001 </dt>
11002 <dd>
11003 <p>
11004         A boolean indicating if commands should enable the <code>--recurse-submodules</code>
11005         option by default. Defaults to false.
11006 </p>
11007 <div class="paragraph"><p>When set to true, it can be deactivated via the
11008 <code>--no-recurse-submodules</code> option. Note that some Git commands
11009 lacking this option may call some of the above commands affected by
11010 <code>submodule.recurse</code>; for instance <code>git remote update</code> will call
11011 <code>git fetch</code> but does not have a <code>--no-recurse-submodules</code> option.
11012 For these commands a workaround is to temporarily change the
11013 configuration value by using <code>git -c submodule.recurse=0</code>.</p></div>
11014 <div class="paragraph"><p>The following list shows the commands that accept
11015 <code>--recurse-submodules</code> and whether they are supported by this
11016 setting.</p></div>
11017 <div class="ulist"><ul>
11018 <li>
11019 <p>
11020 <code>checkout</code>, <code>fetch</code>, <code>grep</code>, <code>pull</code>, <code>push</code>, <code>read-tree</code>,
11021 <code>reset</code>, <code>restore</code> and <code>switch</code> are always supported.
11022 </p>
11023 </li>
11024 <li>
11025 <p>
11026 <code>clone</code> and <code>ls-files</code> are not supported.
11027 </p>
11028 </li>
11029 <li>
11030 <p>
11031 <code>branch</code> is supported only if <code>submodule.propagateBranches</code> is
11032 enabled
11033 </p>
11034 </li>
11035 </ul></div>
11036 </dd>
11037 <dt class="hdlist1">
11038 submodule.propagateBranches
11039 </dt>
11040 <dd>
11041 <p>
11042         [EXPERIMENTAL] A boolean that enables branching support when
11043         using <code>--recurse-submodules</code> or <code>submodule.recurse=true</code>.
11044         Enabling this will allow certain commands to accept
11045         <code>--recurse-submodules</code> and certain commands that already accept
11046         <code>--recurse-submodules</code> will now consider branches.
11047         Defaults to false.
11048 </p>
11049 </dd>
11050 <dt class="hdlist1">
11051 submodule.fetchJobs
11052 </dt>
11053 <dd>
11054 <p>
11055         Specifies how many submodules are fetched/cloned at the same time.
11056         A positive integer allows up to that number of submodules fetched
11057         in parallel. A value of 0 will give some reasonable default.
11058         If unset, it defaults to 1.
11059 </p>
11060 </dd>
11061 <dt class="hdlist1">
11062 submodule.alternateLocation
11063 </dt>
11064 <dd>
11065 <p>
11066         Specifies how the submodules obtain alternates when submodules are
11067         cloned. Possible values are <code>no</code>, <code>superproject</code>.
11068         By default <code>no</code> is assumed, which doesn&#8217;t add references. When the
11069         value is set to <code>superproject</code> the submodule to be cloned computes
11070         its alternates location relative to the superprojects alternate.
11071 </p>
11072 </dd>
11073 <dt class="hdlist1">
11074 submodule.alternateErrorStrategy
11075 </dt>
11076 <dd>
11077 <p>
11078         Specifies how to treat errors with the alternates for a submodule
11079         as computed via <code>submodule.alternateLocation</code>. Possible values are
11080         <code>ignore</code>, <code>info</code>, <code>die</code>. Default is <code>die</code>. Note that if set to <code>ignore</code>
11081         or <code>info</code>, and if there is an error with the computed alternate, the
11082         clone proceeds as if no alternate was specified.
11083 </p>
11084 </dd>
11085 <dt class="hdlist1">
11086 tag.forceSignAnnotated
11087 </dt>
11088 <dd>
11089 <p>
11090         A boolean to specify whether annotated tags created should be GPG signed.
11091         If <code>--annotate</code> is specified on the command line, it takes
11092         precedence over this option.
11093 </p>
11094 </dd>
11095 <dt class="hdlist1">
11096 tag.sort
11097 </dt>
11098 <dd>
11099 <p>
11100         This variable controls the sort ordering of tags when displayed by
11101         <a href="git-tag.html">git-tag(1)</a>. Without the "--sort=&lt;value&gt;" option provided, the
11102         value of this variable will be used as the default.
11103 </p>
11104 </dd>
11105 <dt class="hdlist1">
11106 tag.gpgSign
11107 </dt>
11108 <dd>
11109 <p>
11110         A boolean to specify whether all tags should be GPG signed.
11111         Use of this option when running in an automated script can
11112         result in a large number of tags being signed. It is therefore
11113         convenient to use an agent to avoid typing your gpg passphrase
11114         several times. Note that this option doesn&#8217;t affect tag signing
11115         behavior enabled by "-u &lt;keyid&gt;" or "--local-user=&lt;keyid&gt;" options.
11116 </p>
11117 </dd>
11118 <dt class="hdlist1">
11119 tar.umask
11120 </dt>
11121 <dd>
11122 <p>
11123         This variable can be used to restrict the permission bits of
11124         tar archive entries.  The default is 0002, which turns off the
11125         world write bit.  The special value "user" indicates that the
11126         archiving user&#8217;s umask will be used instead.  See umask(2) and
11127         <a href="git-archive.html">git-archive(1)</a>.
11128 </p>
11129 </dd>
11130 </dl></div>
11131 <div class="paragraph"><p>Trace2 config settings are only read from the system and global
11132 config files; repository local and worktree config files and <code>-c</code>
11133 command line arguments are not respected.</p></div>
11134 <div class="dlist"><dl>
11135 <dt class="hdlist1">
11136 trace2.normalTarget
11137 </dt>
11138 <dd>
11139 <p>
11140         This variable controls the normal target destination.
11141         It may be overridden by the <code>GIT_TRACE2</code> environment variable.
11142         The following table shows possible values.
11143 </p>
11144 </dd>
11145 <dt class="hdlist1">
11146 trace2.perfTarget
11147 </dt>
11148 <dd>
11149 <p>
11150         This variable controls the performance target destination.
11151         It may be overridden by the <code>GIT_TRACE2_PERF</code> environment variable.
11152         The following table shows possible values.
11153 </p>
11154 </dd>
11155 <dt class="hdlist1">
11156 trace2.eventTarget
11157 </dt>
11158 <dd>
11159 <p>
11160         This variable controls the event target destination.
11161         It may be overridden by the <code>GIT_TRACE2_EVENT</code> environment variable.
11162         The following table shows possible values.
11163 </p>
11164 <div class="openblock">
11165 <div class="content">
11166 <div class="ulist"><ul>
11167 <li>
11168 <p>
11169 <code>0</code> or <code>false</code> - Disables the target.
11170 </p>
11171 </li>
11172 <li>
11173 <p>
11174 <code>1</code> or <code>true</code> - Writes to <code>STDERR</code>.
11175 </p>
11176 </li>
11177 <li>
11178 <p>
11179 <code>[2-9]</code> - Writes to the already opened file descriptor.
11180 </p>
11181 </li>
11182 <li>
11183 <p>
11184 <code>&lt;absolute-pathname&gt;</code> - Writes to the file in append mode. If the target
11185 already exists and is a directory, the traces will be written to files (one
11186 per process) underneath the given directory.
11187 </p>
11188 </li>
11189 <li>
11190 <p>
11191 <code>af_unix:[&lt;socket_type&gt;:]&lt;absolute-pathname&gt;</code> - Write to a
11192 Unix DomainSocket (on platforms that support them).  Socket
11193 type can be either <code>stream</code> or <code>dgram</code>; if omitted Git will
11194 try both.
11195 </p>
11196 </li>
11197 </ul></div>
11198 </div></div>
11199 </dd>
11200 <dt class="hdlist1">
11201 trace2.normalBrief
11202 </dt>
11203 <dd>
11204 <p>
11205         Boolean.  When true <code>time</code>, <code>filename</code>, and <code>line</code> fields are
11206         omitted from normal output.  May be overridden by the
11207         <code>GIT_TRACE2_BRIEF</code> environment variable.  Defaults to false.
11208 </p>
11209 </dd>
11210 <dt class="hdlist1">
11211 trace2.perfBrief
11212 </dt>
11213 <dd>
11214 <p>
11215         Boolean.  When true <code>time</code>, <code>filename</code>, and <code>line</code> fields are
11216         omitted from PERF output.  May be overridden by the
11217         <code>GIT_TRACE2_PERF_BRIEF</code> environment variable.  Defaults to false.
11218 </p>
11219 </dd>
11220 <dt class="hdlist1">
11221 trace2.eventBrief
11222 </dt>
11223 <dd>
11224 <p>
11225         Boolean.  When true <code>time</code>, <code>filename</code>, and <code>line</code> fields are
11226         omitted from event output.  May be overridden by the
11227         <code>GIT_TRACE2_EVENT_BRIEF</code> environment variable.  Defaults to false.
11228 </p>
11229 </dd>
11230 <dt class="hdlist1">
11231 trace2.eventNesting
11232 </dt>
11233 <dd>
11234 <p>
11235         Integer.  Specifies desired depth of nested regions in the
11236         event output.  Regions deeper than this value will be
11237         omitted.  May be overridden by the <code>GIT_TRACE2_EVENT_NESTING</code>
11238         environment variable.  Defaults to 2.
11239 </p>
11240 </dd>
11241 <dt class="hdlist1">
11242 trace2.configParams
11243 </dt>
11244 <dd>
11245 <p>
11246         A comma-separated list of patterns of "important" config
11247         settings that should be recorded in the trace2 output.
11248         For example, <code>core.*,remote.*.url</code> would cause the trace2
11249         output to contain events listing each configured remote.
11250         May be overridden by the <code>GIT_TRACE2_CONFIG_PARAMS</code> environment
11251         variable.  Unset by default.
11252 </p>
11253 </dd>
11254 <dt class="hdlist1">
11255 trace2.envVars
11256 </dt>
11257 <dd>
11258 <p>
11259         A comma-separated list of "important" environment variables that should
11260         be recorded in the trace2 output.  For example,
11261         <code>GIT_HTTP_USER_AGENT,GIT_CONFIG</code> would cause the trace2 output to
11262         contain events listing the overrides for HTTP user agent and the
11263         location of the Git configuration file (assuming any are set).  May be
11264         overridden by the <code>GIT_TRACE2_ENV_VARS</code> environment variable.  Unset by
11265         default.
11266 </p>
11267 </dd>
11268 <dt class="hdlist1">
11269 trace2.destinationDebug
11270 </dt>
11271 <dd>
11272 <p>
11273         Boolean.  When true Git will print error messages when a
11274         trace target destination cannot be opened for writing.
11275         By default, these errors are suppressed and tracing is
11276         silently disabled.  May be overridden by the
11277         <code>GIT_TRACE2_DST_DEBUG</code> environment variable.
11278 </p>
11279 </dd>
11280 <dt class="hdlist1">
11281 trace2.maxFiles
11282 </dt>
11283 <dd>
11284 <p>
11285         Integer.  When writing trace files to a target directory, do not
11286         write additional traces if we would exceed this many files. Instead,
11287         write a sentinel file that will block further tracing to this
11288         directory. Defaults to 0, which disables this check.
11289 </p>
11290 </dd>
11291 <dt class="hdlist1">
11292 transfer.credentialsInUrl
11293 </dt>
11294 <dd>
11295 <p>
11296         A configured URL can contain plaintext credentials in the form
11297         <code>&lt;protocol&gt;://&lt;user&gt;:&lt;password&gt;@&lt;domain&gt;/&lt;path&gt;</code>. You may want
11298         to warn or forbid the use of such configuration (in favor of
11299         using <a href="git-credential.html">git-credential(1)</a>). This will be used on
11300         <a href="git-clone.html">git-clone(1)</a>, <a href="git-fetch.html">git-fetch(1)</a>, <a href="git-push.html">git-push(1)</a>,
11301         and any other direct use of the configured URL.
11302 </p>
11303 <div class="paragraph"><p>Note that this is currently limited to detecting credentials in
11304 <code>remote.&lt;name&gt;.url</code> configuration, it won&#8217;t detect credentials in
11305 <code>remote.&lt;name&gt;.pushurl</code> configuration.</p></div>
11306 <div class="paragraph"><p>You might want to enable this to prevent inadvertent credentials
11307 exposure, e.g. because:</p></div>
11308 <div class="ulist"><ul>
11309 <li>
11310 <p>
11311 The OS or system where you&#8217;re running git may not provide a way or
11312   otherwise allow you to configure the permissions of the
11313   configuration file where the username and/or password are stored.
11314 </p>
11315 </li>
11316 <li>
11317 <p>
11318 Even if it does, having such data stored "at rest" might expose you
11319   in other ways, e.g. a backup process might copy the data to another
11320   system.
11321 </p>
11322 </li>
11323 <li>
11324 <p>
11325 The git programs will pass the full URL to one another as arguments
11326   on the command-line, meaning the credentials will be exposed to other
11327   users on OS&#8217;s or systems that allow other users to see the full
11328   process list of other users. On linux the "hidepid" setting
11329   documented in procfs(5) allows for configuring this behavior.
11330 </p>
11331 <div class="paragraph"><p>If such concerns don&#8217;t apply to you then you probably don&#8217;t need to be
11332 concerned about credentials exposure due to storing that sensitive
11333 data in git&#8217;s configuration files. If you do want to use this, set
11334 <code>transfer.credentialsInUrl</code> to one of these values:</p></div>
11335 </li>
11336 <li>
11337 <p>
11338 <code>allow</code> (default): Git will proceed with its activity without warning.
11339 </p>
11340 </li>
11341 <li>
11342 <p>
11343 <code>warn</code>: Git will write a warning message to <code>stderr</code> when parsing a URL
11344   with a plaintext credential.
11345 </p>
11346 </li>
11347 <li>
11348 <p>
11349 <code>die</code>: Git will write a failure message to <code>stderr</code> when parsing a URL
11350   with a plaintext credential.
11351 </p>
11352 </li>
11353 </ul></div>
11354 </dd>
11355 <dt class="hdlist1">
11356 transfer.fsckObjects
11357 </dt>
11358 <dd>
11359 <p>
11360         When <code>fetch.fsckObjects</code> or <code>receive.fsckObjects</code> are
11361         not set, the value of this variable is used instead.
11362         Defaults to false.
11363 </p>
11364 <div class="paragraph"><p>When set, the fetch or receive will abort in the case of a malformed
11365 object or a link to a nonexistent object. In addition, various other
11366 issues are checked for, including legacy issues (see <code>fsck.&lt;msg-id&gt;</code>),
11367 and potential security issues like the existence of a <code>.GIT</code> directory
11368 or a malicious <code>.gitmodules</code> file (see the release notes for v2.2.1
11369 and v2.17.1 for details). Other sanity and security checks may be
11370 added in future releases.</p></div>
11371 <div class="paragraph"><p>On the receiving side, failing fsckObjects will make those objects
11372 unreachable, see "QUARANTINE ENVIRONMENT" in
11373 <a href="git-receive-pack.html">git-receive-pack(1)</a>. On the fetch side, malformed objects will
11374 instead be left unreferenced in the repository.</p></div>
11375 <div class="paragraph"><p>Due to the non-quarantine nature of the <code>fetch.fsckObjects</code>
11376 implementation it cannot be relied upon to leave the object store
11377 clean like <code>receive.fsckObjects</code> can.</p></div>
11378 <div class="paragraph"><p>As objects are unpacked they&#8217;re written to the object store, so there
11379 can be cases where malicious objects get introduced even though the
11380 "fetch" failed, only to have a subsequent "fetch" succeed because only
11381 new incoming objects are checked, not those that have already been
11382 written to the object store. That difference in behavior should not be
11383 relied upon. In the future, such objects may be quarantined for
11384 "fetch" as well.</p></div>
11385 <div class="paragraph"><p>For now, the paranoid need to find some way to emulate the quarantine
11386 environment if they&#8217;d like the same protection as "push". E.g. in the
11387 case of an internal mirror do the mirroring in two steps, one to fetch
11388 the untrusted objects, and then do a second "push" (which will use the
11389 quarantine) to another internal repo, and have internal clients
11390 consume this pushed-to repository, or embargo internal fetches and
11391 only allow them once a full "fsck" has run (and no new fetches have
11392 happened in the meantime).</p></div>
11393 </dd>
11394 <dt class="hdlist1">
11395 transfer.hideRefs
11396 </dt>
11397 <dd>
11398 <p>
11399         String(s) <code>receive-pack</code> and <code>upload-pack</code> use to decide which
11400         refs to omit from their initial advertisements.  Use more than
11401         one definition to specify multiple prefix strings. A ref that is
11402         under the hierarchies listed in the value of this variable is
11403         excluded, and is hidden when responding to <code>git push</code> or <code>git
11404         fetch</code>.  See <code>receive.hideRefs</code> and <code>uploadpack.hideRefs</code> for
11405         program-specific versions of this config.
11406 </p>
11407 <div class="paragraph"><p>You may also include a <code>!</code> in front of the ref name to negate the entry,
11408 explicitly exposing it, even if an earlier entry marked it as hidden.
11409 If you have multiple hideRefs values, later entries override earlier ones
11410 (and entries in more-specific config files override less-specific ones).</p></div>
11411 <div class="paragraph"><p>If a namespace is in use, the namespace prefix is stripped from each
11412 reference before it is matched against <code>transfer.hiderefs</code> patterns. In
11413 order to match refs before stripping, add a <code>^</code> in front of the ref name. If
11414 you combine <code>!</code> and <code>^</code>, <code>!</code> must be specified first.</p></div>
11415 <div class="paragraph"><p>For example, if <code>refs/heads/master</code> is specified in <code>transfer.hideRefs</code> and
11416 the current namespace is <code>foo</code>, then <code>refs/namespaces/foo/refs/heads/master</code>
11417 is omitted from the advertisements. If <code>uploadpack.allowRefInWant</code> is set,
11418 <code>upload-pack</code> will treat <code>want-ref refs/heads/master</code> in a protocol v2
11419 <code>fetch</code> command as if <code>refs/namespaces/foo/refs/heads/master</code> did not exist.
11420 <code>receive-pack</code>, on the other hand, will still advertise the object id the
11421 ref is pointing to without mentioning its name (a so-called ".have" line).</p></div>
11422 <div class="paragraph"><p>Even if you hide refs, a client may still be able to steal the target
11423 objects via the techniques described in the "SECURITY" section of the
11424 <a href="gitnamespaces.html">gitnamespaces(7)</a> man page; it&#8217;s best to keep private data in a
11425 separate repository.</p></div>
11426 </dd>
11427 <dt class="hdlist1">
11428 transfer.unpackLimit
11429 </dt>
11430 <dd>
11431 <p>
11432         When <code>fetch.unpackLimit</code> or <code>receive.unpackLimit</code> are
11433         not set, the value of this variable is used instead.
11434         The default value is 100.
11435 </p>
11436 </dd>
11437 <dt class="hdlist1">
11438 transfer.advertiseSID
11439 </dt>
11440 <dd>
11441 <p>
11442         Boolean. When true, client and server processes will advertise their
11443         unique session IDs to their remote counterpart. Defaults to false.
11444 </p>
11445 </dd>
11446 <dt class="hdlist1">
11447 transfer.bundleURI
11448 </dt>
11449 <dd>
11450 <p>
11451         When <code>true</code>, local <code>git clone</code> commands will request bundle
11452         information from the remote server (if advertised) and download
11453         bundles before continuing the clone through the Git protocol.
11454         Defaults to <code>false</code>.
11455 </p>
11456 </dd>
11457 <dt class="hdlist1">
11458 uploadarchive.allowUnreachable
11459 </dt>
11460 <dd>
11461 <p>
11462         If true, allow clients to use <code>git archive --remote</code> to request
11463         any tree, whether reachable from the ref tips or not. See the
11464         discussion in the "SECURITY" section of
11465         <a href="git-upload-archive.html">git-upload-archive(1)</a> for more details. Defaults to
11466         <code>false</code>.
11467 </p>
11468 </dd>
11469 <dt class="hdlist1">
11470 uploadpack.hideRefs
11471 </dt>
11472 <dd>
11473 <p>
11474         This variable is the same as <code>transfer.hideRefs</code>, but applies
11475         only to <code>upload-pack</code> (and so affects only fetches, not pushes).
11476         An attempt to fetch a hidden ref by <code>git fetch</code> will fail.  See
11477         also <code>uploadpack.allowTipSHA1InWant</code>.
11478 </p>
11479 </dd>
11480 <dt class="hdlist1">
11481 uploadpack.allowTipSHA1InWant
11482 </dt>
11483 <dd>
11484 <p>
11485         When <code>uploadpack.hideRefs</code> is in effect, allow <code>upload-pack</code>
11486         to accept a fetch request that asks for an object at the tip
11487         of a hidden ref (by default, such a request is rejected).
11488         See also <code>uploadpack.hideRefs</code>.  Even if this is false, a client
11489         may be able to steal objects via the techniques described in the
11490         "SECURITY" section of the <a href="gitnamespaces.html">gitnamespaces(7)</a> man page; it&#8217;s
11491         best to keep private data in a separate repository.
11492 </p>
11493 </dd>
11494 <dt class="hdlist1">
11495 uploadpack.allowReachableSHA1InWant
11496 </dt>
11497 <dd>
11498 <p>
11499         Allow <code>upload-pack</code> to accept a fetch request that asks for an
11500         object that is reachable from any ref tip. However, note that
11501         calculating object reachability is computationally expensive.
11502         Defaults to <code>false</code>.  Even if this is false, a client may be able
11503         to steal objects via the techniques described in the "SECURITY"
11504         section of the <a href="gitnamespaces.html">gitnamespaces(7)</a> man page; it&#8217;s best to
11505         keep private data in a separate repository.
11506 </p>
11507 </dd>
11508 <dt class="hdlist1">
11509 uploadpack.allowAnySHA1InWant
11510 </dt>
11511 <dd>
11512 <p>
11513         Allow <code>upload-pack</code> to accept a fetch request that asks for any
11514         object at all.
11515         Defaults to <code>false</code>.
11516 </p>
11517 </dd>
11518 <dt class="hdlist1">
11519 uploadpack.keepAlive
11520 </dt>
11521 <dd>
11522 <p>
11523         When <code>upload-pack</code> has started <code>pack-objects</code>, there may be a
11524         quiet period while <code>pack-objects</code> prepares the pack. Normally
11525         it would output progress information, but if <code>--quiet</code> was used
11526         for the fetch, <code>pack-objects</code> will output nothing at all until
11527         the pack data begins. Some clients and networks may consider
11528         the server to be hung and give up. Setting this option instructs
11529         <code>upload-pack</code> to send an empty keepalive packet every
11530         <code>uploadpack.keepAlive</code> seconds. Setting this option to 0
11531         disables keepalive packets entirely. The default is 5 seconds.
11532 </p>
11533 </dd>
11534 <dt class="hdlist1">
11535 uploadpack.packObjectsHook
11536 </dt>
11537 <dd>
11538 <p>
11539         If this option is set, when <code>upload-pack</code> would run
11540         <code>git pack-objects</code> to create a packfile for a client, it will
11541         run this shell command instead.  The <code>pack-objects</code> command and
11542         arguments it <em>would</em> have run (including the <code>git pack-objects</code>
11543         at the beginning) are appended to the shell command. The stdin
11544         and stdout of the hook are treated as if <code>pack-objects</code> itself
11545         was run. I.e., <code>upload-pack</code> will feed input intended for
11546         <code>pack-objects</code> to the hook, and expects a completed packfile on
11547         stdout.
11548 </p>
11549 <div class="paragraph"><p>Note that this configuration variable is only respected when it is specified
11550 in protected configuration (see <a href="#SCOPES">[SCOPES]</a>). This is a safety measure
11551 against fetching from untrusted repositories.</p></div>
11552 </dd>
11553 <dt class="hdlist1">
11554 uploadpack.allowFilter
11555 </dt>
11556 <dd>
11557 <p>
11558         If this option is set, <code>upload-pack</code> will support partial
11559         clone and partial fetch object filtering.
11560 </p>
11561 </dd>
11562 <dt class="hdlist1">
11563 uploadpackfilter.allow
11564 </dt>
11565 <dd>
11566 <p>
11567         Provides a default value for unspecified object filters (see: the
11568         below configuration variable). If set to <code>true</code>, this will also
11569         enable all filters which get added in the future.
11570         Defaults to <code>true</code>.
11571 </p>
11572 </dd>
11573 <dt class="hdlist1">
11574 uploadpackfilter.&lt;filter&gt;.allow
11575 </dt>
11576 <dd>
11577 <p>
11578         Explicitly allow or ban the object filter corresponding to
11579         <code>&lt;filter&gt;</code>, where <code>&lt;filter&gt;</code> may be one of: <code>blob:none</code>,
11580         <code>blob:limit</code>, <code>object:type</code>, <code>tree</code>, <code>sparse:oid</code>, or <code>combine</code>.
11581         If using combined filters, both <code>combine</code> and all of the nested
11582         filter kinds must be allowed. Defaults to <code>uploadpackfilter.allow</code>.
11583 </p>
11584 </dd>
11585 <dt class="hdlist1">
11586 uploadpackfilter.tree.maxDepth
11587 </dt>
11588 <dd>
11589 <p>
11590         Only allow <code>--filter=tree:&lt;n&gt;</code> when <code>&lt;n&gt;</code> is no more than the value of
11591         <code>uploadpackfilter.tree.maxDepth</code>. If set, this also implies
11592         <code>uploadpackfilter.tree.allow=true</code>, unless this configuration
11593         variable had already been set. Has no effect if unset.
11594 </p>
11595 </dd>
11596 <dt class="hdlist1">
11597 uploadpack.allowRefInWant
11598 </dt>
11599 <dd>
11600 <p>
11601         If this option is set, <code>upload-pack</code> will support the <code>ref-in-want</code>
11602         feature of the protocol version 2 <code>fetch</code> command.  This feature
11603         is intended for the benefit of load-balanced servers which may
11604         not have the same view of what OIDs their refs point to due to
11605         replication delay.
11606 </p>
11607 </dd>
11608 <dt class="hdlist1">
11609 url.&lt;base&gt;.insteadOf
11610 </dt>
11611 <dd>
11612 <p>
11613         Any URL that starts with this value will be rewritten to
11614         start, instead, with &lt;base&gt;. In cases where some site serves a
11615         large number of repositories, and serves them with multiple
11616         access methods, and some users need to use different access
11617         methods, this feature allows people to specify any of the
11618         equivalent URLs and have Git automatically rewrite the URL to
11619         the best alternative for the particular user, even for a
11620         never-before-seen repository on the site.  When more than one
11621         insteadOf strings match a given URL, the longest match is used.
11622 </p>
11623 <div class="paragraph"><p>Note that any protocol restrictions will be applied to the rewritten
11624 URL. If the rewrite changes the URL to use a custom protocol or remote
11625 helper, you may need to adjust the <code>protocol.*.allow</code> config to permit
11626 the request.  In particular, protocols you expect to use for submodules
11627 must be set to <code>always</code> rather than the default of <code>user</code>. See the
11628 description of <code>protocol.allow</code> above.</p></div>
11629 </dd>
11630 <dt class="hdlist1">
11631 url.&lt;base&gt;.pushInsteadOf
11632 </dt>
11633 <dd>
11634 <p>
11635         Any URL that starts with this value will not be pushed to;
11636         instead, it will be rewritten to start with &lt;base&gt;, and the
11637         resulting URL will be pushed to. In cases where some site serves
11638         a large number of repositories, and serves them with multiple
11639         access methods, some of which do not allow push, this feature
11640         allows people to specify a pull-only URL and have Git
11641         automatically use an appropriate URL to push, even for a
11642         never-before-seen repository on the site.  When more than one
11643         pushInsteadOf strings match a given URL, the longest match is
11644         used.  If a remote has an explicit pushurl, Git will ignore this
11645         setting for that remote.
11646 </p>
11647 </dd>
11648 <dt class="hdlist1">
11649 user.name
11650 </dt>
11651 <dt class="hdlist1">
11652 user.email
11653 </dt>
11654 <dt class="hdlist1">
11655 author.name
11656 </dt>
11657 <dt class="hdlist1">
11658 author.email
11659 </dt>
11660 <dt class="hdlist1">
11661 committer.name
11662 </dt>
11663 <dt class="hdlist1">
11664 committer.email
11665 </dt>
11666 <dd>
11667 <p>
11668         The <code>user.name</code> and <code>user.email</code> variables determine what ends
11669         up in the <code>author</code> and <code>committer</code> field of commit
11670         objects.
11671         If you need the <code>author</code> or <code>committer</code> to be different, the
11672         <code>author.name</code>, <code>author.email</code>, <code>committer.name</code> or
11673         <code>committer.email</code> variables can be set.
11674         Also, all of these can be overridden by the <code>GIT_AUTHOR_NAME</code>,
11675         <code>GIT_AUTHOR_EMAIL</code>, <code>GIT_COMMITTER_NAME</code>,
11676         <code>GIT_COMMITTER_EMAIL</code> and <code>EMAIL</code> environment variables.
11677 </p>
11678 <div class="paragraph"><p>Note that the <code>name</code> forms of these variables conventionally refer to
11679 some form of a personal name.  See <a href="git-commit.html">git-commit(1)</a> and the
11680 environment variables section of <a href="git.html">git(1)</a> for more information on
11681 these settings and the <code>credential.username</code> option if you&#8217;re looking
11682 for authentication credentials instead.</p></div>
11683 </dd>
11684 <dt class="hdlist1">
11685 user.useConfigOnly
11686 </dt>
11687 <dd>
11688 <p>
11689         Instruct Git to avoid trying to guess defaults for <code>user.email</code>
11690         and <code>user.name</code>, and instead retrieve the values only from the
11691         configuration. For example, if you have multiple email addresses
11692         and would like to use a different one for each repository, then
11693         with this configuration option set to <code>true</code> in the global config
11694         along with a name, Git will prompt you to set up an email before
11695         making new commits in a newly cloned repository.
11696         Defaults to <code>false</code>.
11697 </p>
11698 </dd>
11699 <dt class="hdlist1">
11700 user.signingKey
11701 </dt>
11702 <dd>
11703 <p>
11704         If <a href="git-tag.html">git-tag(1)</a> or <a href="git-commit.html">git-commit(1)</a> is not selecting the
11705         key you want it to automatically when creating a signed tag or
11706         commit, you can override the default selection with this variable.
11707         This option is passed unchanged to gpg&#8217;s --local-user parameter,
11708         so you may specify a key using any method that gpg supports.
11709         If gpg.format is set to <code>ssh</code> this can contain the path to either
11710         your private ssh key or the public key when ssh-agent is used.
11711         Alternatively it can contain a public key prefixed with <code>key::</code>
11712         directly (e.g.: "key::ssh-rsa XXXXXX identifier"). The private key
11713         needs to be available via ssh-agent. If not set git will call
11714         gpg.ssh.defaultKeyCommand (e.g.: "ssh-add -L") and try to use the
11715         first key available. For backward compatibility, a raw key which
11716         begins with "ssh-", such as "ssh-rsa XXXXXX identifier", is treated
11717         as "key::ssh-rsa XXXXXX identifier", but this form is deprecated;
11718         use the <code>key::</code> form instead.
11719 </p>
11720 </dd>
11721 <dt class="hdlist1">
11722 versionsort.prereleaseSuffix (deprecated)
11723 </dt>
11724 <dd>
11725 <p>
11726         Deprecated alias for <code>versionsort.suffix</code>.  Ignored if
11727         <code>versionsort.suffix</code> is set.
11728 </p>
11729 </dd>
11730 <dt class="hdlist1">
11731 versionsort.suffix
11732 </dt>
11733 <dd>
11734 <p>
11735         Even when version sort is used in <a href="git-tag.html">git-tag(1)</a>, tagnames
11736         with the same base version but different suffixes are still sorted
11737         lexicographically, resulting e.g. in prerelease tags appearing
11738         after the main release (e.g. "1.0-rc1" after "1.0").  This
11739         variable can be specified to determine the sorting order of tags
11740         with different suffixes.
11741 </p>
11742 <div class="paragraph"><p>By specifying a single suffix in this variable, any tagname containing
11743 that suffix will appear before the corresponding main release.  E.g. if
11744 the variable is set to "-rc", then all "1.0-rcX" tags will appear before
11745 "1.0".  If specified multiple times, once per suffix, then the order of
11746 suffixes in the configuration will determine the sorting order of tagnames
11747 with those suffixes.  E.g. if "-pre" appears before "-rc" in the
11748 configuration, then all "1.0-preX" tags will be listed before any
11749 "1.0-rcX" tags.  The placement of the main release tag relative to tags
11750 with various suffixes can be determined by specifying the empty suffix
11751 among those other suffixes.  E.g. if the suffixes "-rc", "", "-ck" and
11752 "-bfs" appear in the configuration in this order, then all "v4.8-rcX" tags
11753 are listed first, followed by "v4.8", then "v4.8-ckX" and finally
11754 "v4.8-bfsX".</p></div>
11755 <div class="paragraph"><p>If more than one suffixes match the same tagname, then that tagname will
11756 be sorted according to the suffix which starts at the earliest position in
11757 the tagname.  If more than one different matching suffixes start at
11758 that earliest position, then that tagname will be sorted according to the
11759 longest of those suffixes.
11760 The sorting order between different suffixes is undefined if they are
11761 in multiple config files.</p></div>
11762 </dd>
11763 <dt class="hdlist1">
11764 web.browser
11765 </dt>
11766 <dd>
11767 <p>
11768         Specify a web browser that may be used by some commands.
11769         Currently only <a href="git-instaweb.html">git-instaweb(1)</a> and <a href="git-help.html">git-help(1)</a>
11770         may use it.
11771 </p>
11772 </dd>
11773 <dt class="hdlist1">
11774 worktree.guessRemote
11775 </dt>
11776 <dd>
11777 <p>
11778         If no branch is specified and neither <code>-b</code> nor <code>-B</code> nor
11779         <code>--detach</code> is used, then <code>git worktree add</code> defaults to
11780         creating a new branch from HEAD.  If <code>worktree.guessRemote</code> is
11781         set to true, <code>worktree add</code> tries to find a remote-tracking
11782         branch whose name uniquely matches the new branch name.  If
11783         such a branch exists, it is checked out and set as "upstream"
11784         for the new branch.  If no such match can be found, it falls
11785         back to creating a new branch from the current HEAD.
11786 </p>
11787 </dd>
11788 </dl></div>
11789 </div>
11790 </div>
11791 </div>
11792 <div class="sect1">
11793 <h2 id="_bugs">BUGS</h2>
11794 <div class="sectionbody">
11795 <div class="paragraph"><p>When using the deprecated <code>[section.subsection]</code> syntax, changing a value
11796 will result in adding a multi-line key instead of a change, if the subsection
11797 is given with at least one uppercase character. For example when the config
11798 looks like</p></div>
11799 <div class="listingblock">
11800 <div class="content">
11801 <pre><code>  [section.subsection]
11802     key = value1</code></pre>
11803 </div></div>
11804 <div class="paragraph"><p>and running <code>git config section.Subsection.key value2</code> will result in</p></div>
11805 <div class="listingblock">
11806 <div class="content">
11807 <pre><code>  [section.subsection]
11808     key = value1
11809     key = value2</code></pre>
11810 </div></div>
11811 </div>
11812 </div>
11813 <div class="sect1">
11814 <h2 id="_git">GIT</h2>
11815 <div class="sectionbody">
11816 <div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
11817 </div>
11818 </div>
11819 </div>
11820 <div id="footnotes"><hr /></div>
11821 <div id="footer">
11822 <div id="footer-text">
11823 Last updated
11824  2023-09-22 17:04:28 PDT
11825 </div>
11826 </div>
11827 </body>
11828 </html>