From d09d33db2e61405c02a0bdf4b7c07eb296623a2c Mon Sep 17 00:00:00 2001
From: ttaylorr <ttaylorr@noreply.github.com>
Date: Tue, 24 Sep 2024 17:42:49 +0000
Subject: [PATCH] Update manual pages (2.46.2)

Updated via the `update-git-version-and-manual-pages.yml` GitHub workflow.
---
 .../35a8f8e1fb14cdf92baf4490ae1127a37dcf3bb9  |  480 +
 .../8ce83a5e94562ab0e73c88ef4afd41ae6d2296a7  |  328 +
 .../a13f478d7cb3fc25a95f0e14cff73cd5203e4b57  | 1131 +++
 .../b6eb1ed05504fc766aabc581c310057c6a46f010  | 7022 +++++++++++++
 .../d470969260e7a605742fb34733463f6434be4872  | 1318 +++
 .../docs/MyFirstContribution/2.46.0.html      |    1 +
 .../docs/MyFirstObjectWalk/2.45.0.html        |    1 +
 .../docs/SubmittingPatches/2.46.0.html        |    1 +
 .../docs/api-error-handling/2.37.0.html       |    1 +
 .../content/docs/api-index-skel/2.43.0.html   |    1 +
 .../docs/content/docs/api-merge/2.42.0.html   |    1 +
 .../docs/api-parse-options/2.38.0.html        |    1 +
 .../content/docs/api-simple-ipc/2.43.0.html   |    1 +
 .../docs/content/docs/api-trace2/2.44.0.html  |    1 +
 .../content/docs/bitmap-format/2.46.0.html    |    1 +
 .../docs/content/docs/bundle-uri/2.40.0.html  |    1 +
 .../content/docs/commit-graph/2.43.0.html     |    1 +
 .../docs/content/docs/diff-format/2.43.0.html |    1 +
 .../docs/diff-generate-patch/2.43.0.html      |    1 +
 .../content/docs/diff-options/2.46.0.html     |    1 +
 .../directory-rename-detection/2.33.1.html    |    1 +
 external/docs/content/docs/fetch-options.html |    9 +-
 .../content/docs/fetch-options/2.46.2.html    |  378 +
 .../docs/content/docs/git-add/2.46.0.html     |    1 +
 external/docs/content/docs/git-am/2.46.0.html |    1 +
 .../content/docs/git-annotate/2.41.0.html     |    1 +
 .../docs/content/docs/git-apply/2.43.0.html   |    1 +
 .../content/docs/git-archimport/2.35.0.html   |    1 +
 .../docs/content/docs/git-archive/2.46.0.html |    1 +
 .../docs/git-bisect-lk2009/2.40.0.html        |    1 +
 .../docs/content/docs/git-bisect/2.44.0.html  |    1 +
 .../docs/content/docs/git-blame/2.44.0.html   |    1 +
 .../docs/content/docs/git-branch/2.44.0.html  |    1 +
 .../content/docs/git-bugreport/2.45.0.html    |    1 +
 .../docs/content/docs/git-bundle/2.41.0.html  |    1 +
 .../content/docs/git-cat-file/2.46.1.html     |    1 +
 .../content/docs/git-check-attr/2.43.0.html   |    1 +
 .../content/docs/git-check-ignore/2.43.0.html |    1 +
 .../docs/git-check-mailmap/2.31.0.html        |    1 +
 .../docs/git-check-ref-format/2.43.0.html     |    1 +
 .../docs/git-checkout-index/2.43.0.html       |    1 +
 .../content/docs/git-checkout/2.44.0.html     |    1 +
 .../content/docs/git-cherry-pick/2.45.0.html  |    1 +
 .../docs/content/docs/git-cherry/2.0.5.html   |    1 +
 .../docs/content/docs/git-citool/2.0.5.html   |    1 +
 .../docs/content/docs/git-clean/2.45.0.html   |    1 +
 .../docs/content/docs/git-clone/2.46.0.html   |    1 +
 .../docs/content/docs/git-column/2.43.0.html  |    1 +
 .../content/docs/git-commit-graph/2.46.0.html |    1 +
 .../content/docs/git-commit-tree/2.45.0.html  |    1 +
 .../docs/content/docs/git-commit/2.46.1.html  |    1 +
 external/docs/content/docs/git-config.html    |   17 +-
 .../docs/content/docs/git-config/2.46.2.html  | 8705 +++++++++++++++++
 .../docs/git-count-objects/2.43.0.html        |    1 +
 .../git-credential-cache--daemon/2.39.0.html  |    1 +
 .../docs/git-credential-cache/2.43.0.html     |    1 +
 .../docs/git-credential-store/2.43.0.html     |    1 +
 .../content/docs/git-credential/2.46.0.html   |    1 +
 .../docs/git-cvsexportcommit/2.35.0.html      |    1 +
 .../content/docs/git-cvsimport/2.43.1.html    |    1 +
 .../content/docs/git-cvsserver/2.44.0.html    |    1 +
 .../docs/content/docs/git-daemon/2.44.0.html  |    1 +
 .../content/docs/git-describe/2.42.0.html     |    1 +
 .../content/docs/git-diagnose/2.44.0.html     |    1 +
 .../content/docs/git-diff-files/2.46.0.html   |    1 +
 .../content/docs/git-diff-index/2.46.0.html   |    1 +
 .../content/docs/git-diff-tree/2.46.1.html    |    1 +
 .../docs/content/docs/git-diff/2.46.0.html    |    1 +
 .../content/docs/git-difftool/2.45.0.html     |    1 +
 .../content/docs/git-fast-export/2.45.0.html  |    1 +
 .../content/docs/git-fast-import/2.45.0.html  |    1 +
 .../content/docs/git-fetch-pack/2.43.0.html   |    1 +
 external/docs/content/docs/git-fetch.html     |    9 +-
 .../docs/content/docs/git-fetch/2.46.2.html   | 1385 +++
 .../docs/git-filter-branch/2.44.0.html        |    1 +
 .../docs/git-fmt-merge-msg/2.35.0.html        |    1 +
 .../content/docs/git-for-each-ref/2.45.0.html |    1 +
 .../docs/git-for-each-repo/2.46.0.html        |    1 +
 .../content/docs/git-format-patch/2.46.0.html |    1 +
 .../content/docs/git-fsck-objects/2.0.5.html  |    1 +
 .../docs/content/docs/git-fsck/2.45.2.html    |    1 +
 .../docs/git-fsmonitor--daemon/2.43.0.html    |    1 +
 external/docs/content/docs/git-gc/2.43.0.html |    1 +
 .../docs/git-get-tar-commit-id/2.43.0.html    |    1 +
 .../docs/content/docs/git-grep/2.45.0.html    |    1 +
 .../docs/content/docs/git-gui/2.46.0.html     |    1 +
 .../content/docs/git-hash-object/2.43.0.html  |    1 +
 .../docs/content/docs/git-help/2.43.0.html    |    1 +
 .../docs/content/docs/git-hook/2.43.0.html    |    1 +
 .../content/docs/git-http-backend/2.43.0.html |    1 +
 .../content/docs/git-http-fetch/2.43.0.html   |    1 +
 .../content/docs/git-http-push/2.43.0.html    |    1 +
 .../content/docs/git-imap-send/2.43.1.html    |    1 +
 .../content/docs/git-index-pack/2.44.0.html   |    1 +
 .../docs/content/docs/git-init-db/2.35.0.html |    1 +
 .../docs/content/docs/git-init/2.45.0.html    |    1 +
 .../content/docs/git-instaweb/2.21.0.html     |    1 +
 .../docs/git-interpret-trailers/2.45.0.html   |    1 +
 .../docs/content/docs/git-log/2.46.0.html     |    1 +
 .../content/docs/git-ls-files/2.46.1.html     |    1 +
 .../content/docs/git-ls-remote/2.46.0.html    |    1 +
 .../docs/content/docs/git-ls-tree/2.42.0.html |    1 +
 .../content/docs/git-mailinfo/2.43.0.html     |    1 +
 .../content/docs/git-mailsplit/2.43.0.html    |    1 +
 .../docs/content/docs/git-maintenance.html    |    8 +-
 .../content/docs/git-maintenance/2.46.2.html  |  617 ++
 .../content/docs/git-merge-base/2.43.0.html   |    1 +
 .../content/docs/git-merge-file/2.44.0.html   |    1 +
 .../content/docs/git-merge-index/2.35.0.html  |    1 +
 .../docs/git-merge-one-file/2.0.5.html        |    1 +
 .../content/docs/git-merge-tree/2.46.0.html   |    1 +
 .../docs/content/docs/git-merge/2.43.1.html   |    1 +
 .../docs/git-mergetool--lib/2.43.0.html       |    1 +
 .../content/docs/git-mergetool/2.45.0.html    |    1 +
 .../docs/content/docs/git-mktag/2.43.0.html   |    1 +
 .../docs/content/docs/git-mktree/2.43.0.html  |    1 +
 .../docs/git-multi-pack-index/2.38.2.html     |    1 +
 external/docs/content/docs/git-mv/2.44.0.html |    1 +
 .../content/docs/git-name-rev/2.43.0.html     |    1 +
 .../docs/content/docs/git-notes/2.44.0.html   |    1 +
 external/docs/content/docs/git-p4/2.37.0.html |    1 +
 .../content/docs/git-pack-objects/2.43.0.html |    1 +
 .../docs/git-pack-redundant/2.41.0.html       |    1 +
 .../content/docs/git-pack-refs/2.45.0.html    |    1 +
 .../content/docs/git-patch-id/2.39.0.html     |    1 +
 .../content/docs/git-prune-packed/2.43.0.html |    1 +
 .../docs/content/docs/git-prune/2.43.0.html   |    1 +
 external/docs/content/docs/git-pull.html      |    9 +-
 .../docs/content/docs/git-pull/2.46.2.html    | 1440 +++
 .../docs/content/docs/git-push/2.45.0.html    |    1 +
 .../content/docs/git-quiltimport/2.43.0.html  |    1 +
 .../content/docs/git-range-diff/2.43.0.html   |    1 +
 .../content/docs/git-read-tree/2.43.0.html    |    1 +
 .../docs/content/docs/git-rebase/2.46.1.html  |    1 +
 .../content/docs/git-receive-pack/2.43.0.html |    1 +
 .../docs/content/docs/git-reflog/2.45.0.html  |    1 +
 .../docs/content/docs/git-refs/2.46.0.html    |    1 +
 .../content/docs/git-remote-ext/2.43.0.html   |    1 +
 .../content/docs/git-remote-fd/2.43.0.html    |    1 +
 .../docs/content/docs/git-remote/2.45.0.html  |    1 +
 .../docs/content/docs/git-repack/2.43.0.html  |    1 +
 .../docs/content/docs/git-replace/2.44.0.html |    1 +
 .../docs/content/docs/git-replay/2.45.0.html  |    1 +
 .../content/docs/git-request-pull/2.43.0.html |    1 +
 .../docs/content/docs/git-rerere/2.39.0.html  |    1 +
 .../docs/content/docs/git-reset/2.39.3.html   |    1 +
 .../docs/content/docs/git-restore/2.43.0.html |    1 +
 .../content/docs/git-rev-list/2.45.0.html     |    1 +
 .../content/docs/git-rev-parse/2.46.0.html    |    1 +
 .../docs/content/docs/git-revert/2.44.0.html  |    1 +
 external/docs/content/docs/git-rm/2.43.0.html |    1 +
 .../content/docs/git-send-email/2.45.0.html   |    1 +
 .../content/docs/git-send-pack/2.43.0.html    |    1 +
 .../docs/git-sh-i18n--envsubst/2.0.5.html     |    1 +
 .../docs/content/docs/git-sh-i18n/2.0.5.html  |    1 +
 .../content/docs/git-sh-setup/2.43.0.html     |    1 +
 .../docs/content/docs/git-shell/2.18.0.html   |    1 +
 .../content/docs/git-shortlog/2.45.0.html     |    1 +
 .../content/docs/git-show-branch/2.46.0.html  |    1 +
 .../content/docs/git-show-index/2.42.0.html   |    1 +
 .../content/docs/git-show-ref/2.46.0.html     |    1 +
 .../docs/content/docs/git-show/2.46.0.html    |    1 +
 .../docs/git-sparse-checkout/2.42.0.html      |    1 +
 .../docs/content/docs/git-stage/2.35.0.html   |    1 +
 .../docs/content/docs/git-stash/2.43.0.html   |    1 +
 .../docs/content/docs/git-status/2.45.0.html  |    1 +
 .../content/docs/git-stripspace/2.43.0.html   |    1 +
 .../content/docs/git-submodule/2.44.0.html    |    1 +
 .../docs/content/docs/git-svn/2.44.0.html     |    1 +
 .../docs/content/docs/git-switch/2.44.0.html  |    1 +
 .../content/docs/git-symbolic-ref/2.43.0.html |    1 +
 .../docs/content/docs/git-tag/2.46.0.html     |    1 +
 .../docs/content/docs/git-tools/2.13.7.html   |    1 +
 .../content/docs/git-unpack-file/2.0.5.html   |    1 +
 .../docs/git-unpack-objects/2.11.4.html       |    1 +
 .../content/docs/git-update-index/2.46.0.html |    1 +
 .../content/docs/git-update-ref/2.46.0.html   |    1 +
 .../docs/git-update-server-info/2.43.0.html   |    1 +
 .../docs/git-upload-archive/2.39.0.html       |    1 +
 .../content/docs/git-upload-pack/2.45.1.html  |    1 +
 .../docs/content/docs/git-var/2.43.0.html     |    1 +
 .../docs/git-verify-commit/2.39.0.html        |    1 +
 .../content/docs/git-verify-pack/2.43.0.html  |    1 +
 .../content/docs/git-verify-tag/2.39.0.html   |    1 +
 .../docs/content/docs/git-version/2.33.1.html |    1 +
 .../content/docs/git-web--browse/2.35.0.html  |    1 +
 .../content/docs/git-whatchanged/2.43.0.html  |    1 +
 .../content/docs/git-worktree/2.43.1.html     |    1 +
 .../content/docs/git-write-tree/2.0.5.html    |    1 +
 external/docs/content/docs/git/2.46.0.html    |    1 +
 .../content/docs/gitattributes/2.46.0.html    |    1 +
 external/docs/content/docs/gitcli/2.45.0.html |    1 +
 .../content/docs/gitcore-tutorial/2.43.1.html |    1 +
 .../content/docs/gitcredentials/2.42.0.html   |    1 +
 .../content/docs/gitcvs-migration/2.12.5.html |    1 +
 .../docs/content/docs/gitdiffcore/2.44.0.html |    1 +
 .../docs/content/docs/giteveryday/2.43.0.html |    1 +
 external/docs/content/docs/gitfaq/2.46.0.html |    1 +
 .../content/docs/gitformat-bundle/2.43.0.html |    1 +
 .../content/docs/gitformat-chunk/2.43.0.html  |    1 +
 .../docs/gitformat-commit-graph/2.46.0.html   |    1 +
 .../content/docs/gitformat-index/2.44.0.html  |    1 +
 .../content/docs/gitformat-pack/2.44.0.html   |    1 +
 .../docs/gitformat-signature/2.40.0.html      |    1 +
 .../docs/content/docs/gitglossary/2.46.0.html |    1 +
 .../docs/content/docs/githooks/2.46.1.html    |    1 +
 .../docs/content/docs/gitignore/2.42.0.html   |    1 +
 external/docs/content/docs/gitk/2.44.0.html   |    1 +
 .../docs/content/docs/gitmailmap/2.32.0.html  |    1 +
 .../docs/content/docs/gitmodules/2.42.0.html  |    1 +
 .../content/docs/gitnamespaces/2.32.0.html    |    1 +
 .../docs/content/docs/gitpacking/2.46.0.html  |    1 +
 .../docs/gitprotocol-capabilities/2.44.0.html |    1 +
 .../docs/gitprotocol-common/2.43.0.html       |    1 +
 .../content/docs/gitprotocol-http/2.44.0.html |    1 +
 .../content/docs/gitprotocol-pack/2.43.0.html |    1 +
 .../content/docs/gitprotocol-v2/2.45.0.html   |    1 +
 .../docs/gitremote-helpers/2.45.0.html        |    1 +
 .../docs/gitrepository-layout/2.45.0.html     |    1 +
 .../content/docs/gitrevisions/2.42.0.html     |    1 +
 .../content/docs/gitsubmodules/2.44.0.html    |    1 +
 .../content/docs/gittutorial-2/2.23.0.html    |    1 +
 .../docs/content/docs/gittutorial/2.46.1.html |    1 +
 .../docs/content/docs/gitweb.conf/2.44.0.html |    1 +
 external/docs/content/docs/gitweb/2.44.0.html |    1 +
 .../content/docs/gitworkflows/2.35.0.html     |    1 +
 .../docs/hash-function-transition/2.40.0.html |    1 +
 .../long-running-process-protocol/2.38.0.html |    1 +
 .../content/docs/merge-options/2.43.1.html    |    1 +
 .../content/docs/merge-strategies/2.34.0.html |    1 +
 .../content/docs/multi-pack-index/2.36.0.html |    1 +
 .../content/docs/pack-heuristics/2.0.5.html   |    1 +
 .../content/docs/packfile-uri/2.38.0.html     |    1 +
 .../docs/parallel-checkout/2.43.0.html        |    1 +
 .../content/docs/partial-clone/2.43.0.html    |    1 +
 .../content/docs/pretty-formats/2.45.0.html   |    1 +
 .../content/docs/pretty-options/2.43.0.html   |    1 +
 .../content/docs/pull-fetch-param/2.43.0.html |    1 +
 .../docs/content/docs/racy-git/2.43.0.html    |    1 +
 .../docs/content/docs/reftable/2.43.0.html    |    1 +
 .../docs/remembering-renames/2.42.0.html      |    1 +
 .../docs/repository-version/2.45.0.html       |    1 +
 external/docs/content/docs/rerere/2.43.0.html |    1 +
 .../docs/rev-list-description/2.29.0.html     |    1 +
 .../content/docs/rev-list-options/2.45.0.html |    1 +
 .../docs/content/docs/revisions/2.42.0.html   |    1 +
 external/docs/content/docs/scalar/2.42.1.html |    1 +
 .../docs/send-pack-pipeline/2.0.5.html        |    1 +
 .../docs/content/docs/shallow/2.29.0.html     |    1 +
 .../content/docs/sparse-checkout/2.39.0.html  |    1 +
 .../content/docs/sparse-index/2.32.0.html     |    1 +
 .../content/docs/trivial-merge/2.15.4.html    |    1 +
 .../docs/content/docs/unit-tests/2.44.0.html  |    1 +
 .../docs/content/docs/user-manual/2.46.0.html |    1 +
 .../docs/content/docs/vimdiff/2.45.0.html     |    1 +
 external/docs/data/docs.yml                   |  770 +-
 256 files changed, 23605 insertions(+), 261 deletions(-)
 create mode 100644 external/docs/asciidoc/35a8f8e1fb14cdf92baf4490ae1127a37dcf3bb9
 create mode 100644 external/docs/asciidoc/8ce83a5e94562ab0e73c88ef4afd41ae6d2296a7
 create mode 100644 external/docs/asciidoc/a13f478d7cb3fc25a95f0e14cff73cd5203e4b57
 create mode 100644 external/docs/asciidoc/b6eb1ed05504fc766aabc581c310057c6a46f010
 create mode 100644 external/docs/asciidoc/d470969260e7a605742fb34733463f6434be4872
 create mode 100644 external/docs/content/docs/fetch-options/2.46.2.html
 create mode 100644 external/docs/content/docs/git-config/2.46.2.html
 create mode 100644 external/docs/content/docs/git-fetch/2.46.2.html
 create mode 100644 external/docs/content/docs/git-maintenance/2.46.2.html
 create mode 100644 external/docs/content/docs/git-pull/2.46.2.html

diff --git a/external/docs/asciidoc/35a8f8e1fb14cdf92baf4490ae1127a37dcf3bb9 b/external/docs/asciidoc/35a8f8e1fb14cdf92baf4490ae1127a37dcf3bb9
new file mode 100644
index 0000000000..f3b44b5110
--- /dev/null
+++ b/external/docs/asciidoc/35a8f8e1fb14cdf92baf4490ae1127a37dcf3bb9
@@ -0,0 +1,480 @@
+git-maintenance(1)
+==================
+
+NAME
+----
+git-maintenance - Run tasks to optimize Git repository data
+
+
+SYNOPSIS
+--------
+[verse]
+'git maintenance' run [<options>]
+'git maintenance' start [--scheduler=<scheduler>]
+'git maintenance' (stop|register|unregister) [<options>]
+
+
+DESCRIPTION
+-----------
+Run tasks to optimize Git repository data, speeding up other Git commands
+and reducing storage requirements for the repository.
+
+Git commands that add repository data, such as `git add` or `git fetch`,
+are optimized for a responsive user experience. These commands do not take
+time to optimize the Git data, since such optimizations scale with the full
+size of the repository while these user commands each perform a relatively
+small action.
+
+The `git maintenance` command provides flexibility for how to optimize the
+Git repository.
+
+SUBCOMMANDS
+-----------
+
+run::
+	Run one or more maintenance tasks. If one or more `--task` options
+	are specified, then those tasks are run in that order. Otherwise,
+	the tasks are determined by which `maintenance.<task>.enabled`
+	config options are true. By default, only `maintenance.gc.enabled`
+	is true.
+
+start::
+	Start running maintenance on the current repository. This performs
+	the same config updates as the `register` subcommand, then updates
+	the background scheduler to run `git maintenance run --scheduled`
+	on an hourly basis.
+
+stop::
+	Halt the background maintenance schedule. The current repository
+	is not removed from the list of maintained repositories, in case
+	the background maintenance is restarted later.
+
+register::
+	Initialize Git config values so any scheduled maintenance will start
+	running on this repository. This adds the repository to the
+	`maintenance.repo` config variable in the current user's global config,
+	or the config specified by --config-file option, and enables some
+	recommended configuration values for `maintenance.<task>.schedule`. The
+	tasks that are enabled are safe for running in the background without
+	disrupting foreground processes.
++
+The `register` subcommand will also set the `maintenance.strategy` config
+value to `incremental`, if this value is not previously set. The
+`incremental` strategy uses the following schedule for each maintenance
+task:
++
+--
+* `gc`: disabled.
+* `commit-graph`: hourly.
+* `prefetch`: hourly.
+* `loose-objects`: daily.
+* `incremental-repack`: daily.
+--
++
+`git maintenance register` will also disable foreground maintenance by
+setting `maintenance.auto = false` in the current repository. This config
+setting will remain after a `git maintenance unregister` command.
+
+unregister::
+	Remove the current repository from background maintenance. This
+	only removes the repository from the configured list. It does not
+	stop the background maintenance processes from running.
++
+The `unregister` subcommand will report an error if the current repository
+is not already registered. Use the `--force` option to return success even
+when the current repository is not registered.
+
+TASKS
+-----
+
+commit-graph::
+	The `commit-graph` job updates the `commit-graph` files incrementally,
+	then verifies that the written data is correct. The incremental
+	write is safe to run alongside concurrent Git processes since it
+	will not expire `.graph` files that were in the previous
+	`commit-graph-chain` file. They will be deleted by a later run based
+	on the expiration delay.
+
+prefetch::
+	The `prefetch` task updates the object directory with the latest
+	objects from all registered remotes. For each remote, a `git fetch`
+	command is run. The configured refspec is modified to place all
+	requested refs within `refs/prefetch/`. Also, tags are not updated.
++
+This is done to avoid disrupting the remote-tracking branches. The end users
+expect these refs to stay unmoved unless they initiate a fetch.  However,
+with the prefetch task, the objects necessary to complete a later real fetch
+would already be obtained, making the real fetch faster.  In the ideal case,
+it will just become an update to a bunch of remote-tracking branches without
+any object transfer.
++
+The `remote.<name>.skipFetchAll` configuration can be used to
+exclude a particular remote from getting prefetched.
+
+gc::
+	Clean up unnecessary files and optimize the local repository. "GC"
+	stands for "garbage collection," but this task performs many
+	smaller tasks. This task can be expensive for large repositories,
+	as it repacks all Git objects into a single pack-file. It can also
+	be disruptive in some situations, as it deletes stale data. See
+	linkgit:git-gc[1] for more details on garbage collection in Git.
+
+loose-objects::
+	The `loose-objects` job cleans up loose objects and places them into
+	pack-files. In order to prevent race conditions with concurrent Git
+	commands, it follows a two-step process. First, it deletes any loose
+	objects that already exist in a pack-file; concurrent Git processes
+	will examine the pack-file for the object data instead of the loose
+	object. Second, it creates a new pack-file (starting with "loose-")
+	containing a batch of loose objects. The batch size is limited to 50
+	thousand objects to prevent the job from taking too long on a
+	repository with many loose objects. The `gc` task writes unreachable
+	objects as loose objects to be cleaned up by a later step only if
+	they are not re-added to a pack-file; for this reason it is not
+	advisable to enable both the `loose-objects` and `gc` tasks at the
+	same time.
+
+incremental-repack::
+	The `incremental-repack` job repacks the object directory
+	using the `multi-pack-index` feature. In order to prevent race
+	conditions with concurrent Git commands, it follows a two-step
+	process. First, it calls `git multi-pack-index expire` to delete
+	pack-files unreferenced by the `multi-pack-index` file. Second, it
+	calls `git multi-pack-index repack` to select several small
+	pack-files and repack them into a bigger one, and then update the
+	`multi-pack-index` entries that refer to the small pack-files to
+	refer to the new pack-file. This prepares those small pack-files
+	for deletion upon the next run of `git multi-pack-index expire`.
+	The selection of the small pack-files is such that the expected
+	size of the big pack-file is at least the batch size; see the
+	`--batch-size` option for the `repack` subcommand in
+	linkgit:git-multi-pack-index[1]. The default batch-size is zero,
+	which is a special case that attempts to repack all pack-files
+	into a single pack-file.
+
+pack-refs::
+	The `pack-refs` task collects the loose reference files and
+	collects them into a single file. This speeds up operations that
+	need to iterate across many references. See linkgit:git-pack-refs[1]
+	for more information.
+
+OPTIONS
+-------
+--auto::
+	When combined with the `run` subcommand, run maintenance tasks
+	only if certain thresholds are met. For example, the `gc` task
+	runs when the number of loose objects exceeds the number stored
+	in the `gc.auto` config setting, or when the number of pack-files
+	exceeds the `gc.autoPackLimit` config setting. Not compatible with
+	the `--schedule` option.
+
+--schedule::
+	When combined with the `run` subcommand, run maintenance tasks
+	only if certain time conditions are met, as specified by the
+	`maintenance.<task>.schedule` config value for each `<task>`.
+	This config value specifies a number of seconds since the last
+	time that task ran, according to the `maintenance.<task>.lastRun`
+	config value. The tasks that are tested are those provided by
+	the `--task=<task>` option(s) or those with
+	`maintenance.<task>.enabled` set to true.
+
+--quiet::
+	Do not report progress or other information over `stderr`.
+
+--task=<task>::
+	If this option is specified one or more times, then only run the
+	specified tasks in the specified order. If no `--task=<task>`
+	arguments are specified, then only the tasks with
+	`maintenance.<task>.enabled` configured as `true` are considered.
+	See the 'TASKS' section for the list of accepted `<task>` values.
+
+--scheduler=auto|crontab|systemd-timer|launchctl|schtasks::
+	When combined with the `start` subcommand, specify the scheduler
+	for running the hourly, daily and weekly executions of
+	`git maintenance run`.
+	Possible values for `<scheduler>` are `auto`, `crontab`
+	(POSIX), `systemd-timer` (Linux), `launchctl` (macOS), and
+	`schtasks` (Windows). When `auto` is specified, the
+	appropriate platform-specific scheduler is used; on Linux,
+	`systemd-timer` is used if available, otherwise
+	`crontab`. Default is `auto`.
+
+
+TROUBLESHOOTING
+---------------
+The `git maintenance` command is designed to simplify the repository
+maintenance patterns while minimizing user wait time during Git commands.
+A variety of configuration options are available to allow customizing this
+process. The default maintenance options focus on operations that complete
+quickly, even on large repositories.
+
+Users may find some cases where scheduled maintenance tasks do not run as
+frequently as intended. Each `git maintenance run` command takes a lock on
+the repository's object database, and this prevents other concurrent
+`git maintenance run` commands from running on the same repository. Without
+this safeguard, competing processes could leave the repository in an
+unpredictable state.
+
+The background maintenance schedule runs `git maintenance run` processes
+on an hourly basis. Each run executes the "hourly" tasks. At midnight,
+that process also executes the "daily" tasks. At midnight on the first day
+of the week, that process also executes the "weekly" tasks. A single
+process iterates over each registered repository, performing the scheduled
+tasks for that frequency. Depending on the number of registered
+repositories and their sizes, this process may take longer than an hour.
+In this case, multiple `git maintenance run` commands may run on the same
+repository at the same time, colliding on the object database lock. This
+results in one of the two tasks not running.
+
+If you find that some maintenance windows are taking longer than one hour
+to complete, then consider reducing the complexity of your maintenance
+tasks. For example, the `gc` task is much slower than the
+`incremental-repack` task. However, this comes at a cost of a slightly
+larger object database. Consider moving more expensive tasks to be run
+less frequently.
+
+Expert users may consider scheduling their own maintenance tasks using a
+different schedule than is available through `git maintenance start` and
+Git configuration options. These users should be aware of the object
+database lock and how concurrent `git maintenance run` commands behave.
+Further, the `git gc` command should not be combined with
+`git maintenance run` commands. `git gc` modifies the object database
+but does not take the lock in the same way as `git maintenance run`. If
+possible, use `git maintenance run --task=gc` instead of `git gc`.
+
+The following sections describe the mechanisms put in place to run
+background maintenance by `git maintenance start` and how to customize
+them.
+
+BACKGROUND MAINTENANCE ON POSIX SYSTEMS
+---------------------------------------
+
+The standard mechanism for scheduling background tasks on POSIX systems
+is cron(8). This tool executes commands based on a given schedule. The
+current list of user-scheduled tasks can be found by running `crontab -l`.
+The schedule written by `git maintenance start` is similar to this:
+
+-----------------------------------------------------------------------
+# BEGIN GIT MAINTENANCE SCHEDULE
+# The following schedule was created by Git
+# Any edits made in this region might be
+# replaced in the future by a Git command.
+
+0 1-23 * * * "/<path>/git" --exec-path="/<path>" for-each-repo --config=maintenance.repo maintenance run --schedule=hourly
+0 0 * * 1-6 "/<path>/git" --exec-path="/<path>" for-each-repo --config=maintenance.repo maintenance run --schedule=daily
+0 0 * * 0 "/<path>/git" --exec-path="/<path>" for-each-repo --config=maintenance.repo maintenance run --schedule=weekly
+
+# END GIT MAINTENANCE SCHEDULE
+-----------------------------------------------------------------------
+
+The comments are used as a region to mark the schedule as written by Git.
+Any modifications within this region will be completely deleted by
+`git maintenance stop` or overwritten by `git maintenance start`.
+
+The `crontab` entry specifies the full path of the `git` executable to
+ensure that the executed `git` command is the same one with which
+`git maintenance start` was issued independent of `PATH`. If the same user
+runs `git maintenance start` with multiple Git executables, then only the
+latest executable is used.
+
+These commands use `git for-each-repo --config=maintenance.repo` to run
+`git maintenance run --schedule=<frequency>` on each repository listed in
+the multi-valued `maintenance.repo` config option. These are typically
+loaded from the user-specific global config. The `git maintenance` process
+then determines which maintenance tasks are configured to run on each
+repository with each `<frequency>` using the `maintenance.<task>.schedule`
+config options. These values are loaded from the global or repository
+config values.
+
+If the config values are insufficient to achieve your desired background
+maintenance schedule, then you can create your own schedule. If you run
+`crontab -e`, then an editor will load with your user-specific `cron`
+schedule. In that editor, you can add your own schedule lines. You could
+start by adapting the default schedule listed earlier, or you could read
+the crontab(5) documentation for advanced scheduling techniques. Please
+do use the full path and `--exec-path` techniques from the default
+schedule to ensure you are executing the correct binaries in your
+schedule.
+
+
+BACKGROUND MAINTENANCE ON LINUX SYSTEMD SYSTEMS
+-----------------------------------------------
+
+While Linux supports `cron`, depending on the distribution, `cron` may
+be an optional package not necessarily installed. On modern Linux
+distributions, systemd timers are superseding it.
+
+If user systemd timers are available, they will be used as a replacement
+of `cron`.
+
+In this case, `git maintenance start` will create user systemd timer units
+and start the timers. The current list of user-scheduled tasks can be found
+by running `systemctl --user list-timers`. The timers written by `git
+maintenance start` are similar to this:
+
+-----------------------------------------------------------------------
+$ systemctl --user list-timers
+NEXT                         LEFT          LAST                         PASSED     UNIT                         ACTIVATES
+Thu 2021-04-29 19:00:00 CEST 42min left    Thu 2021-04-29 18:00:11 CEST 17min ago  git-maintenance@hourly.timer git-maintenance@hourly.service
+Fri 2021-04-30 00:00:00 CEST 5h 42min left Thu 2021-04-29 00:00:11 CEST 18h ago    git-maintenance@daily.timer  git-maintenance@daily.service
+Mon 2021-05-03 00:00:00 CEST 3 days left   Mon 2021-04-26 00:00:11 CEST 3 days ago git-maintenance@weekly.timer git-maintenance@weekly.service
+-----------------------------------------------------------------------
+
+One timer is registered for each `--schedule=<frequency>` option.
+
+The definition of the systemd units can be inspected in the following files:
+
+-----------------------------------------------------------------------
+~/.config/systemd/user/git-maintenance@.timer
+~/.config/systemd/user/git-maintenance@.service
+~/.config/systemd/user/timers.target.wants/git-maintenance@hourly.timer
+~/.config/systemd/user/timers.target.wants/git-maintenance@daily.timer
+~/.config/systemd/user/timers.target.wants/git-maintenance@weekly.timer
+-----------------------------------------------------------------------
+
+`git maintenance start` will overwrite these files and start the timer
+again with `systemctl --user`, so any customization should be done by
+creating a drop-in file, i.e. a `.conf` suffixed file in the
+`~/.config/systemd/user/git-maintenance@.service.d` directory.
+
+`git maintenance stop` will stop the user systemd timers and delete
+the above mentioned files.
+
+For more details, see `systemd.timer(5)`.
+
+
+BACKGROUND MAINTENANCE ON MACOS SYSTEMS
+---------------------------------------
+
+While macOS technically supports `cron`, using `crontab -e` requires
+elevated privileges and the executed process does not have a full user
+context. Without a full user context, Git and its credential helpers
+cannot access stored credentials, so some maintenance tasks are not
+functional.
+
+Instead, `git maintenance start` interacts with the `launchctl` tool,
+which is the recommended way to schedule timed jobs in macOS. Scheduling
+maintenance through `git maintenance (start|stop)` requires some
+`launchctl` features available only in macOS 10.11 or later.
+
+Your user-specific scheduled tasks are stored as XML-formatted `.plist`
+files in `~/Library/LaunchAgents/`. You can see the currently-registered
+tasks using the following command:
+
+-----------------------------------------------------------------------
+$ ls ~/Library/LaunchAgents/org.git-scm.git*
+org.git-scm.git.daily.plist
+org.git-scm.git.hourly.plist
+org.git-scm.git.weekly.plist
+-----------------------------------------------------------------------
+
+One task is registered for each `--schedule=<frequency>` option. To
+inspect how the XML format describes each schedule, open one of these
+`.plist` files in an editor and inspect the `<array>` element following
+the `<key>StartCalendarInterval</key>` element.
+
+`git maintenance start` will overwrite these files and register the
+tasks again with `launchctl`, so any customizations should be done by
+creating your own `.plist` files with distinct names. Similarly, the
+`git maintenance stop` command will unregister the tasks with `launchctl`
+and delete the `.plist` files.
+
+To create more advanced customizations to your background tasks, see
+launchctl.plist(5) for more information.
+
+
+BACKGROUND MAINTENANCE ON WINDOWS SYSTEMS
+-----------------------------------------
+
+Windows does not support `cron` and instead has its own system for
+scheduling background tasks. The `git maintenance start` command uses
+the `schtasks` command to submit tasks to this system. You can inspect
+all background tasks using the Task Scheduler application. The tasks
+added by Git have names of the form `Git Maintenance (<frequency>)`.
+The Task Scheduler GUI has ways to inspect these tasks, but you can also
+export the tasks to XML files and view the details there.
+
+Note that since Git is a console application, these background tasks
+create a console window visible to the current user. This can be changed
+manually by selecting the "Run whether user is logged in or not" option
+in Task Scheduler. This change requires a password input, which is why
+`git maintenance start` does not select it by default.
+
+If you want to customize the background tasks, please rename the tasks
+so future calls to `git maintenance (start|stop)` do not overwrite your
+custom tasks.
+
+CONFIGURATION
+-------------
+
+Everything below this line in this section is selectively included
+from the linkgit:git-config[1] documentation. The content is the same
+as what's found there:
+
+
+maintenance.auto::
+	This boolean config option controls whether some commands run
+	`git maintenance run --auto` after doing their normal work. Defaults
+	to true.
+
+maintenance.strategy::
+	This string config option provides a way to specify one of a few
+	recommended schedules for background maintenance. This only affects
+	which tasks are run during `git maintenance run --schedule=X`
+	commands, provided no `--task=<task>` arguments are provided.
+	Further, if a `maintenance.<task>.schedule` config value is set,
+	then that value is used instead of the one provided by
+	`maintenance.strategy`. The possible strategy strings are:
++
+* `none`: This default setting implies no tasks are run at any schedule.
+* `incremental`: This setting optimizes for performing small maintenance
+  activities that do not delete any data. This does not schedule the `gc`
+  task, but runs the `prefetch` and `commit-graph` tasks hourly, the
+  `loose-objects` and `incremental-repack` tasks daily, and the `pack-refs`
+  task weekly.
+
+maintenance.<task>.enabled::
+	This boolean config option controls whether the maintenance task
+	with name `<task>` is run when no `--task` option is specified to
+	`git maintenance run`. These config values are ignored if a
+	`--task` option exists. By default, only `maintenance.gc.enabled`
+	is true.
+
+maintenance.<task>.schedule::
+	This config option controls whether or not the given `<task>` runs
+	during a `git maintenance run --schedule=<frequency>` command. The
+	value must be one of "hourly", "daily", or "weekly".
+
+maintenance.commit-graph.auto::
+	This integer config option controls how often the `commit-graph` task
+	should be run as part of `git maintenance run --auto`. If zero, then
+	the `commit-graph` task will not run with the `--auto` option. A
+	negative value will force the task to run every time. Otherwise, a
+	positive value implies the command should run when the number of
+	reachable commits that are not in the commit-graph file is at least
+	the value of `maintenance.commit-graph.auto`. The default value is
+	100.
+
+maintenance.loose-objects.auto::
+	This integer config option controls how often the `loose-objects` task
+	should be run as part of `git maintenance run --auto`. If zero, then
+	the `loose-objects` task will not run with the `--auto` option. A
+	negative value will force the task to run every time. Otherwise, a
+	positive value implies the command should run when the number of
+	loose objects is at least the value of `maintenance.loose-objects.auto`.
+	The default value is 100.
+
+maintenance.incremental-repack.auto::
+	This integer config option controls how often the `incremental-repack`
+	task should be run as part of `git maintenance run --auto`. If zero,
+	then the `incremental-repack` task will not run with the `--auto`
+	option. A negative value will force the task to run every time.
+	Otherwise, a positive value implies the command should run when the
+	number of pack-files not in the multi-pack-index is at least the value
+	of `maintenance.incremental-repack.auto`. The default value is 10.
+
+
+
+GIT
+---
+Part of the linkgit:git[1] suite
diff --git a/external/docs/asciidoc/8ce83a5e94562ab0e73c88ef4afd41ae6d2296a7 b/external/docs/asciidoc/8ce83a5e94562ab0e73c88ef4afd41ae6d2296a7
new file mode 100644
index 0000000000..80838fe37e
--- /dev/null
+++ b/external/docs/asciidoc/8ce83a5e94562ab0e73c88ef4afd41ae6d2296a7
@@ -0,0 +1,328 @@
+--[no-]all::
+	Fetch all remotes, except for the ones that has the
+	`remote.<name>.skipFetchAll` configuration variable set.
+	This overrides the configuration variable fetch.all`.
+
+-a::
+--append::
+	Append ref names and object names of fetched refs to the
+	existing contents of `.git/FETCH_HEAD`.  Without this
+	option old data in `.git/FETCH_HEAD` will be overwritten.
+
+--atomic::
+	Use an atomic transaction to update local refs. Either all refs are
+	updated, or on error, no refs are updated.
+
+--depth=<depth>::
+	Limit fetching to the specified number of commits from the tip of
+	each remote branch history. If fetching to a 'shallow' repository
+	created by `git clone` with `--depth=<depth>` option (see
+	linkgit:git-clone[1]), deepen or shorten the history to the specified
+	number of commits. Tags for the deepened commits are not fetched.
+
+--deepen=<depth>::
+	Similar to --depth, except it specifies the number of commits
+	from the current shallow boundary instead of from the tip of
+	each remote branch history.
+
+--shallow-since=<date>::
+	Deepen or shorten the history of a shallow repository to
+	include all reachable commits after <date>.
+
+--shallow-exclude=<revision>::
+	Deepen or shorten the history of a shallow repository to
+	exclude commits reachable from a specified remote branch or tag.
+	This option can be specified multiple times.
+
+--unshallow::
+	If the source repository is complete, convert a shallow
+	repository to a complete one, removing all the limitations
+	imposed by shallow repositories.
++
+If the source repository is shallow, fetch as much as possible so that
+the current repository has the same history as the source repository.
+
+--update-shallow::
+	By default when fetching from a shallow repository,
+	`git fetch` refuses refs that require updating
+	.git/shallow. This option updates .git/shallow and accepts such
+	refs.
+
+--negotiation-tip=<commit|glob>::
+	By default, Git will report, to the server, commits reachable
+	from all local refs to find common commits in an attempt to
+	reduce the size of the to-be-received packfile. If specified,
+	Git will only report commits reachable from the given tips.
+	This is useful to speed up fetches when the user knows which
+	local ref is likely to have commits in common with the
+	upstream ref being fetched.
++
+This option may be specified more than once; if so, Git will report
+commits reachable from any of the given commits.
++
+The argument to this option may be a glob on ref names, a ref, or the (possibly
+abbreviated) SHA-1 of a commit. Specifying a glob is equivalent to specifying
+this option multiple times, one for each matching ref name.
++
+See also the `fetch.negotiationAlgorithm` and `push.negotiate`
+configuration variables documented in linkgit:git-config[1], and the
+`--negotiate-only` option below.
+
+--negotiate-only::
+	Do not fetch anything from the server, and instead print the
+	ancestors of the provided `--negotiation-tip=*` arguments,
+	which we have in common with the server.
++
+This is incompatible with `--recurse-submodules=[yes|on-demand]`.
+Internally this is used to implement the `push.negotiate` option, see
+linkgit:git-config[1].
+
+--dry-run::
+	Show what would be done, without making any changes.
+
+--porcelain::
+	Print the output to standard output in an easy-to-parse format for
+	scripts. See section OUTPUT in linkgit:git-fetch[1] for details.
++
+This is incompatible with `--recurse-submodules=[yes|on-demand]` and takes
+precedence over the `fetch.output` config option.
+
+ifndef::git-pull[]
+--[no-]write-fetch-head::
+	Write the list of remote refs fetched in the `FETCH_HEAD`
+	file directly under `$GIT_DIR`.  This is the default.
+	Passing `--no-write-fetch-head` from the command line tells
+	Git not to write the file.  Under `--dry-run` option, the
+	file is never written.
+endif::git-pull[]
+
+-f::
+--force::
+	When 'git fetch' is used with `<src>:<dst>` refspec, it may
+	refuse to update the local branch as discussed
+ifdef::git-pull[]
+	in the `<refspec>` part of the linkgit:git-fetch[1]
+	documentation.
+endif::git-pull[]
+ifndef::git-pull[]
+	in the `<refspec>` part below.
+endif::git-pull[]
+	This option overrides that check.
+
+-k::
+--keep::
+	Keep downloaded pack.
+
+ifndef::git-pull[]
+--multiple::
+	Allow several <repository> and <group> arguments to be
+	specified. No <refspec>s may be specified.
+
+--[no-]auto-maintenance::
+--[no-]auto-gc::
+	Run `git maintenance run --auto` at the end to perform automatic
+	repository maintenance if needed. (`--[no-]auto-gc` is a synonym.)
+	This is enabled by default.
+
+--[no-]write-commit-graph::
+	Write a commit-graph after fetching. This overrides the config
+	setting `fetch.writeCommitGraph`.
+endif::git-pull[]
+
+--prefetch::
+	Modify the configured refspec to place all refs into the
+	`refs/prefetch/` namespace. See the `prefetch` task in
+	linkgit:git-maintenance[1].
+
+-p::
+--prune::
+	Before fetching, remove any remote-tracking references that no
+	longer exist on the remote.  Tags are not subject to pruning
+	if they are fetched only because of the default tag
+	auto-following or due to a --tags option.  However, if tags
+	are fetched due to an explicit refspec (either on the command
+	line or in the remote configuration, for example if the remote
+	was cloned with the --mirror option), then they are also
+	subject to pruning. Supplying `--prune-tags` is a shorthand for
+	providing the tag refspec.
+ifndef::git-pull[]
++
+See the PRUNING section below for more details.
+
+-P::
+--prune-tags::
+	Before fetching, remove any local tags that no longer exist on
+	the remote if `--prune` is enabled. This option should be used
+	more carefully, unlike `--prune` it will remove any local
+	references (local tags) that have been created. This option is
+	a shorthand for providing the explicit tag refspec along with
+	`--prune`, see the discussion about that in its documentation.
++
+See the PRUNING section below for more details.
+
+endif::git-pull[]
+
+ifndef::git-pull[]
+-n::
+endif::git-pull[]
+--no-tags::
+	By default, tags that point at objects that are downloaded
+	from the remote repository are fetched and stored locally.
+	This option disables this automatic tag following. The default
+	behavior for a remote may be specified with the remote.<name>.tagOpt
+	setting. See linkgit:git-config[1].
+
+ifndef::git-pull[]
+--refetch::
+	Instead of negotiating with the server to avoid transferring commits and
+	associated objects that are already present locally, this option fetches
+	all objects as a fresh clone would. Use this to reapply a partial clone
+	filter from configuration or using `--filter=` when the filter
+	definition has changed. Automatic post-fetch maintenance will perform
+	object database pack consolidation to remove any duplicate objects.
+endif::git-pull[]
+
+--refmap=<refspec>::
+	When fetching refs listed on the command line, use the
+	specified refspec (can be given more than once) to map the
+	refs to remote-tracking branches, instead of the values of
+	`remote.*.fetch` configuration variables for the remote
+	repository.  Providing an empty `<refspec>` to the
+	`--refmap` option causes Git to ignore the configured
+	refspecs and rely entirely on the refspecs supplied as
+	command-line arguments. See section on "Configured Remote-tracking
+	Branches" for details.
+
+-t::
+--tags::
+	Fetch all tags from the remote (i.e., fetch remote tags
+	`refs/tags/*` into local tags with the same name), in addition
+	to whatever else would otherwise be fetched.  Using this
+	option alone does not subject tags to pruning, even if --prune
+	is used (though tags may be pruned anyway if they are also the
+	destination of an explicit refspec; see `--prune`).
+
+ifndef::git-pull[]
+--recurse-submodules[=(yes|on-demand|no)]::
+	This option controls if and under what conditions new commits of
+	submodules should be fetched too. When recursing through submodules,
+	`git fetch` always attempts to fetch "changed" submodules, that is, a
+	submodule that has commits that are referenced by a newly fetched
+	superproject commit but are missing in the local submodule clone. A
+	changed submodule can be fetched as long as it is present locally e.g.
+	in `$GIT_DIR/modules/` (see linkgit:gitsubmodules[7]); if the upstream
+	adds a new submodule, that submodule cannot be fetched until it is
+	cloned e.g. by `git submodule update`.
++
+When set to 'on-demand', only changed submodules are fetched. When set
+to 'yes', all populated submodules are fetched and submodules that are
+both unpopulated and changed are fetched. When set to 'no', submodules
+are never fetched.
++
+When unspecified, this uses the value of `fetch.recurseSubmodules` if it
+is set (see linkgit:git-config[1]), defaulting to 'on-demand' if unset.
+When this option is used without any value, it defaults to 'yes'.
+endif::git-pull[]
+
+-j::
+--jobs=<n>::
+	Number of parallel children to be used for all forms of fetching.
++
+If the `--multiple` option was specified, the different remotes will be fetched
+in parallel. If multiple submodules are fetched, they will be fetched in
+parallel. To control them independently, use the config settings
+`fetch.parallel` and `submodule.fetchJobs` (see linkgit:git-config[1]).
++
+Typically, parallel recursive and multi-remote fetches will be faster. By
+default fetches are performed sequentially, not in parallel.
+
+ifndef::git-pull[]
+--no-recurse-submodules::
+	Disable recursive fetching of submodules (this has the same effect as
+	using the `--recurse-submodules=no` option).
+endif::git-pull[]
+
+--set-upstream::
+	If the remote is fetched successfully, add upstream
+	(tracking) reference, used by argument-less
+	linkgit:git-pull[1] and other commands. For more information,
+	see `branch.<name>.merge` and `branch.<name>.remote` in
+	linkgit:git-config[1].
+
+ifndef::git-pull[]
+--submodule-prefix=<path>::
+	Prepend <path> to paths printed in informative messages
+	such as "Fetching submodule foo".  This option is used
+	internally when recursing over submodules.
+
+--recurse-submodules-default=[yes|on-demand]::
+	This option is used internally to temporarily provide a
+	non-negative default value for the --recurse-submodules
+	option.  All other methods of configuring fetch's submodule
+	recursion (such as settings in linkgit:gitmodules[5] and
+	linkgit:git-config[1]) override this option, as does
+	specifying --[no-]recurse-submodules directly.
+
+-u::
+--update-head-ok::
+	By default 'git fetch' refuses to update the head which
+	corresponds to the current branch.  This flag disables the
+	check.  This is purely for the internal use for 'git pull'
+	to communicate with 'git fetch', and unless you are
+	implementing your own Porcelain you are not supposed to
+	use it.
+endif::git-pull[]
+
+--upload-pack <upload-pack>::
+	When given, and the repository to fetch from is handled
+	by 'git fetch-pack', `--exec=<upload-pack>` is passed to
+	the command to specify non-default path for the command
+	run on the other end.
+
+ifndef::git-pull[]
+-q::
+--quiet::
+	Pass --quiet to git-fetch-pack and silence any other internally
+	used git commands. Progress is not reported to the standard error
+	stream.
+
+-v::
+--verbose::
+	Be verbose.
+endif::git-pull[]
+
+--progress::
+	Progress status is reported on the standard error stream
+	by default when it is attached to a terminal, unless -q
+	is specified. This flag forces progress status even if the
+	standard error stream is not directed to a terminal.
+
+-o <option>::
+--server-option=<option>::
+	Transmit the given string to the server when communicating using
+	protocol version 2.  The given string must not contain a NUL or LF
+	character.  The server's handling of server options, including
+	unknown ones, is server-specific.
+	When multiple `--server-option=<option>` are given, they are all
+	sent to the other side in the order listed on the command line.
+
+--show-forced-updates::
+	By default, git checks if a branch is force-updated during
+	fetch. This can be disabled through fetch.showForcedUpdates, but
+	the --show-forced-updates option guarantees this check occurs.
+	See linkgit:git-config[1].
+
+--no-show-forced-updates::
+	By default, git checks if a branch is force-updated during
+	fetch. Pass --no-show-forced-updates or set fetch.showForcedUpdates
+	to false to skip this check for performance reasons. If used during
+	'git-pull' the --ff-only option will still check for forced updates
+	before attempting a fast-forward update. See linkgit:git-config[1].
+
+-4::
+--ipv4::
+	Use IPv4 addresses only, ignoring IPv6 addresses.
+
+-6::
+--ipv6::
+	Use IPv6 addresses only, ignoring IPv4 addresses.
diff --git a/external/docs/asciidoc/a13f478d7cb3fc25a95f0e14cff73cd5203e4b57 b/external/docs/asciidoc/a13f478d7cb3fc25a95f0e14cff73cd5203e4b57
new file mode 100644
index 0000000000..5fcd57fd26
--- /dev/null
+++ b/external/docs/asciidoc/a13f478d7cb3fc25a95f0e14cff73cd5203e4b57
@@ -0,0 +1,1131 @@
+git-fetch(1)
+============
+
+NAME
+----
+git-fetch - Download objects and refs from another repository
+
+
+SYNOPSIS
+--------
+[verse]
+'git fetch' [<options>] [<repository> [<refspec>...]]
+'git fetch' [<options>] <group>
+'git fetch' --multiple [<options>] [(<repository> | <group>)...]
+'git fetch' --all [<options>]
+
+
+DESCRIPTION
+-----------
+Fetch branches and/or tags (collectively, "refs") from one or more
+other repositories, along with the objects necessary to complete their
+histories.  Remote-tracking branches are updated (see the description
+of <refspec> below for ways to control this behavior).
+
+By default, any tag that points into the histories being fetched is
+also fetched; the effect is to fetch tags that
+point at branches that you are interested in.  This default behavior
+can be changed by using the --tags or --no-tags options or by
+configuring remote.<name>.tagOpt.  By using a refspec that fetches tags
+explicitly, you can fetch tags that do not point into branches you
+are interested in as well.
+
+'git fetch' can fetch from either a single named repository or URL,
+or from several repositories at once if <group> is given and
+there is a remotes.<group> entry in the configuration file.
+(See linkgit:git-config[1]).
+
+When no remote is specified, by default the `origin` remote will be used,
+unless there's an upstream branch configured for the current branch.
+
+The names of refs that are fetched, together with the object names
+they point at, are written to `.git/FETCH_HEAD`.  This information
+may be used by scripts or other git commands, such as linkgit:git-pull[1].
+
+OPTIONS
+-------
+--[no-]all::
+	Fetch all remotes, except for the ones that has the
+	`remote.<name>.skipFetchAll` configuration variable set.
+	This overrides the configuration variable fetch.all`.
+
+-a::
+--append::
+	Append ref names and object names of fetched refs to the
+	existing contents of `.git/FETCH_HEAD`.  Without this
+	option old data in `.git/FETCH_HEAD` will be overwritten.
+
+--atomic::
+	Use an atomic transaction to update local refs. Either all refs are
+	updated, or on error, no refs are updated.
+
+--depth=<depth>::
+	Limit fetching to the specified number of commits from the tip of
+	each remote branch history. If fetching to a 'shallow' repository
+	created by `git clone` with `--depth=<depth>` option (see
+	linkgit:git-clone[1]), deepen or shorten the history to the specified
+	number of commits. Tags for the deepened commits are not fetched.
+
+--deepen=<depth>::
+	Similar to --depth, except it specifies the number of commits
+	from the current shallow boundary instead of from the tip of
+	each remote branch history.
+
+--shallow-since=<date>::
+	Deepen or shorten the history of a shallow repository to
+	include all reachable commits after <date>.
+
+--shallow-exclude=<revision>::
+	Deepen or shorten the history of a shallow repository to
+	exclude commits reachable from a specified remote branch or tag.
+	This option can be specified multiple times.
+
+--unshallow::
+	If the source repository is complete, convert a shallow
+	repository to a complete one, removing all the limitations
+	imposed by shallow repositories.
++
+If the source repository is shallow, fetch as much as possible so that
+the current repository has the same history as the source repository.
+
+--update-shallow::
+	By default when fetching from a shallow repository,
+	`git fetch` refuses refs that require updating
+	.git/shallow. This option updates .git/shallow and accepts such
+	refs.
+
+--negotiation-tip=<commit|glob>::
+	By default, Git will report, to the server, commits reachable
+	from all local refs to find common commits in an attempt to
+	reduce the size of the to-be-received packfile. If specified,
+	Git will only report commits reachable from the given tips.
+	This is useful to speed up fetches when the user knows which
+	local ref is likely to have commits in common with the
+	upstream ref being fetched.
++
+This option may be specified more than once; if so, Git will report
+commits reachable from any of the given commits.
++
+The argument to this option may be a glob on ref names, a ref, or the (possibly
+abbreviated) SHA-1 of a commit. Specifying a glob is equivalent to specifying
+this option multiple times, one for each matching ref name.
++
+See also the `fetch.negotiationAlgorithm` and `push.negotiate`
+configuration variables documented in linkgit:git-config[1], and the
+`--negotiate-only` option below.
+
+--negotiate-only::
+	Do not fetch anything from the server, and instead print the
+	ancestors of the provided `--negotiation-tip=*` arguments,
+	which we have in common with the server.
++
+This is incompatible with `--recurse-submodules=[yes|on-demand]`.
+Internally this is used to implement the `push.negotiate` option, see
+linkgit:git-config[1].
+
+--dry-run::
+	Show what would be done, without making any changes.
+
+--porcelain::
+	Print the output to standard output in an easy-to-parse format for
+	scripts. See section OUTPUT in linkgit:git-fetch[1] for details.
++
+This is incompatible with `--recurse-submodules=[yes|on-demand]` and takes
+precedence over the `fetch.output` config option.
+
+ifndef::git-pull[]
+--[no-]write-fetch-head::
+	Write the list of remote refs fetched in the `FETCH_HEAD`
+	file directly under `$GIT_DIR`.  This is the default.
+	Passing `--no-write-fetch-head` from the command line tells
+	Git not to write the file.  Under `--dry-run` option, the
+	file is never written.
+endif::git-pull[]
+
+-f::
+--force::
+	When 'git fetch' is used with `<src>:<dst>` refspec, it may
+	refuse to update the local branch as discussed
+ifdef::git-pull[]
+	in the `<refspec>` part of the linkgit:git-fetch[1]
+	documentation.
+endif::git-pull[]
+ifndef::git-pull[]
+	in the `<refspec>` part below.
+endif::git-pull[]
+	This option overrides that check.
+
+-k::
+--keep::
+	Keep downloaded pack.
+
+ifndef::git-pull[]
+--multiple::
+	Allow several <repository> and <group> arguments to be
+	specified. No <refspec>s may be specified.
+
+--[no-]auto-maintenance::
+--[no-]auto-gc::
+	Run `git maintenance run --auto` at the end to perform automatic
+	repository maintenance if needed. (`--[no-]auto-gc` is a synonym.)
+	This is enabled by default.
+
+--[no-]write-commit-graph::
+	Write a commit-graph after fetching. This overrides the config
+	setting `fetch.writeCommitGraph`.
+endif::git-pull[]
+
+--prefetch::
+	Modify the configured refspec to place all refs into the
+	`refs/prefetch/` namespace. See the `prefetch` task in
+	linkgit:git-maintenance[1].
+
+-p::
+--prune::
+	Before fetching, remove any remote-tracking references that no
+	longer exist on the remote.  Tags are not subject to pruning
+	if they are fetched only because of the default tag
+	auto-following or due to a --tags option.  However, if tags
+	are fetched due to an explicit refspec (either on the command
+	line or in the remote configuration, for example if the remote
+	was cloned with the --mirror option), then they are also
+	subject to pruning. Supplying `--prune-tags` is a shorthand for
+	providing the tag refspec.
+ifndef::git-pull[]
++
+See the PRUNING section below for more details.
+
+-P::
+--prune-tags::
+	Before fetching, remove any local tags that no longer exist on
+	the remote if `--prune` is enabled. This option should be used
+	more carefully, unlike `--prune` it will remove any local
+	references (local tags) that have been created. This option is
+	a shorthand for providing the explicit tag refspec along with
+	`--prune`, see the discussion about that in its documentation.
++
+See the PRUNING section below for more details.
+
+endif::git-pull[]
+
+ifndef::git-pull[]
+-n::
+endif::git-pull[]
+--no-tags::
+	By default, tags that point at objects that are downloaded
+	from the remote repository are fetched and stored locally.
+	This option disables this automatic tag following. The default
+	behavior for a remote may be specified with the remote.<name>.tagOpt
+	setting. See linkgit:git-config[1].
+
+ifndef::git-pull[]
+--refetch::
+	Instead of negotiating with the server to avoid transferring commits and
+	associated objects that are already present locally, this option fetches
+	all objects as a fresh clone would. Use this to reapply a partial clone
+	filter from configuration or using `--filter=` when the filter
+	definition has changed. Automatic post-fetch maintenance will perform
+	object database pack consolidation to remove any duplicate objects.
+endif::git-pull[]
+
+--refmap=<refspec>::
+	When fetching refs listed on the command line, use the
+	specified refspec (can be given more than once) to map the
+	refs to remote-tracking branches, instead of the values of
+	`remote.*.fetch` configuration variables for the remote
+	repository.  Providing an empty `<refspec>` to the
+	`--refmap` option causes Git to ignore the configured
+	refspecs and rely entirely on the refspecs supplied as
+	command-line arguments. See section on "Configured Remote-tracking
+	Branches" for details.
+
+-t::
+--tags::
+	Fetch all tags from the remote (i.e., fetch remote tags
+	`refs/tags/*` into local tags with the same name), in addition
+	to whatever else would otherwise be fetched.  Using this
+	option alone does not subject tags to pruning, even if --prune
+	is used (though tags may be pruned anyway if they are also the
+	destination of an explicit refspec; see `--prune`).
+
+ifndef::git-pull[]
+--recurse-submodules[=(yes|on-demand|no)]::
+	This option controls if and under what conditions new commits of
+	submodules should be fetched too. When recursing through submodules,
+	`git fetch` always attempts to fetch "changed" submodules, that is, a
+	submodule that has commits that are referenced by a newly fetched
+	superproject commit but are missing in the local submodule clone. A
+	changed submodule can be fetched as long as it is present locally e.g.
+	in `$GIT_DIR/modules/` (see linkgit:gitsubmodules[7]); if the upstream
+	adds a new submodule, that submodule cannot be fetched until it is
+	cloned e.g. by `git submodule update`.
++
+When set to 'on-demand', only changed submodules are fetched. When set
+to 'yes', all populated submodules are fetched and submodules that are
+both unpopulated and changed are fetched. When set to 'no', submodules
+are never fetched.
++
+When unspecified, this uses the value of `fetch.recurseSubmodules` if it
+is set (see linkgit:git-config[1]), defaulting to 'on-demand' if unset.
+When this option is used without any value, it defaults to 'yes'.
+endif::git-pull[]
+
+-j::
+--jobs=<n>::
+	Number of parallel children to be used for all forms of fetching.
++
+If the `--multiple` option was specified, the different remotes will be fetched
+in parallel. If multiple submodules are fetched, they will be fetched in
+parallel. To control them independently, use the config settings
+`fetch.parallel` and `submodule.fetchJobs` (see linkgit:git-config[1]).
++
+Typically, parallel recursive and multi-remote fetches will be faster. By
+default fetches are performed sequentially, not in parallel.
+
+ifndef::git-pull[]
+--no-recurse-submodules::
+	Disable recursive fetching of submodules (this has the same effect as
+	using the `--recurse-submodules=no` option).
+endif::git-pull[]
+
+--set-upstream::
+	If the remote is fetched successfully, add upstream
+	(tracking) reference, used by argument-less
+	linkgit:git-pull[1] and other commands. For more information,
+	see `branch.<name>.merge` and `branch.<name>.remote` in
+	linkgit:git-config[1].
+
+ifndef::git-pull[]
+--submodule-prefix=<path>::
+	Prepend <path> to paths printed in informative messages
+	such as "Fetching submodule foo".  This option is used
+	internally when recursing over submodules.
+
+--recurse-submodules-default=[yes|on-demand]::
+	This option is used internally to temporarily provide a
+	non-negative default value for the --recurse-submodules
+	option.  All other methods of configuring fetch's submodule
+	recursion (such as settings in linkgit:gitmodules[5] and
+	linkgit:git-config[1]) override this option, as does
+	specifying --[no-]recurse-submodules directly.
+
+-u::
+--update-head-ok::
+	By default 'git fetch' refuses to update the head which
+	corresponds to the current branch.  This flag disables the
+	check.  This is purely for the internal use for 'git pull'
+	to communicate with 'git fetch', and unless you are
+	implementing your own Porcelain you are not supposed to
+	use it.
+endif::git-pull[]
+
+--upload-pack <upload-pack>::
+	When given, and the repository to fetch from is handled
+	by 'git fetch-pack', `--exec=<upload-pack>` is passed to
+	the command to specify non-default path for the command
+	run on the other end.
+
+ifndef::git-pull[]
+-q::
+--quiet::
+	Pass --quiet to git-fetch-pack and silence any other internally
+	used git commands. Progress is not reported to the standard error
+	stream.
+
+-v::
+--verbose::
+	Be verbose.
+endif::git-pull[]
+
+--progress::
+	Progress status is reported on the standard error stream
+	by default when it is attached to a terminal, unless -q
+	is specified. This flag forces progress status even if the
+	standard error stream is not directed to a terminal.
+
+-o <option>::
+--server-option=<option>::
+	Transmit the given string to the server when communicating using
+	protocol version 2.  The given string must not contain a NUL or LF
+	character.  The server's handling of server options, including
+	unknown ones, is server-specific.
+	When multiple `--server-option=<option>` are given, they are all
+	sent to the other side in the order listed on the command line.
+
+--show-forced-updates::
+	By default, git checks if a branch is force-updated during
+	fetch. This can be disabled through fetch.showForcedUpdates, but
+	the --show-forced-updates option guarantees this check occurs.
+	See linkgit:git-config[1].
+
+--no-show-forced-updates::
+	By default, git checks if a branch is force-updated during
+	fetch. Pass --no-show-forced-updates or set fetch.showForcedUpdates
+	to false to skip this check for performance reasons. If used during
+	'git-pull' the --ff-only option will still check for forced updates
+	before attempting a fast-forward update. See linkgit:git-config[1].
+
+-4::
+--ipv4::
+	Use IPv4 addresses only, ignoring IPv6 addresses.
+
+-6::
+--ipv6::
+	Use IPv6 addresses only, ignoring IPv4 addresses.
+
+
+<repository>::
+	The "remote" repository that is the source of a fetch
+	or pull operation.  This parameter can be either a URL
+	(see the section <<URLS,GIT URLS>> below) or the name
+	of a remote (see the section <<REMOTES,REMOTES>> below).
+
+ifndef::git-pull[]
+<group>::
+	A name referring to a list of repositories as the value
+	of remotes.<group> in the configuration file.
+	(See linkgit:git-config[1]).
+endif::git-pull[]
+
+<refspec>::
+	Specifies which refs to fetch and which local refs to update.
+	When no <refspec>s appear on the command line, the refs to fetch
+	are read from `remote.<repository>.fetch` variables instead
+ifndef::git-pull[]
+	(see <<CRTB,CONFIGURED REMOTE-TRACKING BRANCHES>> below).
+endif::git-pull[]
+ifdef::git-pull[]
+	(see the section "CONFIGURED REMOTE-TRACKING BRANCHES"
+	in linkgit:git-fetch[1]).
+endif::git-pull[]
++
+The format of a <refspec> parameter is an optional plus
+`+`, followed by the source <src>, followed
+by a colon `:`, followed by the destination ref <dst>.
+The colon can be omitted when <dst> is empty.  <src> is
+typically a ref, but it can also be a fully spelled hex object
+name.
++
+A <refspec> may contain a `*` in its <src> to indicate a simple pattern
+match. Such a refspec functions like a glob that matches any ref with the
+same prefix. A pattern <refspec> must have a `*` in both the <src> and
+<dst>. It will map refs to the destination by replacing the `*` with the
+contents matched from the source.
++
+If a refspec is prefixed by `^`, it will be interpreted as a negative
+refspec. Rather than specifying which refs to fetch or which local refs to
+update, such a refspec will instead specify refs to exclude. A ref will be
+considered to match if it matches at least one positive refspec, and does
+not match any negative refspec. Negative refspecs can be useful to restrict
+the scope of a pattern refspec so that it will not include specific refs.
+Negative refspecs can themselves be pattern refspecs. However, they may only
+contain a <src> and do not specify a <dst>. Fully spelled out hex object
+names are also not supported.
++
+`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`;
+it requests fetching everything up to the given tag.
++
+The remote ref that matches <src>
+is fetched, and if <dst> is not an empty string, an attempt
+is made to update the local ref that matches it.
++
+Whether that update is allowed without `--force` depends on the ref
+namespace it's being fetched to, the type of object being fetched, and
+whether the update is considered to be a fast-forward. Generally, the
+same rules apply for fetching as when pushing, see the `<refspec>...`
+section of linkgit:git-push[1] for what those are. Exceptions to those
+rules particular to 'git fetch' are noted below.
++
+Until Git version 2.20, and unlike when pushing with
+linkgit:git-push[1], any updates to `refs/tags/*` would be accepted
+without `+` in the refspec (or `--force`). When fetching, we promiscuously
+considered all tag updates from a remote to be forced fetches.  Since
+Git version 2.20, fetching to update `refs/tags/*` works the same way
+as when pushing. I.e. any updates will be rejected without `+` in the
+refspec (or `--force`).
++
+Unlike when pushing with linkgit:git-push[1], any updates outside of
+`refs/{tags,heads}/*` will be accepted without `+` in the refspec (or
+`--force`), whether that's swapping e.g. a tree object for a blob, or
+a commit for another commit that doesn't have the previous commit as
+an ancestor etc.
++
+Unlike when pushing with linkgit:git-push[1], there is no
+configuration which'll amend these rules, and nothing like a
+`pre-fetch` hook analogous to the `pre-receive` hook.
++
+As with pushing with linkgit:git-push[1], all of the rules described
+above about what's not allowed as an update can be overridden by
+adding an optional leading `+` to a refspec (or using the `--force`
+command line option). The only exception to this is that no amount of
+forcing will make the `refs/heads/*` namespace accept a non-commit
+object.
++
+[NOTE]
+When the remote branch you want to fetch is known to
+be rewound and rebased regularly, it is expected that
+its new tip will not be a descendant of its previous tip
+(as stored in your remote-tracking branch the last time
+you fetched).  You would want
+to use the `+` sign to indicate non-fast-forward updates
+will be needed for such branches.  There is no way to
+determine or declare that a branch will be made available
+in a repository with this behavior; the pulling user simply
+must know this is the expected usage pattern for a branch.
+ifdef::git-pull[]
++
+[NOTE]
+There is a difference between listing multiple <refspec>
+directly on 'git pull' command line and having multiple
+`remote.<repository>.fetch` entries in your configuration
+for a <repository> and running a
+'git pull' command without any explicit <refspec> parameters.
+<refspec>s listed explicitly on the command line are always
+merged into the current branch after fetching.  In other words,
+if you list more than one remote ref, 'git pull' will create
+an Octopus merge.  On the other hand, if you do not list any
+explicit <refspec> parameter on the command line, 'git pull'
+will fetch all the <refspec>s it finds in the
+`remote.<repository>.fetch` configuration and merge
+only the first <refspec> found into the current branch.
+This is because making an
+Octopus from remote refs is rarely done, while keeping track
+of multiple remote heads in one-go by fetching more than one
+is often useful.
+endif::git-pull[]
+
+
+--stdin::
+	Read refspecs, one per line, from stdin in addition to those provided
+	as arguments. The "tag <name>" format is not supported.
+
+GIT URLS[[URLS]]
+----------------
+
+In general, URLs contain information about the transport protocol, the
+address of the remote server, and the path to the repository.
+Depending on the transport protocol, some of this information may be
+absent.
+
+Git supports ssh, git, http, and https protocols (in addition, ftp
+and ftps can be used for fetching, but this is inefficient and
+deprecated; do not use them).
+
+The native transport (i.e. git:// URL) does no authentication and
+should be used with caution on unsecured networks.
+
+The following syntaxes may be used with them:
+
+- ++ssh://++{startsb}__<user>__++@++{endsb}__<host>__{startsb}++:++__<port>__{endsb}++/++__<path-to-git-repo>__
+- ++git://++__<host>__{startsb}:__<port>__{endsb}++/++__<path-to-git-repo>__
+- ++http++{startsb}++s++{endsb}++://++__<host>__{startsb}++:++__<port>__{endsb}++/++__<path-to-git-repo>__
+- ++ftp++{startsb}++s++{endsb}++://++__<host>__{startsb}++:++__<port>__{endsb}++/++__<path-to-git-repo>__
+
+An alternative scp-like syntax may also be used with the ssh protocol:
+
+- {startsb}__<user>__++@++{endsb}__<host>__++:/++__<path-to-git-repo>__
+
+This syntax is only recognized if there are no slashes before the
+first colon. This helps differentiate a local path that contains a
+colon. For example the local path `foo:bar` could be specified as an
+absolute path or `./foo:bar` to avoid being misinterpreted as an ssh
+url.
+
+The ssh and git protocols additionally support ++~++__<username>__ expansion:
+
+- ++ssh://++{startsb}__<user>__++@++{endsb}__<host>__{startsb}++:++__<port>__{endsb}++/~++__<user>__++/++__<path-to-git-repo>__
+- ++git://++__<host>__{startsb}++:++__<port>__{endsb}++/~++__<user>__++/++__<path-to-git-repo>__
+- {startsb}__<user>__++@++{endsb}__<host>__++:~++__<user>__++/++__<path-to-git-repo>__
+
+For local repositories, also supported by Git natively, the following
+syntaxes may be used:
+
+- `/path/to/repo.git/`
+- ++file:///path/to/repo.git/++
+
+ifndef::git-clone[]
+These two syntaxes are mostly equivalent, except when cloning, when
+the former implies `--local` option. See linkgit:git-clone[1] for
+details.
+endif::git-clone[]
+
+ifdef::git-clone[]
+These two syntaxes are mostly equivalent, except the former implies
+`--local` option.
+endif::git-clone[]
+
+`git clone`, `git fetch` and `git pull`, but not `git push`, will also
+accept a suitable bundle file. See linkgit:git-bundle[1].
+
+When Git doesn't know how to handle a certain transport protocol, it
+attempts to use the `remote-`{empty}__<transport>__ remote helper, if one
+exists. To explicitly request a remote helper, the following syntax
+may be used:
+
+- _<transport>_::__<address>__
+
+where _<address>_ may be a path, a server and path, or an arbitrary
+URL-like string recognized by the specific remote helper being
+invoked. See linkgit:gitremote-helpers[7] for details.
+
+If there are a large number of similarly-named remote repositories and
+you want to use a different format for them (such that the URLs you
+use will be rewritten into URLs that work), you can create a
+configuration section of the form:
+
+[verse]
+--
+	[url "__<actual-url-base>__"]
+		insteadOf = _<other-url-base>_
+--
+
+For example, with this:
+
+------------
+	[url "git://git.host.xz/"]
+		insteadOf = host.xz:/path/to/
+		insteadOf = work:
+------------
+
+a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
+rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".
+
+If you want to rewrite URLs for push only, you can create a
+configuration section of the form:
+
+[verse]
+--
+	[url "__<actual-url-base>__"]
+		pushInsteadOf = _<other-url-base>_
+--
+
+For example, with this:
+
+------------
+	[url "ssh://example.org/"]
+		pushInsteadOf = git://example.org/
+------------
+
+a URL like "git://example.org/path/to/repo.git" will be rewritten to
+"ssh://example.org/path/to/repo.git" for pushes, but pulls will still
+use the original URL.
+
+
+REMOTES[[REMOTES]]
+------------------
+
+The name of one of the following can be used instead
+of a URL as `<repository>` argument:
+
+* a remote in the Git configuration file: `$GIT_DIR/config`,
+* a file in the `$GIT_DIR/remotes` directory, or
+* a file in the `$GIT_DIR/branches` directory.
+
+All of these also allow you to omit the refspec from the command line
+because they each contain a refspec which git will use by default.
+
+Named remote in configuration file
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can choose to provide the name of a remote which you had previously
+configured using linkgit:git-remote[1], linkgit:git-config[1]
+or even by a manual edit to the `$GIT_DIR/config` file.  The URL of
+this remote will be used to access the repository.  The refspec
+of this remote will be used by default when you do
+not provide a refspec on the command line.  The entry in the
+config file would appear like this:
+
+------------
+	[remote "<name>"]
+		url = <URL>
+		pushurl = <pushurl>
+		push = <refspec>
+		fetch = <refspec>
+------------
+
+The `<pushurl>` is used for pushes only. It is optional and defaults
+to `<URL>`. Pushing to a remote affects all defined pushurls or all
+defined urls if no pushurls are defined. Fetch, however, will only
+fetch from the first defined url if multiple urls are defined.
+
+Named file in `$GIT_DIR/remotes`
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can choose to provide the name of a
+file in `$GIT_DIR/remotes`.  The URL
+in this file will be used to access the repository.  The refspec
+in this file will be used as default when you do not
+provide a refspec on the command line.  This file should have the
+following format:
+
+------------
+	URL: one of the above URL formats
+	Push: <refspec>
+	Pull: <refspec>
+
+------------
+
+`Push:` lines are used by 'git push' and
+`Pull:` lines are used by 'git pull' and 'git fetch'.
+Multiple `Push:` and `Pull:` lines may
+be specified for additional branch mappings.
+
+Named file in `$GIT_DIR/branches`
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can choose to provide the name of a
+file in `$GIT_DIR/branches`.
+The URL in this file will be used to access the repository.
+This file should have the following format:
+
+
+------------
+	<URL>#<head>
+------------
+
+`<URL>` is required; `#<head>` is optional.
+
+Depending on the operation, git will use one of the following
+refspecs, if you don't provide one on the command line.
+`<branch>` is the name of this file in `$GIT_DIR/branches` and
+`<head>` defaults to `master`.
+
+git fetch uses:
+
+------------
+	refs/heads/<head>:refs/heads/<branch>
+------------
+
+git push uses:
+
+------------
+	HEAD:refs/heads/<head>
+------------
+
+
+
+
+
+
+
+CONFIGURED REMOTE-TRACKING BRANCHES[[CRTB]]
+-------------------------------------------
+
+You often interact with the same remote repository by
+regularly and repeatedly fetching from it.  In order to keep track
+of the progress of such a remote repository, `git fetch` allows you
+to configure `remote.<repository>.fetch` configuration variables.
+
+Typically such a variable may look like this:
+
+------------------------------------------------
+[remote "origin"]
+	fetch = +refs/heads/*:refs/remotes/origin/*
+------------------------------------------------
+
+This configuration is used in two ways:
+
+* When `git fetch` is run without specifying what branches
+  and/or tags to fetch on the command line, e.g. `git fetch origin`
+  or `git fetch`, `remote.<repository>.fetch` values are used as
+  the refspecs--they specify which refs to fetch and which local refs
+  to update.  The example above will fetch
+  all branches that exist in the `origin` (i.e. any ref that matches
+  the left-hand side of the value, `refs/heads/*`) and update the
+  corresponding remote-tracking branches in the `refs/remotes/origin/*`
+  hierarchy.
+
+* When `git fetch` is run with explicit branches and/or tags
+  to fetch on the command line, e.g. `git fetch origin master`, the
+  <refspec>s given on the command line determine what are to be
+  fetched (e.g. `master` in the example,
+  which is a short-hand for `master:`, which in turn means
+  "fetch the 'master' branch but I do not explicitly say what
+  remote-tracking branch to update with it from the command line"),
+  and the example command will
+  fetch _only_ the 'master' branch.  The `remote.<repository>.fetch`
+  values determine which
+  remote-tracking branch, if any, is updated.  When used in this
+  way, the `remote.<repository>.fetch` values do not have any
+  effect in deciding _what_ gets fetched (i.e. the values are not
+  used as refspecs when the command-line lists refspecs); they are
+  only used to decide _where_ the refs that are fetched are stored
+  by acting as a mapping.
+
+The latter use of the `remote.<repository>.fetch` values can be
+overridden by giving the `--refmap=<refspec>` parameter(s) on the
+command line.
+
+PRUNING
+-------
+
+Git has a default disposition of keeping data unless it's explicitly
+thrown away; this extends to holding onto local references to branches
+on remotes that have themselves deleted those branches.
+
+If left to accumulate, these stale references might make performance
+worse on big and busy repos that have a lot of branch churn, and
+e.g. make the output of commands like `git branch -a --contains
+<commit>` needlessly verbose, as well as impacting anything else
+that'll work with the complete set of known references.
+
+These remote-tracking references can be deleted as a one-off with
+either of:
+
+------------------------------------------------
+# While fetching
+$ git fetch --prune <name>
+
+# Only prune, don't fetch
+$ git remote prune <name>
+------------------------------------------------
+
+To prune references as part of your normal workflow without needing to
+remember to run that, set `fetch.prune` globally, or
+`remote.<name>.prune` per-remote in the config. See
+linkgit:git-config[1].
+
+Here's where things get tricky and more specific. The pruning feature
+doesn't actually care about branches, instead it'll prune local <-->
+remote-references as a function of the refspec of the remote (see
+`<refspec>` and <<CRTB,CONFIGURED REMOTE-TRACKING BRANCHES>> above).
+
+Therefore if the refspec for the remote includes
+e.g. `refs/tags/*:refs/tags/*`, or you manually run e.g. `git fetch
+--prune <name> "refs/tags/*:refs/tags/*"` it won't be stale remote
+tracking branches that are deleted, but any local tag that doesn't
+exist on the remote.
+
+This might not be what you expect, i.e. you want to prune remote
+`<name>`, but also explicitly fetch tags from it, so when you fetch
+from it you delete all your local tags, most of which may not have
+come from the `<name>` remote in the first place.
+
+So be careful when using this with a refspec like
+`refs/tags/*:refs/tags/*`, or any other refspec which might map
+references from multiple remotes to the same local namespace.
+
+Since keeping up-to-date with both branches and tags on the remote is
+a common use-case the `--prune-tags` option can be supplied along with
+`--prune` to prune local tags that don't exist on the remote, and
+force-update those tags that differ. Tag pruning can also be enabled
+with `fetch.pruneTags` or `remote.<name>.pruneTags` in the config. See
+linkgit:git-config[1].
+
+The `--prune-tags` option is equivalent to having
+`refs/tags/*:refs/tags/*` declared in the refspecs of the remote. This
+can lead to some seemingly strange interactions:
+
+------------------------------------------------
+# These both fetch tags
+$ git fetch --no-tags origin 'refs/tags/*:refs/tags/*'
+$ git fetch --no-tags --prune-tags origin
+------------------------------------------------
+
+The reason it doesn't error out when provided without `--prune` or its
+config versions is for flexibility of the configured versions, and to
+maintain a 1=1 mapping between what the command line flags do, and
+what the configuration versions do.
+
+It's reasonable to e.g. configure `fetch.pruneTags=true` in
+`~/.gitconfig` to have tags pruned whenever `git fetch --prune` is
+run, without making every invocation of `git fetch` without `--prune`
+an error.
+
+Pruning tags with `--prune-tags` also works when fetching a URL
+instead of a named remote. These will all prune tags not found on
+origin:
+
+------------------------------------------------
+$ git fetch origin --prune --prune-tags
+$ git fetch origin --prune 'refs/tags/*:refs/tags/*'
+$ git fetch <url-of-origin> --prune --prune-tags
+$ git fetch <url-of-origin> --prune 'refs/tags/*:refs/tags/*'
+------------------------------------------------
+
+OUTPUT
+------
+
+The output of "git fetch" depends on the transport method used; this
+section describes the output when fetching over the Git protocol
+(either locally or via ssh) and Smart HTTP protocol.
+
+The status of the fetch is output in tabular form, with each line
+representing the status of a single ref. Each line is of the form:
+
+-------------------------------
+ <flag> <summary> <from> -> <to> [<reason>]
+-------------------------------
+
+When using `--porcelain`, the output format is intended to be
+machine-parseable. In contrast to the human-readable output formats it
+thus prints to standard output instead of standard error. Each line is
+of the form:
+
+-------------------------------
+<flag> <old-object-id> <new-object-id> <local-reference>
+-------------------------------
+
+The status of up-to-date refs is shown only if the --verbose option is
+used.
+
+In compact output mode, specified with configuration variable
+fetch.output, if either entire `<from>` or `<to>` is found in the
+other string, it will be substituted with `*` in the other string. For
+example, `master -> origin/master` becomes `master -> origin/*`.
+
+flag::
+	A single character indicating the status of the ref:
+(space);; for a successfully fetched fast-forward;
+`+`;; for a successful forced update;
+`-`;; for a successfully pruned ref;
+`t`;; for a successful tag update;
+`*`;; for a successfully fetched new ref;
+`!`;; for a ref that was rejected or failed to update; and
+`=`;; for a ref that was up to date and did not need fetching.
+
+summary::
+	For a successfully fetched ref, the summary shows the old and new
+	values of the ref in a form suitable for using as an argument to
+	`git log` (this is `<old>..<new>` in most cases, and
+	`<old>...<new>` for forced non-fast-forward updates).
+
+from::
+	The name of the remote ref being fetched from, minus its
+	`refs/<type>/` prefix. In the case of deletion, the name of
+	the remote ref is "(none)".
+
+to::
+	The name of the local ref being updated, minus its
+	`refs/<type>/` prefix.
+
+reason::
+	A human-readable explanation. In the case of successfully fetched
+	refs, no explanation is needed. For a failed ref, the reason for
+	failure is described.
+
+EXAMPLES
+--------
+
+* Update the remote-tracking branches:
++
+------------------------------------------------
+$ git fetch origin
+------------------------------------------------
++
+The above command copies all branches from the remote `refs/heads/`
+namespace and stores them to the local `refs/remotes/origin/` namespace,
+unless the `remote.<repository>.fetch` option is used to specify a
+non-default refspec.
+
+* Using refspecs explicitly:
++
+------------------------------------------------
+$ git fetch origin +seen:seen maint:tmp
+------------------------------------------------
++
+This updates (or creates, as necessary) branches `seen` and `tmp` in
+the local repository by fetching from the branches (respectively)
+`seen` and `maint` from the remote repository.
++
+The `seen` branch will be updated even if it does not fast-forward,
+because it is prefixed with a plus sign; `tmp` will not be.
+
+* Peek at a remote's branch, without configuring the remote in your local
+  repository:
++
+------------------------------------------------
+$ git fetch git://git.kernel.org/pub/scm/git/git.git maint
+$ git log FETCH_HEAD
+------------------------------------------------
++
+The first command fetches the `maint` branch from the repository at
+`git://git.kernel.org/pub/scm/git/git.git` and the second command uses
+`FETCH_HEAD` to examine the branch with linkgit:git-log[1].  The fetched
+objects will eventually be removed by git's built-in housekeeping (see
+linkgit:git-gc[1]).
+
+SECURITY
+--------
+The fetch and push protocols are not designed to prevent one side from
+stealing data from the other repository that was not intended to be
+shared. If you have private data that you need to protect from a malicious
+peer, your best option is to store it in another repository. This applies
+to both clients and servers. In particular, namespaces on a server are not
+effective for read access control; you should only grant read access to a
+namespace to clients that you would trust with read access to the entire
+repository.
+
+The known attack vectors are as follows:
+
+. The victim sends "have" lines advertising the IDs of objects it has that
+  are not explicitly intended to be shared but can be used to optimize the
+  transfer if the peer also has them. The attacker chooses an object ID X
+  to steal and sends a ref to X, but isn't required to send the content of
+  X because the victim already has it. Now the victim believes that the
+  attacker has X, and it sends the content of X back to the attacker
+  later. (This attack is most straightforward for a client to perform on a
+  server, by creating a ref to X in the namespace the client has access
+  to and then fetching it. The most likely way for a server to perform it
+  on a client is to "merge" X into a public branch and hope that the user
+  does additional work on this branch and pushes it back to the server
+  without noticing the merge.)
+
+. As in #1, the attacker chooses an object ID X to steal. The victim sends
+  an object Y that the attacker already has, and the attacker falsely
+  claims to have X and not Y, so the victim sends Y as a delta against X.
+  The delta reveals regions of X that are similar to Y to the attacker.
+
+
+CONFIGURATION
+-------------
+
+Everything below this line in this section is selectively included
+from the linkgit:git-config[1] documentation. The content is the same
+as what's found there:
+
+
+fetch.recurseSubmodules::
+	This option controls whether `git fetch` (and the underlying fetch
+	in `git pull`) will recursively fetch into populated submodules.
+	This option can be set either to a boolean value or to 'on-demand'.
+	Setting it to a boolean changes the behavior of fetch and pull to
+	recurse unconditionally into submodules when set to true or to not
+	recurse at all when set to false. When set to 'on-demand', fetch and
+	pull will only recurse into a populated submodule when its
+	superproject retrieves a commit that updates the submodule's
+	reference.
+	Defaults to 'on-demand', or to the value of 'submodule.recurse' if set.
+
+fetch.fsckObjects::
+	If it is set to true, git-fetch-pack will check all fetched
+	objects. See `transfer.fsckObjects` for what's
+	checked. Defaults to false. If not set, the value of
+	`transfer.fsckObjects` is used instead.
+
+fetch.fsck.<msg-id>::
+	Acts like `fsck.<msg-id>`, but is used by
+	linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See
+	the `fsck.<msg-id>` documentation for details.
+
+fetch.fsck.skipList::
+	Acts like `fsck.skipList`, but is used by
+	linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See
+	the `fsck.skipList` documentation for details.
+
+fetch.unpackLimit::
+	If the number of objects fetched over the Git native
+	transfer is below this
+	limit, then the objects will be unpacked into loose object
+	files. However if the number of received objects equals or
+	exceeds this limit then the received pack will be stored as
+	a pack, after adding any missing delta bases.  Storing the
+	pack from a push can make the push operation complete faster,
+	especially on slow filesystems.  If not set, the value of
+	`transfer.unpackLimit` is used instead.
+
+fetch.prune::
+	If true, fetch will automatically behave as if the `--prune`
+	option was given on the command line.  See also `remote.<name>.prune`
+	and the PRUNING section of linkgit:git-fetch[1].
+
+fetch.pruneTags::
+	If true, fetch will automatically behave as if the
+	`refs/tags/*:refs/tags/*` refspec was provided when pruning,
+	if not set already. This allows for setting both this option
+	and `fetch.prune` to maintain a 1=1 mapping to upstream
+	refs. See also `remote.<name>.pruneTags` and the PRUNING
+	section of linkgit:git-fetch[1].
+
+fetch.all::
+	If true, fetch will attempt to update all available remotes.
+	This behavior can be overridden by passing `--no-all` or by
+	explicitly specifying one or more remote(s) to fetch from.
+	Defaults to false.
+
+fetch.output::
+	Control how ref update status is printed. Valid values are
+	`full` and `compact`. Default value is `full`. See the
+	OUTPUT section in linkgit:git-fetch[1] for details.
+
+fetch.negotiationAlgorithm::
+	Control how information about the commits in the local repository
+	is sent when negotiating the contents of the packfile to be sent by
+	the server.  Set to "consecutive" to use an algorithm that walks
+	over consecutive commits checking each one.  Set to "skipping" to
+	use an algorithm that skips commits in an effort to converge
+	faster, but may result in a larger-than-necessary packfile; or set
+	to "noop" to not send any information at all, which will almost
+	certainly result in a larger-than-necessary packfile, but will skip
+	the negotiation step.  Set to "default" to override settings made
+	previously and use the default behaviour.  The default is normally
+	"consecutive", but if `feature.experimental` is true, then the
+	default is "skipping".  Unknown values will cause 'git fetch' to
+	error out.
++
+See also the `--negotiate-only` and `--negotiation-tip` options to
+linkgit:git-fetch[1].
+
+fetch.showForcedUpdates::
+	Set to false to enable `--no-show-forced-updates` in
+	linkgit:git-fetch[1] and linkgit:git-pull[1] commands.
+	Defaults to true.
+
+fetch.parallel::
+	Specifies the maximal number of fetch operations to be run in parallel
+	at a time (submodules, or remotes when the `--multiple` option of
+	linkgit:git-fetch[1] is in effect).
++
+A value of 0 will give some reasonable default. If unset, it defaults to 1.
++
+For submodules, this setting can be overridden using the `submodule.fetchJobs`
+config setting.
+
+fetch.writeCommitGraph::
+	Set to true to write a commit-graph after every `git fetch` command
+	that downloads a pack-file from a remote. Using the `--split` option,
+	most executions will create a very small commit-graph file on top of
+	the existing commit-graph file(s). Occasionally, these files will
+	merge and the write may take longer. Having an updated commit-graph
+	file helps performance of many Git commands, including `git merge-base`,
+	`git push -f`, and `git log --graph`. Defaults to false.
+
+fetch.bundleURI::
+	This value stores a URI for downloading Git object data from a bundle
+	URI before performing an incremental fetch from the origin Git server.
+	This is similar to how the `--bundle-uri` option behaves in
+	linkgit:git-clone[1]. `git clone --bundle-uri` will set the
+	`fetch.bundleURI` value if the supplied bundle URI contains a bundle
+	list that is organized for incremental fetches.
++
+If you modify this value and your repository has a `fetch.bundleCreationToken`
+value, then remove that `fetch.bundleCreationToken` value before fetching from
+the new bundle URI.
+
+fetch.bundleCreationToken::
+	When using `fetch.bundleURI` to fetch incrementally from a bundle
+	list that uses the "creationToken" heuristic, this config value
+	stores the maximum `creationToken` value of the downloaded bundles.
+	This value is used to prevent downloading bundles in the future
+	if the advertised `creationToken` is not strictly larger than this
+	value.
++
+The creation token values are chosen by the provider serving the specific
+bundle URI. If you modify the URI at `fetch.bundleURI`, then be sure to
+remove the value for the `fetch.bundleCreationToken` value before fetching.
+
+
+BUGS
+----
+Using --recurse-submodules can only fetch new commits in submodules that are
+present locally e.g. in `$GIT_DIR/modules/`. If the upstream adds a new
+submodule, that submodule cannot be fetched until it is cloned e.g. by `git
+submodule update`. This is expected to be fixed in a future Git version.
+
+SEE ALSO
+--------
+linkgit:git-pull[1]
+
+GIT
+---
+Part of the linkgit:git[1] suite
diff --git a/external/docs/asciidoc/b6eb1ed05504fc766aabc581c310057c6a46f010 b/external/docs/asciidoc/b6eb1ed05504fc766aabc581c310057c6a46f010
new file mode 100644
index 0000000000..4582cf69ad
--- /dev/null
+++ b/external/docs/asciidoc/b6eb1ed05504fc766aabc581c310057c6a46f010
@@ -0,0 +1,7022 @@
+git-config(1)
+=============
+
+NAME
+----
+git-config - Get and set repository or global options
+
+
+SYNOPSIS
+--------
+[verse]
+'git config list' [<file-option>] [<display-option>] [--includes]
+'git config get' [<file-option>] [<display-option>] [--includes] [--all] [--regexp] [--value=<value>] [--fixed-value] [--default=<default>] <name>
+'git config set' [<file-option>] [--type=<type>] [--all] [--value=<value>] [--fixed-value] <name> <value>
+'git config unset' [<file-option>] [--all] [--value=<value>] [--fixed-value] <name> <value>
+'git config rename-section' [<file-option>] <old-name> <new-name>
+'git config remove-section' [<file-option>] <name>
+'git config edit' [<file-option>]
+'git config' [<file-option>] --get-colorbool <name> [<stdout-is-tty>]
+
+DESCRIPTION
+-----------
+You can query/set/replace/unset options with this command. The name is
+actually the section and the key separated by a dot, and the value will be
+escaped.
+
+Multiple lines can be added to an option by using the `--append` option.
+If you want to update or unset an option which can occur on multiple
+lines, a `value-pattern` (which is an extended regular expression,
+unless the `--fixed-value` option is given) needs to be given.  Only the
+existing values that match the pattern are updated or unset.  If
+you want to handle the lines that do *not* match the pattern, just
+prepend a single exclamation mark in front (see also <<EXAMPLES>>),
+but note that this only works when the `--fixed-value` option is not
+in use.
+
+The `--type=<type>` option instructs 'git config' to ensure that incoming and
+outgoing values are canonicalize-able under the given <type>.  If no
+`--type=<type>` is given, no canonicalization will be performed. Callers may
+unset an existing `--type` specifier with `--no-type`.
+
+When reading, the values are read from the system, global and
+repository local configuration files by default, and options
+`--system`, `--global`, `--local`, `--worktree` and
+`--file <filename>` can be used to tell the command to read from only
+that location (see <<FILES>>).
+
+When writing, the new value is written to the repository local
+configuration file by default, and options `--system`, `--global`,
+`--worktree`, `--file <filename>` can be used to tell the command to
+write to that location (you can say `--local` but that is the
+default).
+
+This command will fail with non-zero status upon error.  Some exit
+codes are:
+
+- The section or key is invalid (ret=1),
+- no section or name was provided (ret=2),
+- the config file is invalid (ret=3),
+- the config file cannot be written (ret=4),
+- you try to unset an option which does not exist (ret=5),
+- you try to unset/set an option for which multiple lines match (ret=5), or
+- you try to use an invalid regexp (ret=6).
+
+On success, the command returns the exit code 0.
+
+A list of all available configuration variables can be obtained using the
+`git help --config` command.
+
+COMMANDS
+--------
+
+list::
+	List all variables set in config file, along with their values.
+
+get::
+	Emits the value of the specified key. If key is present multiple times
+	in the configuration, emits the last value. If `--all` is specified,
+	emits all values associated with key. Returns error code 1 if key is
+	not present.
+
+set::
+	Set value for one or more config options. By default, this command
+	refuses to write multi-valued config options. Passing `--all` will
+	replace all multi-valued config options with the new value, whereas
+	`--value=` will replace all config options whose values match the given
+	pattern.
+
+unset::
+	Unset value for one or more config options. By default, this command
+	refuses to unset multi-valued keys. Passing `--all` will unset all
+	multi-valued config options, whereas `--value` will unset all config
+	options whose values match the given pattern.
+
+rename-section::
+	Rename the given section to a new name.
+
+remove-section::
+	Remove the given section from the configuration file.
+
+edit::
+	Opens an editor to modify the specified config file; either
+	`--system`, `--global`, `--local` (default), `--worktree`, or
+	`--file <config-file>`.
+
+[[OPTIONS]]
+OPTIONS
+-------
+
+--replace-all::
+	Default behavior is to replace at most one line. This replaces
+	all lines matching the key (and optionally the `value-pattern`).
+
+--append::
+	Adds a new line to the option without altering any existing
+	values. This is the same as providing '--value=^$' in `set`.
+
+--comment <message>::
+	Append a comment at the end of new or modified lines.
+
+	If _<message>_ begins with one or more whitespaces followed
+	by "#", it is used as-is.  If it begins with "#", a space is
+	prepended before it is used.  Otherwise, a string " # " (a
+	space followed by a hash followed by a space) is prepended
+	to it.  And the resulting string is placed immediately after
+	the value defined for the variable.  The _<message>_ must
+	not contain linefeed characters (no multi-line comments are
+	permitted).
+
+--all::
+	With `get`, return all values for a multi-valued key.
+
+--regexp::
+	With `get`, interpret the name as a regular expression. Regular
+	expression matching is currently case-sensitive and done against a
+	canonicalized version of the key in which section and variable names
+	are lowercased, but subsection names are not.
+
+--url=<URL>::
+	When given a two-part <name> as <section>.<key>, the value for
+	<section>.<URL>.<key> whose <URL> part matches the best to the
+	given URL is returned (if no such key exists, the value for
+	<section>.<key> is used as a fallback).  When given just the
+	<section> as name, do so for all the keys in the section and
+	list them.  Returns error code 1 if no value is found.
+
+--global::
+	For writing options: write to global `~/.gitconfig` file
+	rather than the repository `.git/config`, write to
+	`$XDG_CONFIG_HOME/git/config` file if this file exists and the
+	`~/.gitconfig` file doesn't.
++
+For reading options: read only from global `~/.gitconfig` and from
+`$XDG_CONFIG_HOME/git/config` rather than from all available files.
++
+See also <<FILES>>.
+
+--system::
+	For writing options: write to system-wide
+	`$(prefix)/etc/gitconfig` rather than the repository
+	`.git/config`.
++
+For reading options: read only from system-wide `$(prefix)/etc/gitconfig`
+rather than from all available files.
++
+See also <<FILES>>.
+
+--local::
+	For writing options: write to the repository `.git/config` file.
+	This is the default behavior.
++
+For reading options: read only from the repository `.git/config` rather than
+from all available files.
++
+See also <<FILES>>.
+
+--worktree::
+	Similar to `--local` except that `$GIT_DIR/config.worktree` is
+	read from or written to if `extensions.worktreeConfig` is
+	enabled. If not it's the same as `--local`. Note that `$GIT_DIR`
+	is equal to `$GIT_COMMON_DIR` for the main working tree, but is of
+	the form `$GIT_DIR/worktrees/<id>/` for other working trees. See
+	linkgit:git-worktree[1] to learn how to enable
+	`extensions.worktreeConfig`.
+
+-f <config-file>::
+--file <config-file>::
+	For writing options: write to the specified file rather than the
+	repository `.git/config`.
++
+For reading options: read only from the specified file rather than from all
+available files.
++
+See also <<FILES>>.
+
+--blob <blob>::
+	Similar to `--file` but use the given blob instead of a file. E.g.
+	you can use 'master:.gitmodules' to read values from the file
+	'.gitmodules' in the master branch. See "SPECIFYING REVISIONS"
+	section in linkgit:gitrevisions[7] for a more complete list of
+	ways to spell blob names.
+
+--fixed-value::
+	When used with the `value-pattern` argument, treat `value-pattern` as
+	an exact string instead of a regular expression. This will restrict
+	the name/value pairs that are matched to only those where the value
+	is exactly equal to the `value-pattern`.
+
+--type <type>::
+  'git config' will ensure that any input or output is valid under the given
+  type constraint(s), and will canonicalize outgoing values in `<type>`'s
+  canonical form.
++
+Valid `<type>`'s include:
++
+- 'bool': canonicalize values as either "true" or "false".
+- 'int': canonicalize values as simple decimal numbers. An optional suffix of
+  'k', 'm', or 'g' will cause the value to be multiplied by 1024, 1048576, or
+  1073741824 upon input.
+- 'bool-or-int': canonicalize according to either 'bool' or 'int', as described
+  above.
+- 'path': canonicalize by expanding a leading `~` to the value of `$HOME` and
+  `~user` to the home directory for the specified user. This specifier has no
+  effect when setting the value (but you can use `git config section.variable
+  ~/` from the command line to let your shell do the expansion.)
+- 'expiry-date': canonicalize by converting from a fixed or relative date-string
+  to a timestamp. This specifier has no effect when setting the value.
+- 'color': When getting a value, canonicalize by converting to an ANSI color
+  escape sequence. When setting a value, a sanity-check is performed to ensure
+  that the given value is canonicalize-able as an ANSI color, but it is written
+  as-is.
++
+
+--bool::
+--int::
+--bool-or-int::
+--path::
+--expiry-date::
+  Historical options for selecting a type specifier. Prefer instead `--type`
+  (see above).
+
+--no-type::
+  Un-sets the previously set type specifier (if one was previously set). This
+  option requests that 'git config' not canonicalize the retrieved variable.
+  `--no-type` has no effect without `--type=<type>` or `--<type>`.
+
+-z::
+--null::
+	For all options that output values and/or keys, always
+	end values with the null character (instead of a
+	newline). Use newline instead as a delimiter between
+	key and value. This allows for secure parsing of the
+	output without getting confused e.g. by values that
+	contain line breaks.
+
+--name-only::
+	Output only the names of config variables for `list` or
+	`get`.
+
+--show-origin::
+	Augment the output of all queried config options with the
+	origin type (file, standard input, blob, command line) and
+	the actual origin (config file path, ref, or blob id if
+	applicable).
+
+--show-scope::
+	Similar to `--show-origin` in that it augments the output of
+	all queried config options with the scope of that value
+	(worktree, local, global, system, command).
+
+--get-colorbool <name> [<stdout-is-tty>]::
+
+	Find the color setting for `<name>` (e.g. `color.diff`) and output
+	"true" or "false".  `<stdout-is-tty>` should be either "true" or
+	"false", and is taken into account when configuration says
+	"auto".  If `<stdout-is-tty>` is missing, then checks the standard
+	output of the command itself, and exits with status 0 if color
+	is to be used, or exits with status 1 otherwise.
+	When the color setting for `name` is undefined, the command uses
+	`color.ui` as fallback.
+
+--[no-]includes::
+	Respect `include.*` directives in config files when looking up
+	values. Defaults to `off` when a specific file is given (e.g.,
+	using `--file`, `--global`, etc) and `on` when searching all
+	config files.
+
+--default <value>::
+  When using `get`, and the requested variable is not found, behave as if
+  <value> were the value assigned to that variable.
+
+DEPRECATED MODES
+----------------
+
+The following modes have been deprecated in favor of subcommands. It is
+recommended to migrate to the new syntax.
+
+'git config <name>'::
+	Replaced by `git config get <name>`.
+
+'git config <name> <value> [<value-pattern>]'::
+	Replaced by `git config set [--value=<pattern>] <name> <value>`.
+
+-l::
+--list::
+	Replaced by `git config list`.
+
+--get <name> [<value-pattern>]::
+	Replaced by `git config get [--value=<pattern>] <name>`.
+
+--get-all <name> [<value-pattern>]::
+	Replaced by `git config get [--value=<pattern>] --all <name>`.
+
+--get-regexp <name-regexp>::
+	Replaced by `git config get --all --show-names --regexp <name-regexp>`.
+
+--get-urlmatch <name> <URL>::
+	Replaced by `git config get --all --show-names --url=<URL> <name>`.
+
+--get-color <name> [<default>]::
+	Replaced by `git config get --type=color [--default=<default>] <name>`.
+
+--add <name> <value>::
+	Replaced by `git config set --append <name> <value>`.
+
+--unset <name> [<value-pattern>]::
+	Replaced by `git config unset [--value=<pattern>] <name>`.
+
+--unset-all <name> [<value-pattern>]::
+	Replaced by `git config unset [--value=<pattern>] --all <name>`.
+
+--rename-section <old-name> <new-name>::
+	Replaced by `git config rename-section <old-name> <new-name>`.
+
+--remove-section <name>::
+	Replaced by `git config remove-section <name>`.
+
+-e::
+--edit::
+	Replaced by `git config edit`.
+
+CONFIGURATION
+-------------
+`pager.config` is only respected when listing configuration, i.e., when
+using `list` or `get` which may return multiple results. The default is to use
+a pager.
+
+[[FILES]]
+FILES
+-----
+
+By default, 'git config' will read configuration options from multiple
+files:
+
+$(prefix)/etc/gitconfig::
+	System-wide configuration file.
+
+$XDG_CONFIG_HOME/git/config::
+~/.gitconfig::
+	User-specific configuration files. When the XDG_CONFIG_HOME environment
+	variable is not set or empty, $HOME/.config/ is used as
+	$XDG_CONFIG_HOME.
++
+These are also called "global" configuration files. If both files exist, both
+files are read in the order given above.
+
+$GIT_DIR/config::
+	Repository specific configuration file.
+
+$GIT_DIR/config.worktree::
+	This is optional and is only searched when
+	`extensions.worktreeConfig` is present in $GIT_DIR/config.
+
+You may also provide additional configuration parameters when running any
+git command by using the `-c` option. See linkgit:git[1] for details.
+
+Options will be read from all of these files that are available. If the
+global or the system-wide configuration files are missing or unreadable they
+will be ignored. If the repository configuration file is missing or unreadable,
+'git config' will exit with a non-zero error code. An error message is produced
+if the file is unreadable, but not if it is missing.
+
+The files are read in the order given above, with last value found taking
+precedence over values read earlier.  When multiple values are taken then all
+values of a key from all files will be used.
+
+By default, options are only written to the repository specific
+configuration file. Note that this also affects options like `set`
+and `unset`. *'git config' will only ever change one file at a time*.
+
+You can limit which configuration sources are read from or written to by
+specifying the path of a file with the `--file` option, or by specifying a
+configuration scope with `--system`, `--global`, `--local`, or `--worktree`.
+For more, see <<OPTIONS>> above.
+
+[[SCOPES]]
+SCOPES
+------
+
+Each configuration source falls within a configuration scope. The scopes
+are:
+
+system::
+	$(prefix)/etc/gitconfig
+
+global::
+	$XDG_CONFIG_HOME/git/config
++
+~/.gitconfig
+
+local::
+	$GIT_DIR/config
+
+worktree::
+	$GIT_DIR/config.worktree
+
+command::
+	GIT_CONFIG_{COUNT,KEY,VALUE} environment variables (see <<ENVIRONMENT>>
+	below)
++
+the `-c` option
+
+With the exception of 'command', each scope corresponds to a command line
+option: `--system`, `--global`, `--local`, `--worktree`.
+
+When reading options, specifying a scope will only read options from the
+files within that scope. When writing options, specifying a scope will write
+to the files within that scope (instead of the repository specific
+configuration file). See <<OPTIONS>> above for a complete description.
+
+Most configuration options are respected regardless of the scope it is
+defined in, but some options are only respected in certain scopes. See the
+respective option's documentation for the full details.
+
+Protected configuration
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Protected configuration refers to the 'system', 'global', and 'command' scopes.
+For security reasons, certain options are only respected when they are
+specified in protected configuration, and ignored otherwise.
+
+Git treats these scopes as if they are controlled by the user or a trusted
+administrator. This is because an attacker who controls these scopes can do
+substantial harm without using Git, so it is assumed that the user's environment
+protects these scopes against attackers.
+
+[[ENVIRONMENT]]
+ENVIRONMENT
+-----------
+
+GIT_CONFIG_GLOBAL::
+GIT_CONFIG_SYSTEM::
+	Take the configuration from the given files instead from global or
+	system-level configuration. See linkgit:git[1] for details.
+
+GIT_CONFIG_NOSYSTEM::
+	Whether to skip reading settings from the system-wide
+	$(prefix)/etc/gitconfig file. See linkgit:git[1] for details.
+
+See also <<FILES>>.
+
+GIT_CONFIG_COUNT::
+GIT_CONFIG_KEY_<n>::
+GIT_CONFIG_VALUE_<n>::
+	If GIT_CONFIG_COUNT is set to a positive number, all environment pairs
+	GIT_CONFIG_KEY_<n> and GIT_CONFIG_VALUE_<n> up to that number will be
+	added to the process's runtime configuration. The config pairs are
+	zero-indexed. Any missing key or value is treated as an error. An empty
+	GIT_CONFIG_COUNT is treated the same as GIT_CONFIG_COUNT=0, namely no
+	pairs are processed. These environment variables will override values
+	in configuration files, but will be overridden by any explicit options
+	passed via `git -c`.
++
+This is useful for cases where you want to spawn multiple git commands
+with a common configuration but cannot depend on a configuration file,
+for example when writing scripts.
+
+GIT_CONFIG::
+	If no `--file` option is provided to `git config`, use the file
+	given by `GIT_CONFIG` as if it were provided via `--file`. This
+	variable has no effect on other Git commands, and is mostly for
+	historical compatibility; there is generally no reason to use it
+	instead of the `--file` option.
+
+[[EXAMPLES]]
+EXAMPLES
+--------
+
+Given a .git/config like this:
+
+------------
+#
+# This is the config file, and
+# a '#' or ';' character indicates
+# a comment
+#
+
+; core variables
+[core]
+	; Don't trust file modes
+	filemode = false
+
+; Our diff algorithm
+[diff]
+	external = /usr/local/bin/diff-wrapper
+	renames = true
+
+; Proxy settings
+[core]
+	gitproxy=proxy-command for kernel.org
+	gitproxy=default-proxy ; for all the rest
+
+; HTTP
+[http]
+	sslVerify
+[http "https://weak.example.com"]
+	sslVerify = false
+	cookieFile = /tmp/cookie.txt
+------------
+
+you can set the filemode to true with
+
+------------
+% git config set core.filemode true
+------------
+
+The hypothetical proxy command entries actually have a postfix to discern
+what URL they apply to. Here is how to change the entry for kernel.org
+to "ssh".
+
+------------
+% git config set --value='for kernel.org$' core.gitproxy '"ssh" for kernel.org'
+------------
+
+This makes sure that only the key/value pair for kernel.org is replaced.
+
+To delete the entry for renames, do
+
+------------
+% git config unset diff.renames
+------------
+
+If you want to delete an entry for a multivar (like core.gitproxy above),
+you have to provide a regex matching the value of exactly one line.
+
+To query the value for a given key, do
+
+------------
+% git config get core.filemode
+------------
+
+or, to query a multivar:
+
+------------
+% git config get --value="for kernel.org$" core.gitproxy
+------------
+
+If you want to know all the values for a multivar, do:
+
+------------
+% git config get --all --show-names core.gitproxy
+------------
+
+If you like to live dangerously, you can replace *all* core.gitproxy by a
+new one with
+
+------------
+% git config set --all core.gitproxy ssh
+------------
+
+However, if you really only want to replace the line for the default proxy,
+i.e. the one without a "for ..." postfix, do something like this:
+
+------------
+% git config set --value='! for ' core.gitproxy ssh
+------------
+
+To actually match only values with an exclamation mark, you have to
+
+------------
+% git config set --value='[!]' section.key value
+------------
+
+To add a new proxy, without altering any of the existing ones, use
+
+------------
+% git config set --append core.gitproxy '"proxy-command" for example.com'
+------------
+
+An example to use customized color from the configuration in your
+script:
+
+------------
+#!/bin/sh
+WS=$(git config get --type=color --default="blue reverse" color.diff.whitespace)
+RESET=$(git config get --type=color --default="reset" "")
+echo "${WS}your whitespace color or blue reverse${RESET}"
+------------
+
+For URLs in `https://weak.example.com`, `http.sslVerify` is set to
+false, while it is set to `true` for all others:
+
+------------
+% git config get --type=bool --url=https://good.example.com http.sslverify
+true
+% git config get --type=bool --url=https://weak.example.com http.sslverify
+false
+% git config get --url=https://weak.example.com http
+http.cookieFile /tmp/cookie.txt
+http.sslverify false
+------------
+
+CONFIGURATION FILE
+------------------
+
+The Git configuration file contains a number of variables that affect
+the Git commands' behavior. The files `.git/config` and optionally
+`config.worktree` (see the "CONFIGURATION FILE" section of
+linkgit:git-worktree[1]) in each repository are used to store the
+configuration for that repository, and `$HOME/.gitconfig` is used to
+store a per-user configuration as fallback values for the `.git/config`
+file. The file `/etc/gitconfig` can be used to store a system-wide
+default configuration.
+
+The configuration variables are used by both the Git plumbing
+and the porcelain commands. The variables are divided into sections, wherein
+the fully qualified variable name of the variable itself is the last
+dot-separated segment and the section name is everything before the last
+dot. The variable names are case-insensitive, allow only alphanumeric
+characters and `-`, and must start with an alphabetic character.  Some
+variables may appear multiple times; we say then that the variable is
+multivalued.
+
+Syntax
+~~~~~~
+
+The syntax is fairly flexible and permissive.  Whitespace characters,
+which in this context are the space character (SP) and the horizontal
+tabulation (HT), are mostly ignored.  The '#' and ';' characters begin
+comments to the end of line.  Blank lines are ignored.
+
+The file consists of sections and variables.  A section begins with
+the name of the section in square brackets and continues until the next
+section begins.  Section names are case-insensitive.  Only alphanumeric
+characters, `-` and `.` are allowed in section names.  Each variable
+must belong to some section, which means that there must be a section
+header before the first setting of a variable.
+
+Sections can be further divided into subsections.  To begin a subsection
+put its name in double quotes, separated by space from the section name,
+in the section header, like in the example below:
+
+--------
+	[section "subsection"]
+
+--------
+
+Subsection names are case sensitive and can contain any characters except
+newline and the null byte. Doublequote `"` and backslash can be included
+by escaping them as `\"` and `\\`, respectively. Backslashes preceding
+other characters are dropped when reading; for example, `\t` is read as
+`t` and `\0` is read as `0`. Section headers cannot span multiple lines.
+Variables may belong directly to a section or to a given subsection. You
+can have `[section]` if you have `[section "subsection"]`, but you don't
+need to.
+
+There is also a deprecated `[section.subsection]` syntax. With this
+syntax, the subsection name is converted to lower-case and is also
+compared case sensitively. These subsection names follow the same
+restrictions as section names.
+
+All the other lines (and the remainder of the line after the section
+header) are recognized as setting variables, in the form
+'name = value' (or just 'name', which is a short-hand to say that
+the variable is the boolean "true").
+The variable names are case-insensitive, allow only alphanumeric characters
+and `-`, and must start with an alphabetic character.
+
+Whitespace characters surrounding `name`, `=` and `value` are discarded.
+Internal whitespace characters within 'value' are retained verbatim.
+Comments starting with either `#` or `;` and extending to the end of line
+are discarded.  A line that defines a value can be continued to the next
+line by ending it with a backslash (`\`);  the backslash and the end-of-line
+characters are discarded.
+
+If `value` needs to contain leading or trailing whitespace characters,
+it must be enclosed in double quotation marks (`"`).  Inside double quotation
+marks, double quote (`"`) and backslash (`\`) characters must be escaped:
+use `\"` for `"` and `\\` for `\`.
+
+The following escape sequences (beside `\"` and `\\`) are recognized:
+`\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB)
+and `\b` for backspace (BS).  Other char escape sequences (including octal
+escape sequences) are invalid.
+
+
+Includes
+~~~~~~~~
+
+The `include` and `includeIf` sections allow you to include config
+directives from another source. These sections behave identically to
+each other with the exception that `includeIf` sections may be ignored
+if their condition does not evaluate to true; see "Conditional includes"
+below.
+
+You can include a config file from another by setting the special
+`include.path` (or `includeIf.*.path`) variable to the name of the file
+to be included. The variable takes a pathname as its value, and is
+subject to tilde expansion. These variables can be given multiple times.
+
+The contents of the included file are inserted immediately, as if they
+had been found at the location of the include directive. If the value of the
+variable is a relative path, the path is considered to
+be relative to the configuration file in which the include directive
+was found.  See below for examples.
+
+Conditional includes
+~~~~~~~~~~~~~~~~~~~~
+
+You can conditionally include a config file from another by setting an
+`includeIf.<condition>.path` variable to the name of the file to be
+included.
+
+The condition starts with a keyword followed by a colon and some data
+whose format and meaning depends on the keyword. Supported keywords
+are:
+
+`gitdir`::
+
+	The data that follows the keyword `gitdir:` is used as a glob
+	pattern. If the location of the .git directory matches the
+	pattern, the include condition is met.
++
+The .git location may be auto-discovered, or come from `$GIT_DIR`
+environment variable. If the repository is auto-discovered via a .git
+file (e.g. from submodules, or a linked worktree), the .git location
+would be the final location where the .git directory is, not where the
+.git file is.
++
+The pattern can contain standard globbing wildcards and two additional
+ones, `**/` and `/**`, that can match multiple path components. Please
+refer to linkgit:gitignore[5] for details. For convenience:
+
+ * If the pattern starts with `~/`, `~` will be substituted with the
+   content of the environment variable `HOME`.
+
+ * If the pattern starts with `./`, it is replaced with the directory
+   containing the current config file.
+
+ * If the pattern does not start with either `~/`, `./` or `/`, `**/`
+   will be automatically prepended. For example, the pattern `foo/bar`
+   becomes `**/foo/bar` and would match `/any/path/to/foo/bar`.
+
+ * If the pattern ends with `/`, `**` will be automatically added. For
+   example, the pattern `foo/` becomes `foo/**`. In other words, it
+   matches "foo" and everything inside, recursively.
+
+`gitdir/i`::
+	This is the same as `gitdir` except that matching is done
+	case-insensitively (e.g. on case-insensitive file systems)
+
+`onbranch`::
+	The data that follows the keyword `onbranch:` is taken to be a
+	pattern with standard globbing wildcards and two additional
+	ones, `**/` and `/**`, that can match multiple path components.
+	If we are in a worktree where the name of the branch that is
+	currently checked out matches the pattern, the include condition
+	is met.
++
+If the pattern ends with `/`, `**` will be automatically added. For
+example, the pattern `foo/` becomes `foo/**`. In other words, it matches
+all branches that begin with `foo/`. This is useful if your branches are
+organized hierarchically and you would like to apply a configuration to
+all the branches in that hierarchy.
+
+`hasconfig:remote.*.url:`::
+	The data that follows this keyword is taken to
+	be a pattern with standard globbing wildcards and two
+	additional ones, `**/` and `/**`, that can match multiple
+	components. The first time this keyword is seen, the rest of
+	the config files will be scanned for remote URLs (without
+	applying any values). If there exists at least one remote URL
+	that matches this pattern, the include condition is met.
++
+Files included by this option (directly or indirectly) are not allowed
+to contain remote URLs.
++
+Note that unlike other includeIf conditions, resolving this condition
+relies on information that is not yet known at the point of reading the
+condition. A typical use case is this option being present as a
+system-level or global-level config, and the remote URL being in a
+local-level config; hence the need to scan ahead when resolving this
+condition. In order to avoid the chicken-and-egg problem in which
+potentially-included files can affect whether such files are potentially
+included, Git breaks the cycle by prohibiting these files from affecting
+the resolution of these conditions (thus, prohibiting them from
+declaring remote URLs).
++
+As for the naming of this keyword, it is for forwards compatibility with
+a naming scheme that supports more variable-based include conditions,
+but currently Git only supports the exact keyword described above.
+
+A few more notes on matching via `gitdir` and `gitdir/i`:
+
+ * Symlinks in `$GIT_DIR` are not resolved before matching.
+
+ * Both the symlink & realpath versions of paths will be matched
+   outside of `$GIT_DIR`. E.g. if ~/git is a symlink to
+   /mnt/storage/git, both `gitdir:~/git` and `gitdir:/mnt/storage/git`
+   will match.
++
+This was not the case in the initial release of this feature in
+v2.13.0, which only matched the realpath version. Configuration that
+wants to be compatible with the initial release of this feature needs
+to either specify only the realpath version, or both versions.
+
+ * Note that "../" is not special and will match literally, which is
+   unlikely what you want.
+
+Example
+~~~~~~~
+
+----
+# Core variables
+[core]
+	; Don't trust file modes
+	filemode = false
+
+# Our diff algorithm
+[diff]
+	external = /usr/local/bin/diff-wrapper
+	renames = true
+
+[branch "devel"]
+	remote = origin
+	merge = refs/heads/devel
+
+# Proxy settings
+[core]
+	gitProxy="ssh" for "kernel.org"
+	gitProxy=default-proxy ; for the rest
+
+[include]
+	path = /path/to/foo.inc ; include by absolute path
+	path = foo.inc ; find "foo.inc" relative to the current file
+	path = ~/foo.inc ; find "foo.inc" in your `$HOME` directory
+
+; include if $GIT_DIR is /path/to/foo/.git
+[includeIf "gitdir:/path/to/foo/.git"]
+	path = /path/to/foo.inc
+
+; include for all repositories inside /path/to/group
+[includeIf "gitdir:/path/to/group/"]
+	path = /path/to/foo.inc
+
+; include for all repositories inside $HOME/to/group
+[includeIf "gitdir:~/to/group/"]
+	path = /path/to/foo.inc
+
+; relative paths are always relative to the including
+; file (if the condition is true); their location is not
+; affected by the condition
+[includeIf "gitdir:/path/to/group/"]
+	path = foo.inc
+
+; include only if we are in a worktree where foo-branch is
+; currently checked out
+[includeIf "onbranch:foo-branch"]
+	path = foo.inc
+
+; include only if a remote with the given URL exists (note
+; that such a URL may be provided later in a file or in a
+; file read after this file is read, as seen in this example)
+[includeIf "hasconfig:remote.*.url:https://example.com/**"]
+	path = foo.inc
+[remote "origin"]
+	url = https://example.com/git
+----
+
+Values
+~~~~~~
+
+Values of many variables are treated as a simple string, but there
+are variables that take values of specific types and there are rules
+as to how to spell them.
+
+boolean::
+
+       When a variable is said to take a boolean value, many
+       synonyms are accepted for 'true' and 'false'; these are all
+       case-insensitive.
+
+	true;; Boolean true literals are `yes`, `on`, `true`,
+		and `1`.  Also, a variable defined without `= <value>`
+		is taken as true.
+
+	false;; Boolean false literals are `no`, `off`, `false`,
+		`0` and the empty string.
++
+When converting a value to its canonical form using the `--type=bool` type
+specifier, 'git config' will ensure that the output is "true" or
+"false" (spelled in lowercase).
+
+integer::
+       The value for many variables that specify various sizes can
+       be suffixed with `k`, `M`,... to mean "scale the number by
+       1024", "by 1024x1024", etc.
+
+color::
+       The value for a variable that takes a color is a list of
+       colors (at most two, one for foreground and one for background)
+       and attributes (as many as you want), separated by spaces.
++
+The basic colors accepted are `normal`, `black`, `red`, `green`,
+`yellow`, `blue`, `magenta`, `cyan`, `white` and `default`.  The first
+color given is the foreground; the second is the background.  All the
+basic colors except `normal` and `default` have a bright variant that can
+be specified by prefixing the color with `bright`, like `brightred`.
++
+The color `normal` makes no change to the color. It is the same as an
+empty string, but can be used as the foreground color when specifying a
+background color alone (for example, "normal red").
++
+The color `default` explicitly resets the color to the terminal default,
+for example to specify a cleared background. Although it varies between
+terminals, this is usually not the same as setting to "white black".
++
+Colors may also be given as numbers between 0 and 255; these use ANSI
+256-color mode (but note that not all terminals may support this).  If
+your terminal supports it, you may also specify 24-bit RGB values as
+hex, like `#ff0ab3`, or 12-bit RGB values like `#f1b`, which is
+equivalent to the 24-bit color `#ff11bb`.
++
+The accepted attributes are `bold`, `dim`, `ul`, `blink`, `reverse`,
+`italic`, and `strike` (for crossed-out or "strikethrough" letters).
+The position of any attributes with respect to the colors
+(before, after, or in between), doesn't matter. Specific attributes may
+be turned off by prefixing them with `no` or `no-` (e.g., `noreverse`,
+`no-ul`, etc).
++
+The pseudo-attribute `reset` resets all colors and attributes before
+applying the specified coloring. For example, `reset green` will result
+in a green foreground and default background without any active
+attributes.
++
+An empty color string produces no color effect at all. This can be used
+to avoid coloring specific elements without disabling color entirely.
++
+For git's pre-defined color slots, the attributes are meant to be reset
+at the beginning of each item in the colored output. So setting
+`color.decorate.branch` to `black` will paint that branch name in a
+plain `black`, even if the previous thing on the same output line (e.g.
+opening parenthesis before the list of branch names in `log --decorate`
+output) is set to be painted with `bold` or some other attribute.
+However, custom log formats may do more complicated and layered
+coloring, and the negated forms may be useful there.
+
+pathname::
+	A variable that takes a pathname value can be given a
+	string that begins with "`~/`" or "`~user/`", and the usual
+	tilde expansion happens to such a string: `~/`
+	is expanded to the value of `$HOME`, and `~user/` to the
+	specified user's home directory.
++
+If a path starts with `%(prefix)/`, the remainder is interpreted as a
+path relative to Git's "runtime prefix", i.e. relative to the location
+where Git itself was installed. For example, `%(prefix)/bin/` refers to
+the directory in which the Git executable itself lives. If Git was
+compiled without runtime prefix support, the compiled-in prefix will be
+substituted instead. In the unlikely event that a literal path needs to
+be specified that should _not_ be expanded, it needs to be prefixed by
+`./`, like so: `./%(prefix)/bin`.
+
+
+Variables
+~~~~~~~~~
+
+Note that this list is non-comprehensive and not necessarily complete.
+For command-specific variables, you will find a more detailed description
+in the appropriate manual page.
+
+Other git-related tools may and do use their own variables.  When
+inventing new variables for use in your own tool, make sure their
+names do not conflict with those that are used by Git itself and
+other popular tools, and describe them in your documentation.
+
+add.ignoreErrors::
+add.ignore-errors (deprecated)::
+	Tells 'git add' to continue adding files when some files cannot be
+	added due to indexing errors. Equivalent to the `--ignore-errors`
+	option of linkgit:git-add[1].  `add.ignore-errors` is deprecated,
+	as it does not follow the usual naming convention for configuration
+	variables.
+
+
+advice.*::
+	These variables control various optional help messages designed to
+	aid new users.  When left unconfigured, Git will give the message
+	alongside instructions on how to squelch it.  You can tell Git
+	that you do not need the help message by setting these to `false`:
++
+--
+	addEmbeddedRepo::
+		Shown when the user accidentally adds one
+		git repo inside of another.
+	addEmptyPathspec::
+		Shown when the user runs `git add` without providing
+		the pathspec parameter.
+	addIgnoredFile::
+		Shown when the user attempts to add an ignored file to
+		the index.
+	amWorkDir::
+		Shown when linkgit:git-am[1] fails to apply a patch
+		file, to tell the user the location of the file.
+	ambiguousFetchRefspec::
+		Shown when a fetch refspec for multiple remotes maps to
+		the same remote-tracking branch namespace and causes branch
+		tracking set-up to fail.
+	checkoutAmbiguousRemoteBranchName::
+		Shown when the argument to
+		linkgit:git-checkout[1] and linkgit:git-switch[1]
+		ambiguously resolves to a
+		remote tracking branch on more than one remote in
+		situations where an unambiguous argument would have
+		otherwise caused a remote-tracking branch to be
+		checked out. See the `checkout.defaultRemote`
+		configuration variable for how to set a given remote
+		to be used by default in some situations where this
+		advice would be printed.
+	commitBeforeMerge::
+		Shown when linkgit:git-merge[1] refuses to
+		merge to avoid overwriting local changes.
+	detachedHead::
+		Shown when the user uses
+		linkgit:git-switch[1] or linkgit:git-checkout[1]
+		to move to the detached HEAD state, to tell the user how
+		to create a local branch after the fact.
+	diverging::
+		Shown when a fast-forward is not possible.
+	fetchShowForcedUpdates::
+		Shown when linkgit:git-fetch[1] takes a long time
+		to calculate forced updates after ref updates, or to warn
+		that the check is disabled.
+	forceDeleteBranch::
+		Shown when the user tries to delete a not fully merged
+		branch without the force option set.
+	ignoredHook::
+		Shown when a hook is ignored because the hook is not
+		set as executable.
+	implicitIdentity::
+		Shown when the user's information is guessed from the
+		system username and domain name, to tell the user how to
+		set their identity configuration.
+	mergeConflict::
+		Shown when various commands stop because of conflicts.
+	nestedTag::
+		Shown when a user attempts to recursively tag a tag object.
+	pushAlreadyExists::
+		Shown when linkgit:git-push[1] rejects an update that
+		does not qualify for fast-forwarding (e.g., a tag.)
+	pushFetchFirst::
+		Shown when linkgit:git-push[1] rejects an update that
+		tries to overwrite a remote ref that points at an
+		object we do not have.
+	pushNeedsForce::
+		Shown when linkgit:git-push[1] rejects an update that
+		tries to overwrite a remote ref that points at an
+		object that is not a commit-ish, or make the remote
+		ref point at an object that is not a commit-ish.
+	pushNonFFCurrent::
+		Shown when linkgit:git-push[1] fails due to a
+		non-fast-forward update to the current branch.
+	pushNonFFMatching::
+		Shown when the user ran linkgit:git-push[1] and pushed
+		"matching refs" explicitly (i.e. used `:`, or
+		specified a refspec that isn't the current branch) and
+		it resulted in a non-fast-forward error.
+	pushRefNeedsUpdate::
+		Shown when linkgit:git-push[1] rejects a forced update of
+		a branch when its remote-tracking ref has updates that we
+		do not have locally.
+	pushUnqualifiedRefname::
+		Shown when linkgit:git-push[1] gives up trying to
+		guess based on the source and destination refs what
+		remote ref namespace the source belongs in, but where
+		we can still suggest that the user push to either
+		`refs/heads/*` or `refs/tags/*` based on the type of the
+		source object.
+	pushUpdateRejected::
+		Set this variable to `false` if you want to disable
+		`pushNonFFCurrent`, `pushNonFFMatching`, `pushAlreadyExists`,
+		`pushFetchFirst`, `pushNeedsForce`, and `pushRefNeedsUpdate`
+		simultaneously.
+	rebaseTodoError::
+		Shown when there is an error after editing the rebase todo list.
+	refSyntax::
+		Shown when the user provides an illegal ref name, to
+		tell the user about the ref syntax documentation.
+	resetNoRefresh::
+		Shown when linkgit:git-reset[1] takes more than 2
+		seconds to refresh the index after reset, to tell the user
+		that they can use the `--no-refresh` option.
+	resolveConflict::
+		Shown by various commands when conflicts
+		prevent the operation from being performed.
+	rmHints::
+		Shown on failure in the output of linkgit:git-rm[1], to
+		give directions on how to proceed from the current state.
+	sequencerInUse::
+		Shown when a sequencer command is already in progress.
+	skippedCherryPicks::
+		Shown when linkgit:git-rebase[1] skips a commit that has already
+		been cherry-picked onto the upstream branch.
+	sparseIndexExpanded::
+		Shown when a sparse index is expanded to a full index, which is likely
+		due to an unexpected set of files existing outside of the
+		sparse-checkout.
+	statusAheadBehind::
+		Shown when linkgit:git-status[1] computes the ahead/behind
+		counts for a local ref compared to its remote tracking ref,
+		and that calculation takes longer than expected. Will not
+		appear if `status.aheadBehind` is false or the option
+		`--no-ahead-behind` is given.
+	statusHints::
+		Show directions on how to proceed from the current
+		state in the output of linkgit:git-status[1], in
+		the template shown when writing commit messages in
+		linkgit:git-commit[1], and in the help message shown
+		by linkgit:git-switch[1] or
+		linkgit:git-checkout[1] when switching branches.
+	statusUoption::
+		Shown when linkgit:git-status[1] takes more than 2
+		seconds to enumerate untracked files, to tell the user that
+		they can use the `-u` option.
+	submoduleAlternateErrorStrategyDie::
+		Shown when a submodule.alternateErrorStrategy option
+		configured to "die" causes a fatal error.
+	submoduleMergeConflict::
+		Advice shown when a non-trivial submodule merge conflict is
+		encountered.
+	submodulesNotUpdated::
+		Shown when a user runs a submodule command that fails
+		because `git submodule update --init` was not run.
+	suggestDetachingHead::
+		Shown when linkgit:git-switch[1] refuses to detach HEAD
+		without the explicit `--detach` option.
+	updateSparsePath::
+		Shown when either linkgit:git-add[1] or linkgit:git-rm[1]
+		is asked to update index entries outside the current sparse
+		checkout.
+	waitingForEditor::
+		Shown when Git is waiting for editor input. Relevant
+		when e.g. the editor is not launched inside the terminal.
+	worktreeAddOrphan::
+		Shown when the user tries to create a worktree from an
+		invalid reference, to tell the user how to create a new unborn
+		branch instead.
+--
+
+
+alias.*::
+	Command aliases for the linkgit:git[1] command wrapper - e.g.
+	after defining `alias.last = cat-file commit HEAD`, the invocation
+	`git last` is equivalent to `git cat-file commit HEAD`. To avoid
+	confusion and troubles with script usage, aliases that
+	hide existing Git commands are ignored. Arguments are split by
+	spaces, the usual shell quoting and escaping are supported.
+	A quote pair or a backslash can be used to quote them.
++
+Note that the first word of an alias does not necessarily have to be a
+command. It can be a command-line option that will be passed into the
+invocation of `git`. In particular, this is useful when used with `-c`
+to pass in one-time configurations or `-p` to force pagination. For example,
+`loud-rebase = -c commit.verbose=true rebase` can be defined such that
+running `git loud-rebase` would be equivalent to
+`git -c commit.verbose=true rebase`. Also, `ps = -p status` would be a
+helpful alias since `git ps` would paginate the output of `git status`
+where the original command does not.
++
+If the alias expansion is prefixed with an exclamation point,
+it will be treated as a shell command.  For example, defining
+`alias.new = !gitk --all --not ORIG_HEAD`, the invocation
+`git new` is equivalent to running the shell command
+`gitk --all --not ORIG_HEAD`.  Note:
++
+* Shell commands will be executed from the top-level directory of a
+  repository, which may not necessarily be the current directory.
+* `GIT_PREFIX` is set as returned by running `git rev-parse --show-prefix`
+  from the original current directory. See linkgit:git-rev-parse[1].
+* Shell command aliases always receive any extra arguments provided to
+  the Git command-line as positional arguments.
+** Care should be taken if your shell alias is a "one-liner" script
+   with multiple commands (e.g. in a pipeline), references multiple
+   arguments, or is otherwise not able to handle positional arguments
+   added at the end.  For example: `alias.cmd = "!echo $1 | grep $2"`
+   called as `git cmd 1 2` will be executed as 'echo $1 | grep $2
+   1 2', which is not what you want.
+** A convenient way to deal with this is to write your script
+   operations in an inline function that is then called with any
+   arguments from the command-line.  For example `alias.cmd = "!c() {
+   echo $1 | grep $2 ; }; c" will correctly execute the prior example.
+** Setting `GIT_TRACE=1` can help you debug the command being run for
+   your alias.
+
+
+am.keepcr::
+	If true, git-am will call git-mailsplit for patches in mbox format
+	with parameter `--keep-cr`. In this case git-mailsplit will
+	not remove `\r` from lines ending with `\r\n`. Can be overridden
+	by giving `--no-keep-cr` from the command line.
+	See linkgit:git-am[1], linkgit:git-mailsplit[1].
+
+am.threeWay::
+	By default, `git am` will fail if the patch does not apply cleanly. When
+	set to true, this setting tells `git am` to fall back on 3-way merge if
+	the patch records the identity of blobs it is supposed to apply to and
+	we have those blobs available locally (equivalent to giving the `--3way`
+	option from the command line). Defaults to `false`.
+	See linkgit:git-am[1].
+
+
+apply.ignoreWhitespace::
+	When set to 'change', tells 'git apply' to ignore changes in
+	whitespace, in the same way as the `--ignore-space-change`
+	option.
+	When set to one of: no, none, never, false, it tells 'git apply' to
+	respect all whitespace differences.
+	See linkgit:git-apply[1].
+
+apply.whitespace::
+	Tells 'git apply' how to handle whitespace, in the same way
+	as the `--whitespace` option. See linkgit:git-apply[1].
+
+
+attr.tree::
+	A reference to a tree in the repository from which to read attributes,
+	instead of the `.gitattributes` file in the working tree. If the value
+	does not resolve to a valid tree object, an empty tree is used instead.
+	When the `GIT_ATTR_SOURCE` environment variable or `--attr-source`
+	command line option are used, this configuration variable has no effect.
+
+
+NOTE: The configuration options in `bitmapPseudoMerge.*` are considered
+EXPERIMENTAL and may be subject to change or be removed entirely in the
+future. For more information about the pseudo-merge bitmap feature, see
+the "Pseudo-merge bitmaps" section of linkgit:gitpacking[7].
+
+bitmapPseudoMerge.<name>.pattern::
+	Regular expression used to match reference names. Commits
+	pointed to by references matching this pattern (and meeting
+	the below criteria, like `bitmapPseudoMerge.<name>.sampleRate`
+	and `bitmapPseudoMerge.<name>.threshold`) will be considered
+	for inclusion in a pseudo-merge bitmap.
++
+Commits are grouped into pseudo-merge groups based on whether or not
+any reference(s) that point at a given commit match the pattern, which
+is an extended regular expression.
++
+Within a pseudo-merge group, commits may be further grouped into
+sub-groups based on the capture groups in the pattern. These
+sub-groupings are formed from the regular expressions by concatenating
+any capture groups from the regular expression, with a '-' dash in
+between.
++
+For example, if the pattern is `refs/tags/`, then all tags (provided
+they meet the below criteria) will be considered candidates for the
+same pseudo-merge group. However, if the pattern is instead
+`refs/remotes/([0-9])+/tags/`, then tags from different remotes will
+be grouped into separate pseudo-merge groups, based on the remote
+number.
+
+bitmapPseudoMerge.<name>.decay::
+	Determines the rate at which consecutive pseudo-merge bitmap
+	groups decrease in size. Must be non-negative. This parameter
+	can be thought of as `k` in the function `f(n) = C * n^-k`,
+	where `f(n)` is the size of the `n`th group.
++
+Setting the decay rate equal to `0` will cause all groups to be the
+same size. Setting the decay rate equal to `1` will cause the `n`th
+group to be `1/n` the size of the initial group.  Higher values of the
+decay rate cause consecutive groups to shrink at an increasing rate.
+The default is `1`.
++
+If all groups are the same size, it is possible that groups containing
+newer commits will be able to be used less often than earlier groups,
+since it is more likely that the references pointing at newer commits
+will be updated more often than a reference pointing at an old commit.
+
+bitmapPseudoMerge.<name>.sampleRate::
+	Determines the proportion of non-bitmapped commits (among
+	reference tips) which are selected for inclusion in an
+	unstable pseudo-merge bitmap. Must be between `0` and `1`
+	(inclusive). The default is `1`.
+
+bitmapPseudoMerge.<name>.threshold::
+	Determines the minimum age of non-bitmapped commits (among
+	reference tips, as above) which are candidates for inclusion
+	in an unstable pseudo-merge bitmap. The default is
+	`1.week.ago`.
+
+bitmapPseudoMerge.<name>.maxMerges::
+	Determines the maximum number of pseudo-merge commits among
+	which commits may be distributed.
++
+For pseudo-merge groups whose pattern does not contain any capture
+groups, this setting is applied for all commits matching the regular
+expression. For patterns that have one or more capture groups, this
+setting is applied for each distinct capture group.
++
+For example, if your capture group is `refs/tags/`, then this setting
+will distribute all tags into a maximum of `maxMerges` pseudo-merge
+commits. However, if your capture group is, say,
+`refs/remotes/([0-9]+)/tags/`, then this setting will be applied to
+each remote's set of tags individually.
++
+Must be non-negative. The default value is 64.
+
+bitmapPseudoMerge.<name>.stableThreshold::
+	Determines the minimum age of commits (among reference tips,
+	as above, however stable commits are still considered
+	candidates even when they have been covered by a bitmap) which
+	are candidates for a stable a pseudo-merge bitmap. The default
+	is `1.month.ago`.
++
+Setting this threshold to a smaller value (e.g., 1.week.ago) will cause
+more stable groups to be generated (which impose a one-time generation
+cost) but those groups will likely become stale over time. Using a
+larger value incurs the opposite penalty (fewer stable groups which are
+more useful).
+
+bitmapPseudoMerge.<name>.stableSize::
+	Determines the size (in number of commits) of a stable
+	psuedo-merge bitmap. The default is `512`.
+
+
+blame.blankBoundary::
+	Show blank commit object name for boundary commits in
+	linkgit:git-blame[1]. This option defaults to false.
+
+blame.coloring::
+	This determines the coloring scheme to be applied to blame
+	output. It can be 'repeatedLines', 'highlightRecent',
+	or 'none' which is the default.
+
+blame.date::
+	Specifies the format used to output dates in linkgit:git-blame[1].
+	If unset the iso format is used. For supported values,
+	see the discussion of the `--date` option at linkgit:git-log[1].
+
+blame.showEmail::
+	Show the author email instead of author name in linkgit:git-blame[1].
+	This option defaults to false.
+
+blame.showRoot::
+	Do not treat root commits as boundaries in linkgit:git-blame[1].
+	This option defaults to false.
+
+blame.ignoreRevsFile::
+	Ignore revisions listed in the file, one unabbreviated object name per
+	line, in linkgit:git-blame[1].  Whitespace and comments beginning with
+	`#` are ignored.  This option may be repeated multiple times.  Empty
+	file names will reset the list of ignored revisions.  This option will
+	be handled before the command line option `--ignore-revs-file`.
+
+blame.markUnblamableLines::
+	Mark lines that were changed by an ignored revision that we could not
+	attribute to another commit with a '*' in the output of
+	linkgit:git-blame[1].
+
+blame.markIgnoredLines::
+	Mark lines that were changed by an ignored revision that we attributed to
+	another commit with a '?' in the output of linkgit:git-blame[1].
+
+
+branch.autoSetupMerge::
+	Tells 'git branch', 'git switch' and 'git checkout' to set up new branches
+	so that linkgit:git-pull[1] will appropriately merge from the
+	starting point branch. Note that even if this option is not set,
+	this behavior can be chosen per-branch using the `--track`
+	and `--no-track` options. The valid settings are: `false` -- no
+	automatic setup is done; `true` -- automatic setup is done when the
+	starting point is a remote-tracking branch; `always` --
+	automatic setup is done when the starting point is either a
+	local branch or remote-tracking branch; `inherit` -- if the starting point
+	has a tracking configuration, it is copied to the new
+	branch; `simple` -- automatic setup is done only when the starting point
+	is a remote-tracking branch and the new branch has the same name as the
+	remote branch. This option defaults to true.
+
+branch.autoSetupRebase::
+	When a new branch is created with 'git branch', 'git switch' or 'git checkout'
+	that tracks another branch, this variable tells Git to set
+	up pull to rebase instead of merge (see "branch.<name>.rebase").
+	When `never`, rebase is never automatically set to true.
+	When `local`, rebase is set to true for tracked branches of
+	other local branches.
+	When `remote`, rebase is set to true for tracked branches of
+	remote-tracking branches.
+	When `always`, rebase will be set to true for all tracking
+	branches.
+	See "branch.autoSetupMerge" for details on how to set up a
+	branch to track another branch.
+	This option defaults to never.
+
+branch.sort::
+	This variable controls the sort ordering of branches when displayed by
+	linkgit:git-branch[1]. Without the "--sort=<value>" option provided, the
+	value of this variable will be used as the default.
+	See linkgit:git-for-each-ref[1] field names for valid values.
+
+branch.<name>.remote::
+	When on branch <name>, it tells 'git fetch' and 'git push'
+	which remote to fetch from or push to.  The remote to push to
+	may be overridden with `remote.pushDefault` (for all branches).
+	The remote to push to, for the current branch, may be further
+	overridden by `branch.<name>.pushRemote`.  If no remote is
+	configured, or if you are not on any branch and there is more than
+	one remote defined in the repository, it defaults to `origin` for
+	fetching and `remote.pushDefault` for pushing.
+	Additionally, `.` (a period) is the current local repository
+	(a dot-repository), see `branch.<name>.merge`'s final note below.
+
+branch.<name>.pushRemote::
+	When on branch <name>, it overrides `branch.<name>.remote` for
+	pushing.  It also overrides `remote.pushDefault` for pushing
+	from branch <name>.  When you pull from one place (e.g. your
+	upstream) and push to another place (e.g. your own publishing
+	repository), you would want to set `remote.pushDefault` to
+	specify the remote to push to for all branches, and use this
+	option to override it for a specific branch.
+
+branch.<name>.merge::
+	Defines, together with branch.<name>.remote, the upstream branch
+	for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which
+	branch to merge and can also affect 'git push' (see push.default).
+	When in branch <name>, it tells 'git fetch' the default
+	refspec to be marked for merging in FETCH_HEAD. The value is
+	handled like the remote part of a refspec, and must match a
+	ref which is fetched from the remote given by
+	"branch.<name>.remote".
+	The merge information is used by 'git pull' (which first calls
+	'git fetch') to lookup the default branch for merging. Without
+	this option, 'git pull' defaults to merge the first refspec fetched.
+	Specify multiple values to get an octopus merge.
+	If you wish to setup 'git pull' so that it merges into <name> from
+	another branch in the local repository, you can point
+	branch.<name>.merge to the desired branch, and use the relative path
+	setting `.` (a period) for branch.<name>.remote.
+
+branch.<name>.mergeOptions::
+	Sets default options for merging into branch <name>. The syntax and
+	supported options are the same as those of linkgit:git-merge[1], but
+	option values containing whitespace characters are currently not
+	supported.
+
+branch.<name>.rebase::
+	When true, rebase the branch <name> on top of the fetched branch,
+	instead of merging the default branch from the default remote when
+	"git pull" is run. See "pull.rebase" for doing this in a non
+	branch-specific manner.
++
+When `merges` (or just 'm'), pass the `--rebase-merges` option to 'git rebase'
+so that the local merge commits are included in the rebase (see
+linkgit:git-rebase[1] for details).
++
+When the value is `interactive` (or just 'i'), the rebase is run in interactive
+mode.
++
+*NOTE*: this is a possibly dangerous operation; do *not* use
+it unless you understand the implications (see linkgit:git-rebase[1]
+for details).
+
+branch.<name>.description::
+	Branch description, can be edited with
+	`git branch --edit-description`. Branch description is
+	automatically added to the format-patch cover letter or
+	request-pull summary.
+
+
+browser.<tool>.cmd::
+	Specify the command to invoke the specified browser. The
+	specified command is evaluated in shell with the URLs passed
+	as arguments. (See linkgit:git-web{litdd}browse[1].)
+
+browser.<tool>.path::
+	Override the path for the given tool that may be used to
+	browse HTML help (see `-w` option in linkgit:git-help[1]) or a
+	working repository in gitweb (see linkgit:git-instaweb[1]).
+
+
+bundle.*::
+	The `bundle.*` keys may appear in a bundle list file found via the
+	`git clone --bundle-uri` option. These keys currently have no effect
+	if placed in a repository config file, though this will change in the
+	future. See link:/docs/bundle-uri[the bundle URI design
+	document] for more details.
+
+bundle.version::
+	This integer value advertises the version of the bundle list format
+	used by the bundle list. Currently, the only accepted value is `1`.
+
+bundle.mode::
+	This string value should be either `all` or `any`. This value describes
+	whether all of the advertised bundles are required to unbundle a
+	complete understanding of the bundled information (`all`) or if any one
+	of the listed bundle URIs is sufficient (`any`).
+
+bundle.heuristic::
+	If this string-valued key exists, then the bundle list is designed to
+	work well with incremental `git fetch` commands. The heuristic signals
+	that there are additional keys available for each bundle that help
+	determine which subset of bundles the client should download. The
+	only value currently understood is `creationToken`.
+
+bundle.<id>.*::
+	The `bundle.<id>.*` keys are used to describe a single item in the
+	bundle list, grouped under `<id>` for identification purposes.
+
+bundle.<id>.uri::
+	This string value defines the URI by which Git can reach the contents
+	of this `<id>`. This URI may be a bundle file or another bundle list.
+
+
+checkout.defaultRemote::
+	When you run `git checkout <something>`
+	or `git switch <something>` and only have one
+	remote, it may implicitly fall back on checking out and
+	tracking e.g. `origin/<something>`. This stops working as soon
+	as you have more than one remote with a `<something>`
+	reference. This setting allows for setting the name of a
+	preferred remote that should always win when it comes to
+	disambiguation. The typical use-case is to set this to
+	`origin`.
++
+Currently this is used by linkgit:git-switch[1] and
+linkgit:git-checkout[1] when `git checkout <something>`
+or `git switch <something>`
+will checkout the `<something>` branch on another remote,
+and by linkgit:git-worktree[1] when `git worktree add` refers to a
+remote branch. This setting might be used for other checkout-like
+commands or functionality in the future.
+
+checkout.guess::
+	Provides the default value for the `--guess` or `--no-guess`
+	option in `git checkout` and `git switch`. See
+	linkgit:git-switch[1] and linkgit:git-checkout[1].
+
+checkout.workers::
+	The number of parallel workers to use when updating the working tree.
+	The default is one, i.e. sequential execution. If set to a value less
+	than one, Git will use as many workers as the number of logical cores
+	available. This setting and `checkout.thresholdForParallelism` affect
+	all commands that perform checkout. E.g. checkout, clone, reset,
+	sparse-checkout, etc.
++
+Note: Parallel checkout usually delivers better performance for repositories
+located on SSDs or over NFS. For repositories on spinning disks and/or machines
+with a small number of cores, the default sequential checkout often performs
+better. The size and compression level of a repository might also influence how
+well the parallel version performs.
+
+checkout.thresholdForParallelism::
+	When running parallel checkout with a small number of files, the cost
+	of subprocess spawning and inter-process communication might outweigh
+	the parallelization gains. This setting allows you to define the minimum
+	number of files for which parallel checkout should be attempted. The
+	default is 100.
+
+
+clean.requireForce::
+	A boolean to make git-clean refuse to delete files unless -f
+	is given. Defaults to true.
+
+
+`clone.defaultRemoteName`::
+	The name of the remote to create when cloning a repository.  Defaults to
+	`origin`.
+ifdef::git-clone[]
+	It can be overridden by passing the `--origin` command-line
+	option.
+endif::[]
+ifndef::git-clone[]
+	It can be overridden by passing the `--origin` command-line
+	option to linkgit:git-clone[1].
+endif::[]
+
+`clone.rejectShallow`::
+	Reject cloning a repository if it is a shallow one; this can be overridden by
+	passing the `--reject-shallow` option on the command line.
+ifndef::git-clone[]
+	See linkgit:git-clone[1].
+endif::[]
+
+`clone.filterSubmodules`::
+	If a partial clone filter is provided (see `--filter` in
+	linkgit:git-rev-list[1]) and `--recurse-submodules` is used, also apply
+	the filter to submodules.
+
+
+color.advice::
+	A boolean to enable/disable color in hints (e.g. when a push
+	failed, see `advice.*` for a list).  May be set to `always`,
+	`false` (or `never`) or `auto` (or `true`), in which case colors
+	are used only when the error output goes to a terminal. If
+	unset, then the value of `color.ui` is used (`auto` by default).
+
+color.advice.hint::
+	Use customized color for hints.
+
+color.blame.highlightRecent::
+	Specify the line annotation color for `git blame --color-by-age`
+	depending upon the age of the line.
++
+This setting should be set to a comma-separated list of color and
+date settings, starting and ending with a color, the dates should be
+set from oldest to newest. The metadata will be colored with the
+specified colors if the line was introduced before the given
+timestamp, overwriting older timestamped colors.
++
+Instead of an absolute timestamp relative timestamps work as well,
+e.g. `2.weeks.ago` is valid to address anything older than 2 weeks.
++
+It defaults to `blue,12 month ago,white,1 month ago,red`, which
+colors everything older than one year blue, recent changes between
+one month and one year old are kept white, and lines introduced
+within the last month are colored red.
+
+color.blame.repeatedLines::
+	Use the specified color to colorize line annotations for
+	`git blame --color-lines`, if they come from the same commit as the
+	preceding line. Defaults to cyan.
+
+color.branch::
+	A boolean to enable/disable color in the output of
+	linkgit:git-branch[1]. May be set to `always`,
+	`false` (or `never`) or `auto` (or `true`), in which case colors are used
+	only when the output is to a terminal. If unset, then the
+	value of `color.ui` is used (`auto` by default).
+
+color.branch.<slot>::
+	Use customized color for branch coloration. `<slot>` is one of
+	`current` (the current branch), `local` (a local branch),
+	`remote` (a remote-tracking branch in refs/remotes/),
+	`upstream` (upstream tracking branch), `plain` (other
+	refs).
+
+color.diff::
+	Whether to use ANSI escape sequences to add color to patches.
+	If this is set to `always`, linkgit:git-diff[1],
+	linkgit:git-log[1], and linkgit:git-show[1] will use color
+	for all patches.  If it is set to `true` or `auto`, those
+	commands will only use color when output is to the terminal.
+	If unset, then the value of `color.ui` is used (`auto` by
+	default).
++
+This does not affect linkgit:git-format-patch[1] or the
+'git-diff-{asterisk}' plumbing commands.  Can be overridden on the
+command line with the `--color[=<when>]` option.
+
+color.diff.<slot>::
+	Use customized color for diff colorization.  `<slot>` specifies
+	which part of the patch to use the specified color, and is one
+	of `context` (context text - `plain` is a historical synonym),
+	`meta` (metainformation), `frag`
+	(hunk header), 'func' (function in hunk header), `old` (removed lines),
+	`new` (added lines), `commit` (commit headers), `whitespace`
+	(highlighting whitespace errors), `oldMoved` (deleted lines),
+	`newMoved` (added lines), `oldMovedDimmed`, `oldMovedAlternative`,
+	`oldMovedAlternativeDimmed`, `newMovedDimmed`, `newMovedAlternative`
+	`newMovedAlternativeDimmed` (See the '<mode>'
+	setting of '--color-moved' in linkgit:git-diff[1] for details),
+	`contextDimmed`, `oldDimmed`, `newDimmed`, `contextBold`,
+	`oldBold`, and `newBold` (see linkgit:git-range-diff[1] for details).
+
+color.decorate.<slot>::
+	Use customized color for 'git log --decorate' output.  `<slot>` is one
+	of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local
+	branches, remote-tracking branches, tags, stash and HEAD, respectively
+	and `grafted` for grafted commits.
+
+color.grep::
+	When set to `always`, always highlight matches.  When `false` (or
+	`never`), never.  When set to `true` or `auto`, use color only
+	when the output is written to the terminal.  If unset, then the
+	value of `color.ui` is used (`auto` by default).
+
+color.grep.<slot>::
+	Use customized color for grep colorization.  `<slot>` specifies which
+	part of the line to use the specified color, and is one of
++
+--
+`context`;;
+	non-matching text in context lines (when using `-A`, `-B`, or `-C`)
+`filename`;;
+	filename prefix (when not using `-h`)
+`function`;;
+	function name lines (when using `-p`)
+`lineNumber`;;
+	line number prefix (when using `-n`)
+`column`;;
+	column number prefix (when using `--column`)
+`match`;;
+	matching text (same as setting `matchContext` and `matchSelected`)
+`matchContext`;;
+	matching text in context lines
+`matchSelected`;;
+	matching text in selected lines. Also, used to customize the following
+	linkgit:git-log[1] subcommands: `--grep`, `--author`, and `--committer`.
+`selected`;;
+	non-matching text in selected lines. Also, used to customize the
+	following linkgit:git-log[1] subcommands: `--grep`, `--author` and
+	`--committer`.
+`separator`;;
+	separators between fields on a line (`:`, `-`, and `=`)
+	and between hunks (`--`)
+--
+
+color.interactive::
+	When set to `always`, always use colors for interactive prompts
+	and displays (such as those used by "git-add --interactive" and
+	"git-clean --interactive"). When false (or `never`), never.
+	When set to `true` or `auto`, use colors only when the output is
+	to the terminal. If unset, then the value of `color.ui` is
+	used (`auto` by default).
+
+color.interactive.<slot>::
+	Use customized color for 'git add --interactive' and 'git clean
+	--interactive' output. `<slot>` may be `prompt`, `header`, `help`
+	or `error`, for four distinct types of normal output from
+	interactive commands.
+
+color.pager::
+	A boolean to specify whether `auto` color modes should colorize
+	output going to the pager. Defaults to true; set this to false
+	if your pager does not understand ANSI color codes.
+
+color.push::
+	A boolean to enable/disable color in push errors. May be set to
+	`always`, `false` (or `never`) or `auto` (or `true`), in which
+	case colors are used only when the error output goes to a terminal.
+	If unset, then the value of `color.ui` is used (`auto` by default).
+
+color.push.error::
+	Use customized color for push errors.
+
+color.remote::
+	If set, keywords at the start of the line are highlighted. The
+	keywords are "error", "warning", "hint" and "success", and are
+	matched case-insensitively. May be set to `always`, `false` (or
+	`never`) or `auto` (or `true`). If unset, then the value of
+	`color.ui` is used (`auto` by default).
+
+color.remote.<slot>::
+	Use customized color for each remote keyword. `<slot>` may be
+	`hint`, `warning`, `success` or `error` which match the
+	corresponding keyword.
+
+color.showBranch::
+	A boolean to enable/disable color in the output of
+	linkgit:git-show-branch[1]. May be set to `always`,
+	`false` (or `never`) or `auto` (or `true`), in which case colors are used
+	only when the output is to a terminal. If unset, then the
+	value of `color.ui` is used (`auto` by default).
+
+color.status::
+	A boolean to enable/disable color in the output of
+	linkgit:git-status[1]. May be set to `always`,
+	`false` (or `never`) or `auto` (or `true`), in which case colors are used
+	only when the output is to a terminal. If unset, then the
+	value of `color.ui` is used (`auto` by default).
+
+color.status.<slot>::
+	Use customized color for status colorization. `<slot>` is
+	one of `header` (the header text of the status message),
+	`added` or `updated` (files which are added but not committed),
+	`changed` (files which are changed but not added in the index),
+	`untracked` (files which are not tracked by Git),
+	`branch` (the current branch),
+	`nobranch` (the color the 'no branch' warning is shown in, defaulting
+	to red),
+	`localBranch` or `remoteBranch` (the local and remote branch names,
+	respectively, when branch and tracking information is displayed in the
+	status short-format), or
+	`unmerged` (files which have unmerged changes).
+
+color.transport::
+	A boolean to enable/disable color when pushes are rejected. May be
+	set to `always`, `false` (or `never`) or `auto` (or `true`), in which
+	case colors are used only when the error output goes to a terminal.
+	If unset, then the value of `color.ui` is used (`auto` by default).
+
+color.transport.rejected::
+	Use customized color when a push was rejected.
+
+color.ui::
+	This variable determines the default value for variables such
+	as `color.diff` and `color.grep` that control the use of color
+	per command family. Its scope will expand as more commands learn
+	configuration to set a default for the `--color` option.  Set it
+	to `false` or `never` if you prefer Git commands not to use
+	color unless enabled explicitly with some other configuration
+	or the `--color` option. Set it to `always` if you want all
+	output not intended for machine consumption to use color, to
+	`true` or `auto` (this is the default since Git 1.8.4) if you
+	want such output to use color when written to the terminal.
+
+
+column.ui::
+	Specify whether supported commands should output in columns.
+	This variable consists of a list of tokens separated by spaces
+	or commas:
++
+These options control when the feature should be enabled
+(defaults to 'never'):
++
+--
+`always`;;
+	always show in columns
+`never`;;
+	never show in columns
+`auto`;;
+	show in columns if the output is to the terminal
+--
++
+These options control layout (defaults to 'column').  Setting any
+of these implies 'always' if none of 'always', 'never', or 'auto' are
+specified.
++
+--
+`column`;;
+	fill columns before rows
+`row`;;
+	fill rows before columns
+`plain`;;
+	show in one column
+--
++
+Finally, these options can be combined with a layout option (defaults
+to 'nodense'):
++
+--
+`dense`;;
+	make unequal size columns to utilize more space
+`nodense`;;
+	make equal size columns
+--
+
+column.branch::
+	Specify whether to output branch listing in `git branch` in columns.
+	See `column.ui` for details.
+
+column.clean::
+	Specify the layout when listing items in `git clean -i`, which always
+	shows files and directories in columns. See `column.ui` for details.
+
+column.status::
+	Specify whether to output untracked files in `git status` in columns.
+	See `column.ui` for details.
+
+column.tag::
+	Specify whether to output tag listings in `git tag` in columns.
+	See `column.ui` for details.
+
+
+commit.cleanup::
+	This setting overrides the default of the `--cleanup` option in
+	`git commit`. See linkgit:git-commit[1] for details. Changing the
+	default can be useful when you always want to keep lines that begin
+	with the comment character `#` in your log message, in which case you
+	would do `git config commit.cleanup whitespace` (note that you will
+	have to remove the help lines that begin with `#` in the commit log
+	template yourself, if you do this).
+
+commit.gpgSign::
+
+	A boolean to specify whether all commits should be GPG signed.
+	Use of this option when doing operations such as rebase can
+	result in a large number of commits being signed. It may be
+	convenient to use an agent to avoid typing your GPG passphrase
+	several times.
+
+commit.status::
+	A boolean to enable/disable inclusion of status information in the
+	commit message template when using an editor to prepare the commit
+	message.  Defaults to true.
+
+commit.template::
+	Specify the pathname of a file to use as the template for
+	new commit messages.
+
+commit.verbose::
+	A boolean or int to specify the level of verbosity with `git commit`.
+	See linkgit:git-commit[1].
+
+
+commitGraph.generationVersion::
+	Specifies the type of generation number version to use when writing
+	or reading the commit-graph file. If version 1 is specified, then
+	the corrected commit dates will not be written or read. Defaults to
+	2.
+
+commitGraph.maxNewFilters::
+	Specifies the default value for the `--max-new-filters` option of `git
+	commit-graph write` (c.f., linkgit:git-commit-graph[1]).
+
+commitGraph.readChangedPaths::
+	Deprecated. Equivalent to commitGraph.changedPathsVersion=-1 if true, and
+	commitGraph.changedPathsVersion=0 if false. (If commitGraph.changedPathVersion
+	is also set, commitGraph.changedPathsVersion takes precedence.)
+
+commitGraph.changedPathsVersion::
+	Specifies the version of the changed-path Bloom filters that Git will read and
+	write. May be -1, 0, 1, or 2. Note that values greater than 1 may be
+	incompatible with older versions of Git which do not yet understand
+	those versions. Use caution when operating in a mixed-version
+	environment.
++
+Defaults to -1.
++
+If -1, Git will use the version of the changed-path Bloom filters in the
+repository, defaulting to 1 if there are none.
++
+If 0, Git will not read any Bloom filters, and will write version 1 Bloom
+filters when instructed to write.
++
+If 1, Git will only read version 1 Bloom filters, and will write version 1
+Bloom filters.
++
+If 2, Git will only read version 2 Bloom filters, and will write version 2
+Bloom filters.
++
+See linkgit:git-commit-graph[1] for more information.
+
+
+completion.commands::
+	This is only used by git-completion.bash to add or remove
+	commands from the list of completed commands. Normally only
+	porcelain commands and a few select others are completed. You
+	can add more commands, separated by space, in this
+	variable. Prefixing the command with '-' will remove it from
+	the existing list.
+
+
+core.fileMode::
+	Tells Git if the executable bit of files in the working tree
+	is to be honored.
++
+Some filesystems lose the executable bit when a file that is
+marked as executable is checked out, or checks out a
+non-executable file with executable bit on.
+linkgit:git-clone[1] or linkgit:git-init[1] probe the filesystem
+to see if it handles the executable bit correctly
+and this variable is automatically set as necessary.
++
+A repository, however, may be on a filesystem that handles
+the filemode correctly, and this variable is set to 'true'
+when created, but later may be made accessible from another
+environment that loses the filemode (e.g. exporting ext4 via
+CIFS mount, visiting a Cygwin created repository with
+Git for Windows or Eclipse).
+In such a case it may be necessary to set this variable to 'false'.
+See linkgit:git-update-index[1].
++
+The default is true (when core.filemode is not specified in the config file).
+
+core.hideDotFiles::
+	(Windows-only) If true, mark newly-created directories and files whose
+	name starts with a dot as hidden.  If 'dotGitOnly', only the `.git/`
+	directory is hidden, but no other files starting with a dot.  The
+	default mode is 'dotGitOnly'.
+
+core.ignoreCase::
+	Internal variable which enables various workarounds to enable
+	Git to work better on filesystems that are not case sensitive,
+	like APFS, HFS+, FAT, NTFS, etc. For example, if a directory listing
+	finds "makefile" when Git expects "Makefile", Git will assume
+	it is really the same file, and continue to remember it as
+	"Makefile".
++
+The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]
+will probe and set core.ignoreCase true if appropriate when the repository
+is created.
++
+Git relies on the proper configuration of this variable for your operating
+and file system. Modifying this value may result in unexpected behavior.
+
+core.precomposeUnicode::
+	This option is only used by Mac OS implementation of Git.
+	When core.precomposeUnicode=true, Git reverts the unicode decomposition
+	of filenames done by Mac OS. This is useful when sharing a repository
+	between Mac OS and Linux or Windows.
+	(Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7).
+	When false, file names are handled fully transparent by Git,
+	which is backward compatible with older versions of Git.
+
+core.protectHFS::
+	If set to true, do not allow checkout of paths that would
+	be considered equivalent to `.git` on an HFS+ filesystem.
+	Defaults to `true` on Mac OS, and `false` elsewhere.
+
+core.protectNTFS::
+	If set to true, do not allow checkout of paths that would
+	cause problems with the NTFS filesystem, e.g. conflict with
+	8.3 "short" names.
+	Defaults to `true` on Windows, and `false` elsewhere.
+
+core.fsmonitor::
+	If set to true, enable the built-in file system monitor
+	daemon for this working directory (linkgit:git-fsmonitor{litdd}daemon[1]).
++
+Like hook-based file system monitors, the built-in file system monitor
+can speed up Git commands that need to refresh the Git index
+(e.g. `git status`) in a working directory with many files.  The
+built-in monitor eliminates the need to install and maintain an
+external third-party tool.
++
+The built-in file system monitor is currently available only on a
+limited set of supported platforms.  Currently, this includes Windows
+and MacOS.
++
+	Otherwise, this variable contains the pathname of the "fsmonitor"
+	hook command.
++
+This hook command is used to identify all files that may have changed
+since the requested date/time. This information is used to speed up
+git by avoiding unnecessary scanning of files that have not changed.
++
+See the "fsmonitor-watchman" section of linkgit:githooks[5].
++
+Note that if you concurrently use multiple versions of Git, such
+as one version on the command line and another version in an IDE
+tool, that the definition of `core.fsmonitor` was extended to
+allow boolean values in addition to hook pathnames.  Git versions
+2.35.1 and prior will not understand the boolean values and will
+consider the "true" or "false" values as hook pathnames to be
+invoked.  Git versions 2.26 thru 2.35.1 default to hook protocol
+V2 and will fall back to no fsmonitor (full scan).  Git versions
+prior to 2.26 default to hook protocol V1 and will silently
+assume there were no changes to report (no scan), so status
+commands may report incomplete results.  For this reason, it is
+best to upgrade all of your Git versions before using the built-in
+file system monitor.
+
+core.fsmonitorHookVersion::
+	Sets the protocol version to be used when invoking the
+	"fsmonitor" hook.
++
+There are currently versions 1 and 2. When this is not set,
+version 2 will be tried first and if it fails then version 1
+will be tried. Version 1 uses a timestamp as input to determine
+which files have changes since that time but some monitors
+like Watchman have race conditions when used with a timestamp.
+Version 2 uses an opaque string so that the monitor can return
+something that can be used to determine what files have changed
+without race conditions.
+
+core.trustctime::
+	If false, the ctime differences between the index and the
+	working tree are ignored; useful when the inode change time
+	is regularly modified by something outside Git (file system
+	crawlers and some backup systems).
+	See linkgit:git-update-index[1]. True by default.
+
+core.splitIndex::
+	If true, the split-index feature of the index will be used.
+	See linkgit:git-update-index[1]. False by default.
+
+core.untrackedCache::
+	Determines what to do about the untracked cache feature of the
+	index. It will be kept, if this variable is unset or set to
+	`keep`. It will automatically be added if set to `true`. And
+	it will automatically be removed, if set to `false`. Before
+	setting it to `true`, you should check that mtime is working
+	properly on your system.
+	See linkgit:git-update-index[1]. `keep` by default, unless
+	`feature.manyFiles` is enabled which sets this setting to
+	`true` by default.
+
+core.checkStat::
+	When missing or is set to `default`, many fields in the stat
+	structure are checked to detect if a file has been modified
+	since Git looked at it.  When this configuration variable is
+	set to `minimal`, sub-second part of mtime and ctime, the
+	uid and gid of the owner of the file, the inode number (and
+	the device number, if Git was compiled to use it), are
+	excluded from the check among these fields, leaving only the
+	whole-second part of mtime (and ctime, if `core.trustCtime`
+	is set) and the filesize to be checked.
++
+There are implementations of Git that do not leave usable values in
+some fields (e.g. JGit); by excluding these fields from the
+comparison, the `minimal` mode may help interoperability when the
+same repository is used by these other systems at the same time.
+
+core.quotePath::
+	Commands that output paths (e.g. 'ls-files', 'diff'), will
+	quote "unusual" characters in the pathname by enclosing the
+	pathname in double-quotes and escaping those characters with
+	backslashes in the same way C escapes control characters (e.g.
+	`\t` for TAB, `\n` for LF, `\\` for backslash) or bytes with
+	values larger than 0x80 (e.g. octal `\302\265` for "micro" in
+	UTF-8).  If this variable is set to false, bytes higher than
+	0x80 are not considered "unusual" any more. Double-quotes,
+	backslash and control characters are always escaped regardless
+	of the setting of this variable.  A simple space character is
+	not considered "unusual".  Many commands can output pathnames
+	completely verbatim using the `-z` option. The default value
+	is true.
+
+core.eol::
+	Sets the line ending type to use in the working directory for
+	files that are marked as text (either by having the `text`
+	attribute set, or by having `text=auto` and Git auto-detecting
+	the contents as text).
+	Alternatives are 'lf', 'crlf' and 'native', which uses the platform's
+	native line ending.  The default value is `native`.  See
+	linkgit:gitattributes[5] for more information on end-of-line
+	conversion. Note that this value is ignored if `core.autocrlf`
+	is set to `true` or `input`.
+
+core.safecrlf::
+	If true, makes Git check if converting `CRLF` is reversible when
+	end-of-line conversion is active.  Git will verify if a command
+	modifies a file in the work tree either directly or indirectly.
+	For example, committing a file followed by checking out the
+	same file should yield the original file in the work tree.  If
+	this is not the case for the current setting of
+	`core.autocrlf`, Git will reject the file.  The variable can
+	be set to "warn", in which case Git will only warn about an
+	irreversible conversion but continue the operation.
++
+CRLF conversion bears a slight chance of corrupting data.
+When it is enabled, Git will convert CRLF to LF during commit and LF to
+CRLF during checkout.  A file that contains a mixture of LF and
+CRLF before the commit cannot be recreated by Git.  For text
+files this is the right thing to do: it corrects line endings
+such that we have only LF line endings in the repository.
+But for binary files that are accidentally classified as text the
+conversion can corrupt data.
++
+If you recognize such corruption early you can easily fix it by
+setting the conversion type explicitly in .gitattributes.  Right
+after committing you still have the original file in your work
+tree and this file is not yet corrupted.  You can explicitly tell
+Git that this file is binary and Git will handle the file
+appropriately.
++
+Unfortunately, the desired effect of cleaning up text files with
+mixed line endings and the undesired effect of corrupting binary
+files cannot be distinguished.  In both cases CRLFs are removed
+in an irreversible way.  For text files this is the right thing
+to do because CRLFs are line endings, while for binary files
+converting CRLFs corrupts data.
++
+Note, this safety check does not mean that a checkout will generate a
+file identical to the original file for a different setting of
+`core.eol` and `core.autocrlf`, but only for the current one.  For
+example, a text file with `LF` would be accepted with `core.eol=lf`
+and could later be checked out with `core.eol=crlf`, in which case the
+resulting file would contain `CRLF`, although the original file
+contained `LF`.  However, in both work trees the line endings would be
+consistent, that is either all `LF` or all `CRLF`, but never mixed.  A
+file with mixed line endings would be reported by the `core.safecrlf`
+mechanism.
+
+core.autocrlf::
+	Setting this variable to "true" is the same as setting
+	the `text` attribute to "auto" on all files and core.eol to "crlf".
+	Set to true if you want to have `CRLF` line endings in your
+	working directory and the repository has LF line endings.
+	This variable can be set to 'input',
+	in which case no output conversion is performed.
+
+core.checkRoundtripEncoding::
+	A comma and/or whitespace separated list of encodings that Git
+	performs UTF-8 round trip checks on if they are used in an
+	`working-tree-encoding` attribute (see linkgit:gitattributes[5]).
+	The default value is `SHIFT-JIS`.
+
+core.symlinks::
+	If false, symbolic links are checked out as small plain files that
+	contain the link text. linkgit:git-update-index[1] and
+	linkgit:git-add[1] will not change the recorded type to regular
+	file. Useful on filesystems like FAT that do not support
+	symbolic links.
++
+The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
+will probe and set core.symlinks false if appropriate when the repository
+is created.
+
+core.gitProxy::
+	A "proxy command" to execute (as 'command host port') instead
+	of establishing direct connection to the remote server when
+	using the Git protocol for fetching. If the variable value is
+	in the "COMMAND for DOMAIN" format, the command is applied only
+	on hostnames ending with the specified domain string. This variable
+	may be set multiple times and is matched in the given order;
+	the first match wins.
++
+Can be overridden by the `GIT_PROXY_COMMAND` environment variable
+(which always applies universally, without the special "for"
+handling).
++
+The special string `none` can be used as the proxy command to
+specify that no proxy be used for a given domain pattern.
+This is useful for excluding servers inside a firewall from
+proxy use, while defaulting to a common proxy for external domains.
+
+core.sshCommand::
+	If this variable is set, `git fetch` and `git push` will
+	use the specified command instead of `ssh` when they need to
+	connect to a remote system. The command is in the same form as
+	the `GIT_SSH_COMMAND` environment variable and is overridden
+	when the environment variable is set.
+
+core.ignoreStat::
+	If true, Git will avoid using lstat() calls to detect if files have
+	changed by setting the "assume-unchanged" bit for those tracked files
+	which it has updated identically in both the index and working tree.
++
+When files are modified outside of Git, the user will need to stage
+the modified files explicitly (e.g. see 'Examples' section in
+linkgit:git-update-index[1]).
+Git will not normally detect changes to those files.
++
+This is useful on systems where lstat() calls are very slow, such as
+CIFS/Microsoft Windows.
++
+False by default.
+
+core.preferSymlinkRefs::
+	Instead of the default "symref" format for HEAD
+	and other symbolic reference files, use symbolic links.
+	This is sometimes needed to work with old scripts that
+	expect HEAD to be a symbolic link.
+
+core.alternateRefsCommand::
+	When advertising tips of available history from an alternate, use the shell to
+	execute the specified command instead of linkgit:git-for-each-ref[1]. The
+	first argument is the absolute path of the alternate. Output must contain one
+	hex object id per line (i.e., the same as produced by `git for-each-ref
+	--format='%(objectname)'`).
++
+Note that you cannot generally put `git for-each-ref` directly into the config
+value, as it does not take a repository path as an argument (but you can wrap
+the command above in a shell script).
+
+core.alternateRefsPrefixes::
+	When listing references from an alternate, list only references that begin
+	with the given prefix. Prefixes match as if they were given as arguments to
+	linkgit:git-for-each-ref[1]. To list multiple prefixes, separate them with
+	whitespace. If `core.alternateRefsCommand` is set, setting
+	`core.alternateRefsPrefixes` has no effect.
+
+core.bare::
+	If true this repository is assumed to be 'bare' and has no
+	working directory associated with it.  If this is the case a
+	number of commands that require a working directory will be
+	disabled, such as linkgit:git-add[1] or linkgit:git-merge[1].
++
+This setting is automatically guessed by linkgit:git-clone[1] or
+linkgit:git-init[1] when the repository was created.  By default a
+repository that ends in "/.git" is assumed to be not bare (bare =
+false), while all other repositories are assumed to be bare (bare
+= true).
+
+core.worktree::
+	Set the path to the root of the working tree.
+	If `GIT_COMMON_DIR` environment variable is set, core.worktree
+	is ignored and not used for determining the root of working tree.
+	This can be overridden by the `GIT_WORK_TREE` environment
+	variable and the `--work-tree` command-line option.
+	The value can be an absolute path or relative to the path to
+	the .git directory, which is either specified by --git-dir
+	or GIT_DIR, or automatically discovered.
+	If --git-dir or GIT_DIR is specified but none of
+	--work-tree, GIT_WORK_TREE and core.worktree is specified,
+	the current working directory is regarded as the top level
+	of your working tree.
++
+Note that this variable is honored even when set in a configuration
+file in a ".git" subdirectory of a directory and its value differs
+from the latter directory (e.g. "/path/to/.git/config" has
+core.worktree set to "/different/path"), which is most likely a
+misconfiguration.  Running Git commands in the "/path/to" directory will
+still use "/different/path" as the root of the work tree and can cause
+confusion unless you know what you are doing (e.g. you are creating a
+read-only snapshot of the same index to a location different from the
+repository's usual working tree).
+
+core.logAllRefUpdates::
+	Enable the reflog. Updates to a ref <ref> is logged to the file
+	"`$GIT_DIR/logs/<ref>`", by appending the new and old
+	SHA-1, the date/time and the reason of the update, but
+	only when the file exists.  If this configuration
+	variable is set to `true`, missing "`$GIT_DIR/logs/<ref>`"
+	file is automatically created for branch heads (i.e. under
+	`refs/heads/`), remote refs (i.e. under `refs/remotes/`),
+	note refs (i.e. under `refs/notes/`), and the symbolic ref `HEAD`.
+	If it is set to `always`, then a missing reflog is automatically
+	created for any ref under `refs/`.
++
+This information can be used to determine what commit
+was the tip of a branch "2 days ago".
++
+This value is true by default in a repository that has
+a working directory associated with it, and false by
+default in a bare repository.
+
+core.repositoryFormatVersion::
+	Internal variable identifying the repository format and layout
+	version.
+
+core.sharedRepository::
+	When 'group' (or 'true'), the repository is made shareable between
+	several users in a group (making sure all the files and objects are
+	group-writable). When 'all' (or 'world' or 'everybody'), the
+	repository will be readable by all users, additionally to being
+	group-shareable. When 'umask' (or 'false'), Git will use permissions
+	reported by umask(2). When '0xxx', where '0xxx' is an octal number,
+	files in the repository will have this mode value. '0xxx' will override
+	user's umask value (whereas the other options will only override
+	requested parts of the user's umask value). Examples: '0660' will make
+	the repo read/write-able for the owner and group, but inaccessible to
+	others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a
+	repository that is group-readable but not group-writable.
+	See linkgit:git-init[1]. False by default.
+
+core.warnAmbiguousRefs::
+	If true, Git will warn you if the ref name you passed it is ambiguous
+	and might match multiple refs in the repository. True by default.
+
+core.compression::
+	An integer -1..9, indicating a default compression level.
+	-1 is the zlib default. 0 means no compression,
+	and 1..9 are various speed/size tradeoffs, 9 being slowest.
+	If set, this provides a default to other compression variables,
+	such as `core.looseCompression` and `pack.compression`.
+
+core.looseCompression::
+	An integer -1..9, indicating the compression level for objects that
+	are not in a pack file. -1 is the zlib default. 0 means no
+	compression, and 1..9 are various speed/size tradeoffs, 9 being
+	slowest.  If not set,  defaults to core.compression.  If that is
+	not set,  defaults to 1 (best speed).
+
+core.packedGitWindowSize::
+	Number of bytes of a pack file to map into memory in a
+	single mapping operation.  Larger window sizes may allow
+	your system to process a smaller number of large pack files
+	more quickly.  Smaller window sizes will negatively affect
+	performance due to increased calls to the operating system's
+	memory manager, but may improve performance when accessing
+	a large number of large pack files.
++
+Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
+MiB on 32 bit platforms and 1 GiB on 64 bit platforms.  This should
+be reasonable for all users/operating systems.  You probably do
+not need to adjust this value.
++
+Common unit suffixes of 'k', 'm', or 'g' are supported.
+
+core.packedGitLimit::
+	Maximum number of bytes to map simultaneously into memory
+	from pack files.  If Git needs to access more than this many
+	bytes at once to complete an operation it will unmap existing
+	regions to reclaim virtual address space within the process.
++
+Default is 256 MiB on 32 bit platforms and 32 TiB (effectively
+unlimited) on 64 bit platforms.
+This should be reasonable for all users/operating systems, except on
+the largest projects.  You probably do not need to adjust this value.
++
+Common unit suffixes of 'k', 'm', or 'g' are supported.
+
+core.deltaBaseCacheLimit::
+	Maximum number of bytes per thread to reserve for caching base objects
+	that may be referenced by multiple deltified objects.  By storing the
+	entire decompressed base objects in a cache Git is able
+	to avoid unpacking and decompressing frequently used base
+	objects multiple times.
++
+Default is 96 MiB on all platforms.  This should be reasonable
+for all users/operating systems, except on the largest projects.
+You probably do not need to adjust this value.
++
+Common unit suffixes of 'k', 'm', or 'g' are supported.
+
+core.bigFileThreshold::
+	The size of files considered "big", which as discussed below
+	changes the behavior of numerous git commands, as well as how
+	such files are stored within the repository. The default is
+	512 MiB. Common unit suffixes of 'k', 'm', or 'g' are
+	supported.
++
+Files above the configured limit will be:
++
+* Stored deflated in packfiles, without attempting delta compression.
++
+The default limit is primarily set with this use-case in mind. With it,
+most projects will have their source code and other text files delta
+compressed, but not larger binary media files.
++
+Storing large files without delta compression avoids excessive memory
+usage, at the slight expense of increased disk usage.
++
+* Will be treated as if they were labeled "binary" (see
+  linkgit:gitattributes[5]). e.g. linkgit:git-log[1] and
+  linkgit:git-diff[1] will not compute diffs for files above this limit.
++
+* Will generally be streamed when written, which avoids excessive
+memory usage, at the cost of some fixed overhead. Commands that make
+use of this include linkgit:git-archive[1],
+linkgit:git-fast-import[1], linkgit:git-index-pack[1],
+linkgit:git-unpack-objects[1] and linkgit:git-fsck[1].
+
+core.excludesFile::
+	Specifies the pathname to the file that contains patterns to
+	describe paths that are not meant to be tracked, in addition
+	to `.gitignore` (per-directory) and `.git/info/exclude`.
+	Defaults to `$XDG_CONFIG_HOME/git/ignore`.
+	If `$XDG_CONFIG_HOME` is either not set or empty, `$HOME/.config/git/ignore`
+	is used instead. See linkgit:gitignore[5].
+
+core.askPass::
+	Some commands (e.g. svn and http interfaces) that interactively
+	ask for a password can be told to use an external program given
+	via the value of this variable. Can be overridden by the `GIT_ASKPASS`
+	environment variable. If not set, fall back to the value of the
+	`SSH_ASKPASS` environment variable or, failing that, a simple password
+	prompt. The external program shall be given a suitable prompt as
+	command-line argument and write the password on its STDOUT.
+
+core.attributesFile::
+	In addition to `.gitattributes` (per-directory) and
+	`.git/info/attributes`, Git looks into this file for attributes
+	(see linkgit:gitattributes[5]). Path expansions are made the same
+	way as for `core.excludesFile`. Its default value is
+	`$XDG_CONFIG_HOME/git/attributes`. If `$XDG_CONFIG_HOME` is either not
+	set or empty, `$HOME/.config/git/attributes` is used instead.
+
+core.hooksPath::
+	By default Git will look for your hooks in the
+	`$GIT_DIR/hooks` directory. Set this to different path,
+	e.g. `/etc/git/hooks`, and Git will try to find your hooks in
+	that directory, e.g. `/etc/git/hooks/pre-receive` instead of
+	in `$GIT_DIR/hooks/pre-receive`.
++
+The path can be either absolute or relative. A relative path is
+taken as relative to the directory where the hooks are run (see
+the "DESCRIPTION" section of linkgit:githooks[5]).
++
+This configuration variable is useful in cases where you'd like to
+centrally configure your Git hooks instead of configuring them on a
+per-repository basis, or as a more flexible and centralized
+alternative to having an `init.templateDir` where you've changed
+default hooks.
+
+core.editor::
+	Commands such as `commit` and `tag` that let you edit
+	messages by launching an editor use the value of this
+	variable when it is set, and the environment variable
+	`GIT_EDITOR` is not set.  See linkgit:git-var[1].
+
+core.commentChar::
+core.commentString::
+	Commands such as `commit` and `tag` that let you edit
+	messages consider a line that begins with this character
+	commented, and removes them after the editor returns
+	(default '#').
++
+If set to "auto", `git-commit` would select a character that is not
+the beginning character of any line in existing commit messages.
++
+Note that these two variables are aliases of each other, and in modern
+versions of Git you are free to use a string (e.g., `//` or `⁑⁕⁑`) with
+`commentChar`. Versions of Git prior to v2.45.0 will ignore
+`commentString` but will reject a value of `commentChar` that consists
+of more than a single ASCII byte. If you plan to use your config with
+older and newer versions of Git, you may want to specify both:
++
+    [core]
+    # single character for older versions
+    commentChar = "#"
+    # string for newer versions (which will override commentChar
+    # because it comes later in the file)
+    commentString = "//"
+
+core.filesRefLockTimeout::
+	The length of time, in milliseconds, to retry when trying to
+	lock an individual reference. Value 0 means not to retry at
+	all; -1 means to try indefinitely. Default is 100 (i.e.,
+	retry for 100ms).
+
+core.packedRefsTimeout::
+	The length of time, in milliseconds, to retry when trying to
+	lock the `packed-refs` file. Value 0 means not to retry at
+	all; -1 means to try indefinitely. Default is 1000 (i.e.,
+	retry for 1 second).
+
+core.pager::
+	Text viewer for use by Git commands (e.g., 'less').  The value
+	is meant to be interpreted by the shell.  The order of preference
+	is the `$GIT_PAGER` environment variable, then `core.pager`
+	configuration, then `$PAGER`, and then the default chosen at
+	compile time (usually 'less').
++
+When the `LESS` environment variable is unset, Git sets it to `FRX`
+(if `LESS` environment variable is set, Git does not change it at
+all).  If you want to selectively override Git's default setting
+for `LESS`, you can set `core.pager` to e.g. `less -S`.  This will
+be passed to the shell by Git, which will translate the final
+command to `LESS=FRX less -S`. The environment does not set the
+`S` option but the command line does, instructing less to truncate
+long lines. Similarly, setting `core.pager` to `less -+F` will
+deactivate the `F` option specified by the environment from the
+command-line, deactivating the "quit if one screen" behavior of
+`less`.  One can specifically activate some flags for particular
+commands: for example, setting `pager.blame` to `less -S` enables
+line truncation only for `git blame`.
++
+Likewise, when the `LV` environment variable is unset, Git sets it
+to `-c`.  You can override this setting by exporting `LV` with
+another value or setting `core.pager` to `lv +c`.
+
+core.whitespace::
+	A comma separated list of common whitespace problems to
+	notice.  'git diff' will use `color.diff.whitespace` to
+	highlight them, and 'git apply --whitespace=error' will
+	consider them as errors.  You can prefix `-` to disable
+	any of them (e.g. `-trailing-space`):
++
+* `blank-at-eol` treats trailing whitespaces at the end of the line
+  as an error (enabled by default).
+* `space-before-tab` treats a space character that appears immediately
+  before a tab character in the initial indent part of the line as an
+  error (enabled by default).
+* `indent-with-non-tab` treats a line that is indented with space
+  characters instead of the equivalent tabs as an error (not enabled by
+  default).
+* `tab-in-indent` treats a tab character in the initial indent part of
+  the line as an error (not enabled by default).
+* `blank-at-eof` treats blank lines added at the end of file as an error
+  (enabled by default).
+* `trailing-space` is a short-hand to cover both `blank-at-eol` and
+  `blank-at-eof`.
+* `cr-at-eol` treats a carriage-return at the end of line as
+  part of the line terminator, i.e. with it, `trailing-space`
+  does not trigger if the character before such a carriage-return
+  is not a whitespace (not enabled by default).
+* `tabwidth=<n>` tells how many character positions a tab occupies; this
+  is relevant for `indent-with-non-tab` and when Git fixes `tab-in-indent`
+  errors. The default tab width is 8. Allowed values are 1 to 63.
+
+core.fsync::
+	A comma-separated list of components of the repository that
+	should be hardened via the core.fsyncMethod when created or
+	modified.  You can disable hardening of any component by
+	prefixing it with a '-'.  Items that are not hardened may be
+	lost in the event of an unclean	system shutdown. Unless you
+	have special requirements, it is recommended that you leave
+	this option empty or pick one of `committed`, `added`,
+	or `all`.
++
+When this configuration is encountered, the set of components starts with
+the platform default value, disabled components are removed, and additional
+components are added. `none` resets the state so that the platform default
+is ignored.
++
+The empty string resets the fsync configuration to the platform
+default. The default on most platforms is equivalent to
+`core.fsync=committed,-loose-object`, which has good performance,
+but risks losing recent work in the event of an unclean system shutdown.
++
+* `none` clears the set of fsynced components.
+* `loose-object` hardens objects added to the repo in loose-object form.
+* `pack` hardens objects added to the repo in packfile form.
+* `pack-metadata` hardens packfile bitmaps and indexes.
+* `commit-graph` hardens the commit-graph file.
+* `index` hardens the index when it is modified.
+* `objects` is an aggregate option that is equivalent to
+  `loose-object,pack`.
+* `reference` hardens references modified in the repo.
+* `derived-metadata` is an aggregate option that is equivalent to
+  `pack-metadata,commit-graph`.
+* `committed` is an aggregate option that is currently equivalent to
+  `objects`. This mode sacrifices some performance to ensure that work
+  that is committed to the repository with `git commit` or similar commands
+  is hardened.
+* `added` is an aggregate option that is currently equivalent to
+  `committed,index`. This mode sacrifices additional performance to
+  ensure that the results of commands like `git add` and similar operations
+  are hardened.
+* `all` is an aggregate option that syncs all individual components above.
+
+core.fsyncMethod::
+	A value indicating the strategy Git will use to harden repository data
+	using fsync and related primitives.
++
+* `fsync` uses the fsync() system call or platform equivalents.
+* `writeout-only` issues pagecache writeback requests, but depending on the
+  filesystem and storage hardware, data added to the repository may not be
+  durable in the event of a system crash. This is the default mode on macOS.
+* `batch` enables a mode that uses writeout-only flushes to stage multiple
+  updates in the disk writeback cache and then does a single full fsync of
+  a dummy file to trigger the disk cache flush at the end of the operation.
++
+Currently `batch` mode only applies to loose-object files. Other repository
+data is made durable as if `fsync` was specified. This mode is expected to
+be as safe as `fsync` on macOS for repos stored on HFS+ or APFS filesystems
+and on Windows for repos stored on NTFS or ReFS filesystems.
+
+core.fsyncObjectFiles::
+	This boolean will enable 'fsync()' when writing object files.
+	This setting is deprecated. Use core.fsync instead.
++
+This setting affects data added to the Git repository in loose-object
+form. When set to true, Git will issue an fsync or similar system call
+to flush caches so that loose-objects remain consistent in the face
+of a unclean system shutdown.
+
+core.preloadIndex::
+	Enable parallel index preload for operations like 'git diff'
++
+This can speed up operations like 'git diff' and 'git status' especially
+on filesystems like NFS that have weak caching semantics and thus
+relatively high IO latencies.  When enabled, Git will do the
+index comparison to the filesystem data in parallel, allowing
+overlapping IO's.  Defaults to true.
+
+core.unsetenvvars::
+	Windows-only: comma-separated list of environment variables'
+	names that need to be unset before spawning any other process.
+	Defaults to `PERL5LIB` to account for the fact that Git for
+	Windows insists on using its own Perl interpreter.
+
+core.restrictinheritedhandles::
+	Windows-only: override whether spawned processes inherit only standard
+	file handles (`stdin`, `stdout` and `stderr`) or all handles. Can be
+	`auto`, `true` or `false`. Defaults to `auto`, which means `true` on
+	Windows 7 and later, and `false` on older Windows versions.
+
+core.createObject::
+	You can set this to 'link', in which case a hardlink followed by
+	a delete of the source are used to make sure that object creation
+	will not overwrite existing objects.
++
+On some file system/operating system combinations, this is unreliable.
+Set this config setting to 'rename' there; however, this will remove the
+check that makes sure that existing object files will not get overwritten.
+
+core.notesRef::
+	When showing commit messages, also show notes which are stored in
+	the given ref.  The ref must be fully qualified.  If the given
+	ref does not exist, it is not an error but means that no
+	notes should be printed.
++
+This setting defaults to "refs/notes/commits", and it can be overridden by
+the `GIT_NOTES_REF` environment variable.  See linkgit:git-notes[1].
+
+core.commitGraph::
+	If true, then git will read the commit-graph file (if it exists)
+	to parse the graph structure of commits. Defaults to true. See
+	linkgit:git-commit-graph[1] for more information.
+
+core.useReplaceRefs::
+	If set to `false`, behave as if the `--no-replace-objects`
+	option was given on the command line. See linkgit:git[1] and
+	linkgit:git-replace[1] for more information.
+
+core.multiPackIndex::
+	Use the multi-pack-index file to track multiple packfiles using a
+	single index. See linkgit:git-multi-pack-index[1] for more
+	information. Defaults to true.
+
+core.sparseCheckout::
+	Enable "sparse checkout" feature. See linkgit:git-sparse-checkout[1]
+	for more information.
+
+core.sparseCheckoutCone::
+	Enables the "cone mode" of the sparse checkout feature. When the
+	sparse-checkout file contains a limited set of patterns, this
+	mode provides significant performance advantages. The "non-cone
+	mode" can be requested to allow specifying more flexible
+	patterns by setting this variable to 'false'. See
+	linkgit:git-sparse-checkout[1] for more information.
+
+core.abbrev::
+	Set the length object names are abbreviated to.  If
+	unspecified or set to "auto", an appropriate value is
+	computed based on the approximate number of packed objects
+	in your repository, which hopefully is enough for
+	abbreviated object names to stay unique for some time.
+	If set to "no", no abbreviation is made and the object names
+	are shown in their full length.
+	The minimum length is 4.
+
+core.maxTreeDepth::
+	The maximum depth Git is willing to recurse while traversing a
+	tree (e.g., "a/b/cde/f" has a depth of 4). This is a fail-safe
+	to allow Git to abort cleanly, and should not generally need to
+	be adjusted. When Git is compiled with MSVC, the default is 512.
+	Otherwise, the default is 2048.
+
+
+credential.helper::
+	Specify an external helper to be called when a username or
+	password credential is needed; the helper may consult external
+	storage to avoid prompting the user for the credentials. This is
+	normally the name of a credential helper with possible
+	arguments, but may also be an absolute path with arguments or, if
+	preceded by `!`, shell commands.
++
+Note that multiple helpers may be defined. See linkgit:gitcredentials[7]
+for details and examples.
+
+credential.useHttpPath::
+	When acquiring credentials, consider the "path" component of an http
+	or https URL to be important. Defaults to false. See
+	linkgit:gitcredentials[7] for more information.
+
+credential.username::
+	If no username is set for a network authentication, use this username
+	by default. See credential.<context>.* below, and
+	linkgit:gitcredentials[7].
+
+credential.<url>.*::
+	Any of the credential.* options above can be applied selectively to
+	some credentials. For example, "credential.https://example.com.username"
+	would set the default username only for https connections to
+	example.com. See linkgit:gitcredentials[7] for details on how URLs are
+	matched.
+
+credentialCache.ignoreSIGHUP::
+	Tell git-credential-cache--daemon to ignore SIGHUP, instead of quitting.
+
+credentialStore.lockTimeoutMS::
+	The length of time, in milliseconds, for git-credential-store to retry
+	when trying to lock the credentials file. A value of 0 means not to retry at
+	all; -1 means to try indefinitely. Default is 1000 (i.e., retry for
+	1s).
+
+
+diff.autoRefreshIndex::
+	When using 'git diff' to compare with work tree
+	files, do not consider stat-only changes as changed.
+	Instead, silently run `git update-index --refresh` to
+	update the cached stat information for paths whose
+	contents in the work tree match the contents in the
+	index.  This option defaults to true.  Note that this
+	affects only 'git diff' Porcelain, and not lower level
+	'diff' commands such as 'git diff-files'.
+
+diff.dirstat::
+	A comma separated list of `--dirstat` parameters specifying the
+	default behavior of the `--dirstat` option to linkgit:git-diff[1]
+	and friends. The defaults can be overridden on the command line
+	(using `--dirstat=<param1,param2,...>`). The fallback defaults
+	(when not changed by `diff.dirstat`) are `changes,noncumulative,3`.
+	The following parameters are available:
++
+--
+`changes`;;
+	Compute the dirstat numbers by counting the lines that have been
+	removed from the source, or added to the destination. This ignores
+	the amount of pure code movements within a file.  In other words,
+	rearranging lines in a file is not counted as much as other changes.
+	This is the default behavior when no parameter is given.
+`lines`;;
+	Compute the dirstat numbers by doing the regular line-based diff
+	analysis, and summing the removed/added line counts. (For binary
+	files, count 64-byte chunks instead, since binary files have no
+	natural concept of lines). This is a more expensive `--dirstat`
+	behavior than the `changes` behavior, but it does count rearranged
+	lines within a file as much as other changes. The resulting output
+	is consistent with what you get from the other `--*stat` options.
+`files`;;
+	Compute the dirstat numbers by counting the number of files changed.
+	Each changed file counts equally in the dirstat analysis. This is
+	the computationally cheapest `--dirstat` behavior, since it does
+	not have to look at the file contents at all.
+`cumulative`;;
+	Count changes in a child directory for the parent directory as well.
+	Note that when using `cumulative`, the sum of the percentages
+	reported may exceed 100%. The default (non-cumulative) behavior can
+	be specified with the `noncumulative` parameter.
+<limit>;;
+	An integer parameter specifies a cut-off percent (3% by default).
+	Directories contributing less than this percentage of the changes
+	are not shown in the output.
+--
++
+Example: The following will count changed files, while ignoring
+directories with less than 10% of the total amount of changed files,
+and accumulating child directory counts in the parent directories:
+`files,10,cumulative`.
+
+diff.statNameWidth::
+	Limit the width of the filename part in --stat output. If set, applies
+	to all commands generating --stat output except format-patch.
+
+diff.statGraphWidth::
+	Limit the width of the graph part in --stat output. If set, applies
+	to all commands generating --stat output except format-patch.
+
+diff.context::
+	Generate diffs with <n> lines of context instead of the default
+	of 3. This value is overridden by the -U option.
+
+diff.interHunkContext::
+	Show the context between diff hunks, up to the specified number
+	of lines, thereby fusing the hunks that are close to each other.
+	This value serves as the default for the `--inter-hunk-context`
+	command line option.
+
+diff.external::
+	If this config variable is set, diff generation is not
+	performed using the internal diff machinery, but using the
+	given command.  Can be overridden with the `GIT_EXTERNAL_DIFF'
+	environment variable.  The command is called with parameters
+	as described under "git Diffs" in linkgit:git[1].  Note: if
+	you want to use an external diff program only on a subset of
+	your files, you might want to use linkgit:gitattributes[5] instead.
+
+diff.trustExitCode::
+	If this boolean value is set to true then the
+	`diff.external` command is expected to return exit code
+	0 if it considers the input files to be equal or 1 if it
+	considers them to be different, like `diff(1)`.
+	If it is set to false, which is the default, then the command
+	is expected to return exit code 0 regardless of equality.
+	Any other exit code causes Git to report a fatal error.
+
+diff.ignoreSubmodules::
+	Sets the default value of --ignore-submodules. Note that this
+	affects only 'git diff' Porcelain, and not lower level 'diff'
+	commands such as 'git diff-files'. 'git checkout'
+	and 'git switch' also honor
+	this setting when reporting uncommitted changes. Setting it to
+	'all' disables the submodule summary normally shown by 'git commit'
+	and 'git status' when `status.submoduleSummary` is set unless it is
+	overridden by using the --ignore-submodules command-line option.
+	The 'git submodule' commands are not affected by this setting.
+	By default this is set to untracked so that any untracked
+	submodules are ignored.
+
+diff.mnemonicPrefix::
+	If set, 'git diff' uses a prefix pair that is different from the
+	standard "a/" and "b/" depending on what is being compared.  When
+	this configuration is in effect, reverse diff output also swaps
+	the order of the prefixes:
+`git diff`;;
+	compares the (i)ndex and the (w)ork tree;
+`git diff HEAD`;;
+	 compares a (c)ommit and the (w)ork tree;
+`git diff --cached`;;
+	compares a (c)ommit and the (i)ndex;
+`git diff HEAD:file1 file2`;;
+	compares an (o)bject and a (w)ork tree entity;
+`git diff --no-index a b`;;
+	compares two non-git things (1) and (2).
+
+diff.noPrefix::
+	If set, 'git diff' does not show any source or destination prefix.
+
+diff.srcPrefix::
+	If set, 'git diff' uses this source prefix. Defaults to "a/".
+
+diff.dstPrefix::
+	If set, 'git diff' uses this destination prefix. Defaults to "b/".
+
+diff.relative::
+	If set to 'true', 'git diff' does not show changes outside of the directory
+	and show pathnames relative to the current directory.
+
+diff.orderFile::
+	File indicating how to order files within a diff.
+	See the '-O' option to linkgit:git-diff[1] for details.
+	If `diff.orderFile` is a relative pathname, it is treated as
+	relative to the top of the working tree.
+
+diff.renameLimit::
+	The number of files to consider in the exhaustive portion of
+	copy/rename detection; equivalent to the 'git diff' option
+	`-l`.  If not set, the default value is currently 1000.  This
+	setting has no effect if rename detection is turned off.
+
+diff.renames::
+	Whether and how Git detects renames.  If set to "false",
+	rename detection is disabled. If set to "true", basic rename
+	detection is enabled.  If set to "copies" or "copy", Git will
+	detect copies, as well.  Defaults to true.  Note that this
+	affects only 'git diff' Porcelain like linkgit:git-diff[1] and
+	linkgit:git-log[1], and not lower level commands such as
+	linkgit:git-diff-files[1].
+
+diff.suppressBlankEmpty::
+	A boolean to inhibit the standard behavior of printing a space
+	before each empty output line. Defaults to false.
+
+diff.submodule::
+	Specify the format in which differences in submodules are
+	shown.  The "short" format just shows the names of the commits
+	at the beginning and end of the range. The "log" format lists
+	the commits in the range like linkgit:git-submodule[1] `summary`
+	does. The "diff" format shows an inline diff of the changed
+	contents of the submodule. Defaults to "short".
+
+diff.wordRegex::
+	A POSIX Extended Regular Expression used to determine what is a "word"
+	when performing word-by-word difference calculations.  Character
+	sequences that match the regular expression are "words", all other
+	characters are *ignorable* whitespace.
+
+diff.<driver>.command::
+	The custom diff driver command.  See linkgit:gitattributes[5]
+	for details.
+
+diff.<driver>.trustExitCode::
+	If this boolean value is set to true then the
+	`diff.<driver>.command` command is expected to return exit code
+	0 if it considers the input files to be equal or 1 if it
+	considers them to be different, like `diff(1)`.
+	If it is set to false, which is the default, then the command
+	is expected to return exit code 0 regardless of equality.
+	Any other exit code causes Git to report a fatal error.
+
+diff.<driver>.xfuncname::
+	The regular expression that the diff driver should use to
+	recognize the hunk header.  A built-in pattern may also be used.
+	See linkgit:gitattributes[5] for details.
+
+diff.<driver>.binary::
+	Set this option to true to make the diff driver treat files as
+	binary.  See linkgit:gitattributes[5] for details.
+
+diff.<driver>.textconv::
+	The command that the diff driver should call to generate the
+	text-converted version of a file.  The result of the
+	conversion is used to generate a human-readable diff.  See
+	linkgit:gitattributes[5] for details.
+
+diff.<driver>.wordRegex::
+	The regular expression that the diff driver should use to
+	split words in a line.  See linkgit:gitattributes[5] for
+	details.
+
+diff.<driver>.cachetextconv::
+	Set this option to true to make the diff driver cache the text
+	conversion outputs.  See linkgit:gitattributes[5] for details.
+
+ * araxis
+ * bc
+ * codecompare
+ * deltawalker
+ * diffmerge
+ * diffuse
+ * ecmerge
+ * emerge
+ * examdiff
+ * guiffy
+ * gvimdiff
+ * kdiff3
+ * kompare
+ * meld
+ * nvimdiff
+ * opendiff
+ * p4merge
+ * smerge
+ * tkdiff
+ * vimdiff
+ * winmerge
+ * xxdiff
+
+
+diff.indentHeuristic::
+	Set this option to `false` to disable the default heuristics
+	that shift diff hunk boundaries to make patches easier to read.
+
+diff.algorithm::
+	Choose a diff algorithm.  The variants are as follows:
++
+--
+`default`, `myers`;;
+	The basic greedy diff algorithm. Currently, this is the default.
+`minimal`;;
+	Spend extra time to make sure the smallest possible diff is
+	produced.
+`patience`;;
+	Use "patience diff" algorithm when generating patches.
+`histogram`;;
+	This algorithm extends the patience algorithm to "support
+	low-occurrence common elements".
+--
++
+
+diff.wsErrorHighlight::
+	Highlight whitespace errors in the `context`, `old` or `new`
+	lines of the diff.  Multiple values are separated by comma,
+	`none` resets previous values, `default` reset the list to
+	`new` and `all` is a shorthand for `old,new,context`.  The
+	whitespace errors are colored with `color.diff.whitespace`.
+	The command line option `--ws-error-highlight=<kind>`
+	overrides this setting.
+
+diff.colorMoved::
+	If set to either a valid `<mode>` or a true value, moved lines
+	in a diff are colored differently, for details of valid modes
+	see '--color-moved' in linkgit:git-diff[1]. If simply set to
+	true the default color mode will be used. When set to false,
+	moved lines are not colored.
+
+diff.colorMovedWS::
+	When moved lines are colored using e.g. the `diff.colorMoved` setting,
+	this option controls the `<mode>` how spaces are treated.
+	For details of valid modes see '--color-moved-ws' in linkgit:git-diff[1].
+
+
+diff.tool::
+	Controls which diff tool is used by linkgit:git-difftool[1].
+	This variable overrides the value configured in `merge.tool`.
+	The list below shows the valid built-in values.
+	Any other value is treated as a custom diff tool and requires
+	that a corresponding difftool.<tool>.cmd variable is defined.
+
+diff.guitool::
+	Controls which diff tool is used by linkgit:git-difftool[1] when
+	the -g/--gui flag is specified. This variable overrides the value
+	configured in `merge.guitool`. The list below shows the valid
+	built-in values. Any other value is treated as a custom diff tool
+	and requires that a corresponding difftool.<guitool>.cmd variable
+	is defined.
+
+difftool.<tool>.cmd::
+	Specify the command to invoke the specified diff tool.
+	The specified command is evaluated in shell with the following
+	variables available:  'LOCAL' is set to the name of the temporary
+	file containing the contents of the diff pre-image and 'REMOTE'
+	is set to the name of the temporary file containing the contents
+	of the diff post-image.
++
+See the `--tool=<tool>` option in linkgit:git-difftool[1] for more details.
+
+difftool.<tool>.path::
+	Override the path for the given tool.  This is useful in case
+	your tool is not in the PATH.
+
+difftool.trustExitCode::
+	Exit difftool if the invoked diff tool returns a non-zero exit status.
++
+See the `--trust-exit-code` option in linkgit:git-difftool[1] for more details.
+
+difftool.prompt::
+	Prompt before each invocation of the diff tool.
+
+difftool.guiDefault::
+	Set `true` to use the `diff.guitool` by default (equivalent to specifying
+	the `--gui` argument), or `auto` to select `diff.guitool` or `diff.tool`
+	depending on the presence of a `DISPLAY` environment variable value. The
+	default is `false`, where the `--gui` argument must be provided
+	explicitly for the `diff.guitool` to be used.
+
+
+extensions.objectFormat::
+	Specify the hash algorithm to use.  The acceptable values are `sha1` and
+	`sha256`.  If not specified, `sha1` is assumed.  It is an error to specify
+	this key unless `core.repositoryFormatVersion` is 1.
++
+Note that this setting should only be set by linkgit:git-init[1] or
+linkgit:git-clone[1].  Trying to change it after initialization will not
+work and will produce hard-to-diagnose issues.
+
+extensions.compatObjectFormat::
+
+	Specify a compatitbility hash algorithm to use.  The acceptable values
+	are `sha1` and `sha256`.  The value specified must be different from the
+	value of extensions.objectFormat.  This allows client level
+	interoperability between git repositories whose objectFormat matches
+	this compatObjectFormat.  In particular when fully implemented the
+	pushes and pulls from a repository in whose objectFormat matches
+	compatObjectFormat.  As well as being able to use oids encoded in
+	compatObjectFormat in addition to oids encoded with objectFormat to
+	locally specify objects.
+
+extensions.refStorage::
+	Specify the ref storage format to use. The acceptable values are:
++
+* `files` for loose files with packed-refs. This is the default.
+* `reftable` for the reftable format. This format is experimental and its
+  internals are subject to change.
+
++
+It is an error to specify this key unless `core.repositoryFormatVersion` is 1.
++
+Note that this setting should only be set by linkgit:git-init[1] or
+linkgit:git-clone[1]. Trying to change it after initialization will not
+work and will produce hard-to-diagnose issues.
+
+extensions.worktreeConfig::
+	If enabled, then worktrees will load config settings from the
+	`$GIT_DIR/config.worktree` file in addition to the
+	`$GIT_COMMON_DIR/config` file. Note that `$GIT_COMMON_DIR` and
+	`$GIT_DIR` are the same for the main working tree, while other
+	working trees have `$GIT_DIR` equal to
+	`$GIT_COMMON_DIR/worktrees/<id>/`. The settings in the
+	`config.worktree` file will override settings from any other
+	config files.
++
+When enabling `extensions.worktreeConfig`, you must be careful to move
+certain values from the common config file to the main working tree's
+`config.worktree` file, if present:
++
+* `core.worktree` must be moved from `$GIT_COMMON_DIR/config` to
+  `$GIT_COMMON_DIR/config.worktree`.
+* If `core.bare` is true, then it must be moved from `$GIT_COMMON_DIR/config`
+  to `$GIT_COMMON_DIR/config.worktree`.
++
+It may also be beneficial to adjust the locations of `core.sparseCheckout`
+and `core.sparseCheckoutCone` depending on your desire for customizable
+sparse-checkout settings for each worktree. By default, the `git
+sparse-checkout` builtin enables `extensions.worktreeConfig`, assigns
+these config values on a per-worktree basis, and uses the
+`$GIT_DIR/info/sparse-checkout` file to specify the sparsity for each
+worktree independently. See linkgit:git-sparse-checkout[1] for more
+details.
++
+For historical reasons, `extensions.worktreeConfig` is respected
+regardless of the `core.repositoryFormatVersion` setting.
+
+
+fastimport.unpackLimit::
+	If the number of objects imported by linkgit:git-fast-import[1]
+	is below this limit, then the objects will be unpacked into
+	loose object files.  However, if the number of imported objects
+	equals or exceeds this limit, then the pack will be stored as a
+	pack.  Storing the pack from a fast-import can make the import
+	operation complete faster, especially on slow filesystems.  If
+	not set, the value of `transfer.unpackLimit` is used instead.
+
+
+feature.*::
+	The config settings that start with `feature.` modify the defaults of
+	a group of other config settings. These groups are created by the Git
+	developer community as recommended defaults and are subject to change.
+	In particular, new config options may be added with different defaults.
+
+feature.experimental::
+	Enable config options that are new to Git, and are being considered for
+	future defaults. Config settings included here may be added or removed
+	with each release, including minor version updates. These settings may
+	have unintended interactions since they are so new. Please enable this
+	setting if you are interested in providing feedback on experimental
+	features. The new default values are:
++
+* `fetch.negotiationAlgorithm=skipping` may improve fetch negotiation times by
+skipping more commits at a time, reducing the number of round trips.
++
+* `pack.useBitmapBoundaryTraversal=true` may improve bitmap traversal times by
+walking fewer objects.
++
+* `pack.allowPackReuse=multi` may improve the time it takes to create a pack by
+reusing objects from multiple packs instead of just one.
+
+feature.manyFiles::
+	Enable config options that optimize for repos with many files in the
+	working directory. With many files, commands such as `git status` and
+	`git checkout` may be slow and these new defaults improve performance:
++
+* `index.skipHash=true` speeds up index writes by not computing a trailing
+  checksum. Note that this will cause Git versions earlier than 2.13.0 to
+  refuse to parse the index and Git versions earlier than 2.40.0 will report
+  a corrupted index during `git fsck`.
++
+* `index.version=4` enables path-prefix compression in the index.
++
+* `core.untrackedCache=true` enables the untracked cache. This setting assumes
+that mtime is working on your machine.
+
+
+fetch.recurseSubmodules::
+	This option controls whether `git fetch` (and the underlying fetch
+	in `git pull`) will recursively fetch into populated submodules.
+	This option can be set either to a boolean value or to 'on-demand'.
+	Setting it to a boolean changes the behavior of fetch and pull to
+	recurse unconditionally into submodules when set to true or to not
+	recurse at all when set to false. When set to 'on-demand', fetch and
+	pull will only recurse into a populated submodule when its
+	superproject retrieves a commit that updates the submodule's
+	reference.
+	Defaults to 'on-demand', or to the value of 'submodule.recurse' if set.
+
+fetch.fsckObjects::
+	If it is set to true, git-fetch-pack will check all fetched
+	objects. See `transfer.fsckObjects` for what's
+	checked. Defaults to false. If not set, the value of
+	`transfer.fsckObjects` is used instead.
+
+fetch.fsck.<msg-id>::
+	Acts like `fsck.<msg-id>`, but is used by
+	linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See
+	the `fsck.<msg-id>` documentation for details.
+
+fetch.fsck.skipList::
+	Acts like `fsck.skipList`, but is used by
+	linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See
+	the `fsck.skipList` documentation for details.
+
+fetch.unpackLimit::
+	If the number of objects fetched over the Git native
+	transfer is below this
+	limit, then the objects will be unpacked into loose object
+	files. However if the number of received objects equals or
+	exceeds this limit then the received pack will be stored as
+	a pack, after adding any missing delta bases.  Storing the
+	pack from a push can make the push operation complete faster,
+	especially on slow filesystems.  If not set, the value of
+	`transfer.unpackLimit` is used instead.
+
+fetch.prune::
+	If true, fetch will automatically behave as if the `--prune`
+	option was given on the command line.  See also `remote.<name>.prune`
+	and the PRUNING section of linkgit:git-fetch[1].
+
+fetch.pruneTags::
+	If true, fetch will automatically behave as if the
+	`refs/tags/*:refs/tags/*` refspec was provided when pruning,
+	if not set already. This allows for setting both this option
+	and `fetch.prune` to maintain a 1=1 mapping to upstream
+	refs. See also `remote.<name>.pruneTags` and the PRUNING
+	section of linkgit:git-fetch[1].
+
+fetch.all::
+	If true, fetch will attempt to update all available remotes.
+	This behavior can be overridden by passing `--no-all` or by
+	explicitly specifying one or more remote(s) to fetch from.
+	Defaults to false.
+
+fetch.output::
+	Control how ref update status is printed. Valid values are
+	`full` and `compact`. Default value is `full`. See the
+	OUTPUT section in linkgit:git-fetch[1] for details.
+
+fetch.negotiationAlgorithm::
+	Control how information about the commits in the local repository
+	is sent when negotiating the contents of the packfile to be sent by
+	the server.  Set to "consecutive" to use an algorithm that walks
+	over consecutive commits checking each one.  Set to "skipping" to
+	use an algorithm that skips commits in an effort to converge
+	faster, but may result in a larger-than-necessary packfile; or set
+	to "noop" to not send any information at all, which will almost
+	certainly result in a larger-than-necessary packfile, but will skip
+	the negotiation step.  Set to "default" to override settings made
+	previously and use the default behaviour.  The default is normally
+	"consecutive", but if `feature.experimental` is true, then the
+	default is "skipping".  Unknown values will cause 'git fetch' to
+	error out.
++
+See also the `--negotiate-only` and `--negotiation-tip` options to
+linkgit:git-fetch[1].
+
+fetch.showForcedUpdates::
+	Set to false to enable `--no-show-forced-updates` in
+	linkgit:git-fetch[1] and linkgit:git-pull[1] commands.
+	Defaults to true.
+
+fetch.parallel::
+	Specifies the maximal number of fetch operations to be run in parallel
+	at a time (submodules, or remotes when the `--multiple` option of
+	linkgit:git-fetch[1] is in effect).
++
+A value of 0 will give some reasonable default. If unset, it defaults to 1.
++
+For submodules, this setting can be overridden using the `submodule.fetchJobs`
+config setting.
+
+fetch.writeCommitGraph::
+	Set to true to write a commit-graph after every `git fetch` command
+	that downloads a pack-file from a remote. Using the `--split` option,
+	most executions will create a very small commit-graph file on top of
+	the existing commit-graph file(s). Occasionally, these files will
+	merge and the write may take longer. Having an updated commit-graph
+	file helps performance of many Git commands, including `git merge-base`,
+	`git push -f`, and `git log --graph`. Defaults to false.
+
+fetch.bundleURI::
+	This value stores a URI for downloading Git object data from a bundle
+	URI before performing an incremental fetch from the origin Git server.
+	This is similar to how the `--bundle-uri` option behaves in
+	linkgit:git-clone[1]. `git clone --bundle-uri` will set the
+	`fetch.bundleURI` value if the supplied bundle URI contains a bundle
+	list that is organized for incremental fetches.
++
+If you modify this value and your repository has a `fetch.bundleCreationToken`
+value, then remove that `fetch.bundleCreationToken` value before fetching from
+the new bundle URI.
+
+fetch.bundleCreationToken::
+	When using `fetch.bundleURI` to fetch incrementally from a bundle
+	list that uses the "creationToken" heuristic, this config value
+	stores the maximum `creationToken` value of the downloaded bundles.
+	This value is used to prevent downloading bundles in the future
+	if the advertised `creationToken` is not strictly larger than this
+	value.
++
+The creation token values are chosen by the provider serving the specific
+bundle URI. If you modify the URI at `fetch.bundleURI`, then be sure to
+remove the value for the `fetch.bundleCreationToken` value before fetching.
+
+
+filter.<driver>.clean::
+	The command which is used to convert the content of a worktree
+	file to a blob upon checkin.  See linkgit:gitattributes[5] for
+	details.
+
+filter.<driver>.smudge::
+	The command which is used to convert the content of a blob
+	object to a worktree file upon checkout.  See
+	linkgit:gitattributes[5] for details.
+
+
+format.attach::
+	Enable multipart/mixed attachments as the default for
+	'format-patch'.  The value can also be a double quoted string
+	which will enable attachments as the default and set the
+	value as the boundary.  See the --attach option in
+	linkgit:git-format-patch[1].  To countermand an earlier
+	value, set it to an empty string.
+
+format.from::
+	Provides the default value for the `--from` option to format-patch.
+	Accepts a boolean value, or a name and email address.  If false,
+	format-patch defaults to `--no-from`, using commit authors directly in
+	the "From:" field of patch mails.  If true, format-patch defaults to
+	`--from`, using your committer identity in the "From:" field of patch
+	mails and including a "From:" field in the body of the patch mail if
+	different.  If set to a non-boolean value, format-patch uses that
+	value instead of your committer identity.  Defaults to false.
+
+format.forceInBodyFrom::
+	Provides the default value for the `--[no-]force-in-body-from`
+	option to format-patch.  Defaults to false.
+
+format.numbered::
+	A boolean which can enable or disable sequence numbers in patch
+	subjects.  It defaults to "auto" which enables it only if there
+	is more than one patch.  It can be enabled or disabled for all
+	messages by setting it to "true" or "false".  See --numbered
+	option in linkgit:git-format-patch[1].
+
+format.headers::
+	Additional email headers to include in a patch to be submitted
+	by mail.  See linkgit:git-format-patch[1].
+
+format.to::
+format.cc::
+	Additional recipients to include in a patch to be submitted
+	by mail.  See the --to and --cc options in
+	linkgit:git-format-patch[1].
+
+format.subjectPrefix::
+	The default for format-patch is to output files with the '[PATCH]'
+	subject prefix. Use this variable to change that prefix.
+
+format.coverFromDescription::
+	The default mode for format-patch to determine which parts of
+	the cover letter will be populated using the branch's
+	description. See the `--cover-from-description` option in
+	linkgit:git-format-patch[1].
+
+format.signature::
+	The default for format-patch is to output a signature containing
+	the Git version number. Use this variable to change that default.
+	Set this variable to the empty string ("") to suppress
+	signature generation.
+
+format.signatureFile::
+	Works just like format.signature except the contents of the
+	file specified by this variable will be used as the signature.
+
+format.suffix::
+	The default for format-patch is to output files with the suffix
+	`.patch`. Use this variable to change that suffix (make sure to
+	include the dot if you want it).
+
+format.encodeEmailHeaders::
+	Encode email headers that have non-ASCII characters with
+	"Q-encoding" (described in RFC 2047) for email transmission.
+	Defaults to true.
+
+format.pretty::
+	The default pretty format for log/show/whatchanged command.
+	See linkgit:git-log[1], linkgit:git-show[1],
+	linkgit:git-whatchanged[1].
+
+format.thread::
+	The default threading style for 'git format-patch'.  Can be
+	a boolean value, or `shallow` or `deep`.  `shallow` threading
+	makes every mail a reply to the head of the series,
+	where the head is chosen from the cover letter, the
+	`--in-reply-to`, and the first patch mail, in this order.
+	`deep` threading makes every mail a reply to the previous one.
+	A true boolean value is the same as `shallow`, and a false
+	value disables threading.
+
+format.signOff::
+	A boolean value which lets you enable the `-s/--signoff` option of
+	format-patch by default. *Note:* Adding the `Signed-off-by` trailer to a
+	patch should be a conscious act and means that you certify you have
+	the rights to submit this work under the same open source license.
+	Please see the 'SubmittingPatches' document for further discussion.
+
+format.coverLetter::
+	A boolean that controls whether to generate a cover-letter when
+	format-patch is invoked, but in addition can be set to "auto", to
+	generate a cover-letter only when there's more than one patch.
+	Default is false.
+
+format.outputDirectory::
+	Set a custom directory to store the resulting files instead of the
+	current working directory. All directory components will be created.
+
+format.filenameMaxLength::
+	The maximum length of the output filenames generated by the
+	`format-patch` command; defaults to 64.  Can be overridden
+	by the `--filename-max-length=<n>` command line option.
+
+format.useAutoBase::
+	A boolean value which lets you enable the `--base=auto` option of
+	format-patch by default. Can also be set to "whenAble" to allow
+	enabling `--base=auto` if a suitable base is available, but to skip
+	adding base info otherwise without the format dying.
+
+format.notes::
+	Provides the default value for the `--notes` option to
+	format-patch. Accepts a boolean value, or a ref which specifies
+	where to get notes. If false, format-patch defaults to
+	`--no-notes`. If true, format-patch defaults to `--notes`. If
+	set to a non-boolean value, format-patch defaults to
+	`--notes=<ref>`, where `ref` is the non-boolean value. Defaults
+	to false.
++
+If one wishes to use the ref `refs/notes/true`, please use that literal
+instead.
++
+This configuration can be specified multiple times in order to allow
+multiple notes refs to be included. In that case, it will behave
+similarly to multiple `--[no-]notes[=]` options passed in. That is, a
+value of `true` will show the default notes, a value of `<ref>` will
+also show notes from that notes ref and a value of `false` will negate
+previous configurations and not show notes.
++
+For example,
++
+------------
+[format]
+	notes = true
+	notes = foo
+	notes = false
+	notes = bar
+------------
++
+will only show notes from `refs/notes/bar`.
+
+format.mboxrd::
+	A boolean value which enables the robust "mboxrd" format when
+	`--stdout` is in use to escape "^>+From " lines.
+
+format.noprefix::
+	If set, do not show any source or destination prefix in patches.
+	This is equivalent to the `diff.noprefix` option used by `git
+	diff` (but which is not respected by `format-patch`). Note that
+	by setting this, the receiver of any patches you generate will
+	have to apply them using the `-p0` option.
+
+
+fsck.<msg-id>::
+	During fsck git may find issues with legacy data which
+	wouldn't be generated by current versions of git, and which
+	wouldn't be sent over the wire if `transfer.fsckObjects` was
+	set. This feature is intended to support working with legacy
+	repositories containing such data.
++
+Setting `fsck.<msg-id>` will be picked up by linkgit:git-fsck[1], but
+to accept pushes of such data set `receive.fsck.<msg-id>` instead, or
+to clone or fetch it set `fetch.fsck.<msg-id>`.
++
+The rest of the documentation discusses `fsck.*` for brevity, but the
+same applies for the corresponding `receive.fsck.*` and
+`fetch.fsck.*`. variables.
++
+Unlike variables like `color.ui` and `core.editor`, the
+`receive.fsck.<msg-id>` and `fetch.fsck.<msg-id>` variables will not
+fall back on the `fsck.<msg-id>` configuration if they aren't set. To
+uniformly configure the same fsck settings in different circumstances,
+all three of them must be set to the same values.
++
+When `fsck.<msg-id>` is set, errors can be switched to warnings and
+vice versa by configuring the `fsck.<msg-id>` setting where the
+`<msg-id>` is the fsck message ID and the value is one of `error`,
+`warn` or `ignore`. For convenience, fsck prefixes the error/warning
+with the message ID, e.g. "missingEmail: invalid author/committer
+line - missing email" means that setting `fsck.missingEmail = ignore`
+will hide that issue.
++
+In general, it is better to enumerate existing objects with problems
+with `fsck.skipList`, instead of listing the kind of breakages these
+problematic objects share to be ignored, as doing the latter will
+allow new instances of the same breakages go unnoticed.
++
+Setting an unknown `fsck.<msg-id>` value will cause fsck to die, but
+doing the same for `receive.fsck.<msg-id>` and `fetch.fsck.<msg-id>`
+will only cause git to warn.
++
+See the `Fsck Messages` section of linkgit:git-fsck[1] for supported
+values of `<msg-id>`.
+
+
+fsck.skipList::
+	The path to a list of object names (i.e. one unabbreviated SHA-1 per
+	line) that are known to be broken in a non-fatal way and should
+	be ignored. On versions of Git 2.20 and later, comments ('#'), empty
+	lines, and any leading and trailing whitespace are ignored. Everything
+	but a SHA-1 per line will error out on older versions.
++
+This feature is useful when an established project should be accepted
+despite early commits containing errors that can be safely ignored,
+such as invalid committer email addresses.  Note: corrupt objects
+cannot be skipped with this setting.
++
+Like `fsck.<msg-id>` this variable has corresponding
+`receive.fsck.skipList` and `fetch.fsck.skipList` variants.
++
+Unlike variables like `color.ui` and `core.editor` the
+`receive.fsck.skipList` and `fetch.fsck.skipList` variables will not
+fall back on the `fsck.skipList` configuration if they aren't set. To
+uniformly configure the same fsck settings in different circumstances,
+all three of them must be set to the same values.
++
+Older versions of Git (before 2.20) documented that the object names
+list should be sorted. This was never a requirement; the object names
+could appear in any order, but when reading the list we tracked whether
+the list was sorted for the purposes of an internal binary search
+implementation, which could save itself some work with an already sorted
+list. Unless you had a humongous list there was no reason to go out of
+your way to pre-sort the list. After Git version 2.20 a hash implementation
+is used instead, so there's now no reason to pre-sort the list.
+
+
+fsmonitor.allowRemote::
+    By default, the fsmonitor daemon refuses to work with network-mounted
+    repositories. Setting `fsmonitor.allowRemote` to `true` overrides this
+    behavior.  Only respected when `core.fsmonitor` is set to `true`.
+
+fsmonitor.socketDir::
+    This Mac OS-specific option, if set, specifies the directory in
+    which to create the Unix domain socket used for communication
+    between the fsmonitor daemon and various Git commands. The directory must
+    reside on a native Mac OS filesystem.  Only respected when `core.fsmonitor`
+    is set to `true`.
+
+
+gc.aggressiveDepth::
+	The depth parameter used in the delta compression
+	algorithm used by 'git gc --aggressive'.  This defaults
+	to 50, which is the default for the `--depth` option when
+	`--aggressive` isn't in use.
++
+See the documentation for the `--depth` option in
+linkgit:git-repack[1] for more details.
+
+gc.aggressiveWindow::
+	The window size parameter used in the delta compression
+	algorithm used by 'git gc --aggressive'.  This defaults
+	to 250, which is a much more aggressive window size than
+	the default `--window` of 10.
++
+See the documentation for the `--window` option in
+linkgit:git-repack[1] for more details.
+
+gc.auto::
+	When there are approximately more than this many loose
+	objects in the repository, `git gc --auto` will pack them.
+	Some Porcelain commands use this command to perform a
+	light-weight garbage collection from time to time.  The
+	default value is 6700.
++
+Setting this to 0 disables not only automatic packing based on the
+number of loose objects, but also any other heuristic `git gc --auto` will
+otherwise use to determine if there's work to do, such as
+`gc.autoPackLimit`.
+
+gc.autoPackLimit::
+	When there are more than this many packs that are not
+	marked with `*.keep` file in the repository, `git gc
+	--auto` consolidates them into one larger pack.  The
+	default value is 50.  Setting this to 0 disables it.
+	Setting `gc.auto` to 0 will also disable this.
++
+See the `gc.bigPackThreshold` configuration variable below. When in
+use, it'll affect how the auto pack limit works.
+
+gc.autoDetach::
+	Make `git gc --auto` return immediately and run in the background
+	if the system supports it. Default is true.
+
+gc.bigPackThreshold::
+	If non-zero, all non-cruft packs larger than this limit are kept
+	when `git gc` is run. This is very similar to
+	`--keep-largest-pack` except that all non-cruft packs that meet
+	the threshold are kept, not just the largest pack. Defaults to
+	zero. Common unit suffixes of 'k', 'm', or 'g' are supported.
++
+Note that if the number of kept packs is more than gc.autoPackLimit,
+this configuration variable is ignored, all packs except the base pack
+will be repacked. After this the number of packs should go below
+gc.autoPackLimit and gc.bigPackThreshold should be respected again.
++
+If the amount of memory estimated for `git repack` to run smoothly is
+not available and `gc.bigPackThreshold` is not set, the largest pack
+will also be excluded (this is the equivalent of running `git gc` with
+`--keep-largest-pack`).
+
+gc.writeCommitGraph::
+	If true, then gc will rewrite the commit-graph file when
+	linkgit:git-gc[1] is run. When using `git gc --auto`
+	the commit-graph will be updated if housekeeping is
+	required. Default is true. See linkgit:git-commit-graph[1]
+	for details.
+
+gc.logExpiry::
+	If the file gc.log exists, then `git gc --auto` will print
+	its content and exit with status zero instead of running
+	unless that file is more than 'gc.logExpiry' old.  Default is
+	"1.day".  See `gc.pruneExpire` for more ways to specify its
+	value.
+
+gc.packRefs::
+	Running `git pack-refs` in a repository renders it
+	unclonable by Git versions prior to 1.5.1.2 over dumb
+	transports such as HTTP.  This variable determines whether
+	'git gc' runs `git pack-refs`. This can be set to `notbare`
+	to enable it within all non-bare repos or it can be set to a
+	boolean value.  The default is `true`.
+
+gc.cruftPacks::
+	Store unreachable objects in a cruft pack (see
+	linkgit:git-repack[1]) instead of as loose objects. The default
+	is `true`.
+
+gc.maxCruftSize::
+	Limit the size of new cruft packs when repacking. When
+	specified in addition to `--max-cruft-size`, the command line
+	option takes priority. See the `--max-cruft-size` option of
+	linkgit:git-repack[1].
+
+gc.pruneExpire::
+	When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'
+	(and 'repack --cruft --cruft-expiration 2.weeks.ago' if using
+	cruft packs via `gc.cruftPacks` or `--cruft`).  Override the
+	grace period with this config variable.  The value "now" may be
+	used to disable this grace period and always prune unreachable
+	objects immediately, or "never" may be used to suppress pruning.
+	This feature helps prevent corruption when 'git gc' runs
+	concurrently with another process writing to the repository; see
+	the "NOTES" section of linkgit:git-gc[1].
+
+gc.worktreePruneExpire::
+	When 'git gc' is run, it calls
+	'git worktree prune --expire 3.months.ago'.
+	This config variable can be used to set a different grace
+	period. The value "now" may be used to disable the grace
+	period and prune `$GIT_DIR/worktrees` immediately, or "never"
+	may be used to suppress pruning.
+
+gc.reflogExpire::
+gc.<pattern>.reflogExpire::
+	'git reflog expire' removes reflog entries older than
+	this time; defaults to 90 days. The value "now" expires all
+	entries immediately, and "never" suppresses expiration
+	altogether. With "<pattern>" (e.g.
+	"refs/stash") in the middle the setting applies only to
+	the refs that match the <pattern>.
+
+gc.reflogExpireUnreachable::
+gc.<pattern>.reflogExpireUnreachable::
+	'git reflog expire' removes reflog entries older than
+	this time and are not reachable from the current tip;
+	defaults to 30 days. The value "now" expires all entries
+	immediately, and "never" suppresses expiration altogether.
+	With "<pattern>" (e.g. "refs/stash")
+	in the middle, the setting applies only to the refs that
+	match the <pattern>.
++
+These types of entries are generally created as a result of using `git
+commit --amend` or `git rebase` and are the commits prior to the amend
+or rebase occurring.  Since these changes are not part of the current
+project most users will want to expire them sooner, which is why the
+default is more aggressive than `gc.reflogExpire`.
+
+gc.recentObjectsHook::
+	When considering whether or not to remove an object (either when
+	generating a cruft pack or storing unreachable objects as
+	loose), use the shell to execute the specified command(s).
+	Interpret their output as object IDs which Git will consider as
+	"recent", regardless of their age. By treating their mtimes as
+	"now", any objects (and their descendants) mentioned in the
+	output will be kept regardless of their true age.
++
+Output must contain exactly one hex object ID per line, and nothing
+else. Objects which cannot be found in the repository are ignored.
+Multiple hooks are supported, but all must exit successfully, else the
+operation (either generating a cruft pack or unpacking unreachable
+objects) will be halted.
+
+gc.repackFilter::
+	When repacking, use the specified filter to move certain
+	objects into a separate packfile.  See the
+	`--filter=<filter-spec>` option of linkgit:git-repack[1].
+
+gc.repackFilterTo::
+	When repacking and using a filter, see `gc.repackFilter`, the
+	specified location will be used to create the packfile
+	containing the filtered out objects. **WARNING:** The
+	specified location should be accessible, using for example the
+	Git alternates mechanism, otherwise the repo could be
+	considered corrupt by Git as it migh not be able to access the
+	objects in that packfile. See the `--filter-to=<dir>` option
+	of linkgit:git-repack[1] and the `objects/info/alternates`
+	section of linkgit:gitrepository-layout[5].
+
+gc.rerereResolved::
+	Records of conflicted merge you resolved earlier are
+	kept for this many days when 'git rerere gc' is run.
+	You can also use more human-readable "1.month.ago", etc.
+	The default is 60 days.  See linkgit:git-rerere[1].
+
+gc.rerereUnresolved::
+	Records of conflicted merge you have not resolved are
+	kept for this many days when 'git rerere gc' is run.
+	You can also use more human-readable "1.month.ago", etc.
+	The default is 15 days.  See linkgit:git-rerere[1].
+
+
+gitcvs.commitMsgAnnotation::
+	Append this string to each commit message. Set to empty string
+	to disable this feature. Defaults to "via git-CVS emulator".
+
+gitcvs.enabled::
+	Whether the CVS server interface is enabled for this repository.
+	See linkgit:git-cvsserver[1].
+
+gitcvs.logFile::
+	Path to a log file where the CVS server interface well... logs
+	various stuff. See linkgit:git-cvsserver[1].
+
+gitcvs.usecrlfattr::
+	If true, the server will look up the end-of-line conversion
+	attributes for files to determine the `-k` modes to use. If
+	the attributes force Git to treat a file as text,
+	the `-k` mode will be left blank so CVS clients will
+	treat it as text. If they suppress text conversion, the file
+	will be set with '-kb' mode, which suppresses any newline munging
+	the client might otherwise do. If the attributes do not allow
+	the file type to be determined, then `gitcvs.allBinary` is
+	used. See linkgit:gitattributes[5].
+
+gitcvs.allBinary::
+	This is used if `gitcvs.usecrlfattr` does not resolve
+	the correct '-kb' mode to use. If true, all
+	unresolved files are sent to the client in
+	mode '-kb'. This causes the client to treat them
+	as binary files, which suppresses any newline munging it
+	otherwise might do. Alternatively, if it is set to "guess",
+	then the contents of the file are examined to decide if
+	it is binary, similar to `core.autocrlf`.
+
+gitcvs.dbName::
+	Database used by git-cvsserver to cache revision information
+	derived from the Git repository. The exact meaning depends on the
+	used database driver, for SQLite (which is the default driver) this
+	is a filename. Supports variable substitution (see
+	linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).
+	Default: '%Ggitcvs.%m.sqlite'
+
+gitcvs.dbDriver::
+	Used Perl DBI driver. You can specify any available driver
+	for this here, but it might not work. git-cvsserver is tested
+	with 'DBD::SQLite', reported to work with 'DBD::Pg', and
+	reported *not* to work with 'DBD::mysql'. Experimental feature.
+	May not contain double colons (`:`). Default: 'SQLite'.
+	See linkgit:git-cvsserver[1].
+
+gitcvs.dbUser, gitcvs.dbPass::
+	Database user and password. Only useful if setting `gitcvs.dbDriver`,
+	since SQLite has no concept of database users and/or passwords.
+	'gitcvs.dbUser' supports variable substitution (see
+	linkgit:git-cvsserver[1] for details).
+
+gitcvs.dbTableNamePrefix::
+	Database table name prefix.  Prepended to the names of any
+	database tables used, allowing a single database to be used
+	for several repositories.  Supports variable substitution (see
+	linkgit:git-cvsserver[1] for details).  Any non-alphabetic
+	characters will be replaced with underscores.
+
+All gitcvs variables except for `gitcvs.usecrlfattr` and
+`gitcvs.allBinary` can also be specified as
+'gitcvs.<access_method>.<varname>' (where 'access_method'
+is one of "ext" and "pserver") to make them apply only for the given
+access method.
+
+
+gitweb.category::
+gitweb.description::
+gitweb.owner::
+gitweb.url::
+	See linkgit:gitweb[1] for description.
+
+gitweb.avatar::
+gitweb.blame::
+gitweb.grep::
+gitweb.highlight::
+gitweb.patches::
+gitweb.pickaxe::
+gitweb.remote_heads::
+gitweb.showSizes::
+gitweb.snapshot::
+	See linkgit:gitweb.conf[5] for description.
+
+
+gpg.program::
+	Use this custom program instead of "`gpg`" found on `$PATH` when
+	making or verifying a PGP signature. The program must support the
+	same command-line interface as GPG, namely, to verify a detached
+	signature, "`gpg --verify $signature - <$file`" is run, and the
+	program is expected to signal a good signature by exiting with
+	code 0.  To generate an ASCII-armored detached signature, the
+	standard input of "`gpg -bsau $key`" is fed with the contents to be
+	signed, and the program is expected to send the result to its
+	standard output.
+
+gpg.format::
+	Specifies which key format to use when signing with `--gpg-sign`.
+	Default is "openpgp". Other possible values are "x509", "ssh".
++
+See linkgit:gitformat-signature[5] for the signature format, which differs
+based on the selected `gpg.format`.
+
+gpg.<format>.program::
+	Use this to customize the program used for the signing format you
+	chose. (see `gpg.program` and `gpg.format`) `gpg.program` can still
+	be used as a legacy synonym for `gpg.openpgp.program`. The default
+	value for `gpg.x509.program` is "gpgsm" and `gpg.ssh.program` is "ssh-keygen".
+
+gpg.minTrustLevel::
+	Specifies a minimum trust level for signature verification.  If
+	this option is unset, then signature verification for merge
+	operations requires a key with at least `marginal` trust.  Other
+	operations that perform signature verification require a key
+	with at least `undefined` trust.  Setting this option overrides
+	the required trust-level for all operations.  Supported values,
+	in increasing order of significance:
++
+* `undefined`
+* `never`
+* `marginal`
+* `fully`
+* `ultimate`
+
+gpg.ssh.defaultKeyCommand::
+	This command will be run when user.signingkey is not set and a ssh
+	signature is requested. On successful exit a valid ssh public key
+	prefixed with `key::` is expected in the first line of its output.
+	This allows for a script doing a dynamic lookup of the correct public
+	key when it is impractical to statically configure `user.signingKey`.
+	For example when keys or SSH Certificates are rotated frequently or
+	selection of the right key depends on external factors unknown to git.
+
+gpg.ssh.allowedSignersFile::
+	A file containing ssh public keys which you are willing to trust.
+	The file consists of one or more lines of principals followed by an ssh
+	public key.
+	e.g.: `user1@example.com,user2@example.com ssh-rsa AAAAX1...`
+	See ssh-keygen(1) "ALLOWED SIGNERS" for details.
+	The principal is only used to identify the key and is available when
+	verifying a signature.
++
+SSH has no concept of trust levels like gpg does. To be able to differentiate
+between valid signatures and trusted signatures the trust level of a signature
+verification is set to `fully` when the public key is present in the allowedSignersFile.
+Otherwise the trust level is `undefined` and git verify-commit/tag will fail.
++
+This file can be set to a location outside of the repository and every developer
+maintains their own trust store. A central repository server could generate this
+file automatically from ssh keys with push access to verify the code against.
+In a corporate setting this file is probably generated at a global location
+from automation that already handles developer ssh keys.
++
+A repository that only allows signed commits can store the file
+in the repository itself using a path relative to the top-level of the working tree.
+This way only committers with an already valid key can add or change keys in the keyring.
++
+Since OpensSSH 8.8 this file allows specifying a key lifetime using valid-after &
+valid-before options. Git will mark signatures as valid if the signing key was
+valid at the time of the signature's creation. This allows users to change a
+signing key without invalidating all previously made signatures.
++
+Using a SSH CA key with the cert-authority option
+(see ssh-keygen(1) "CERTIFICATES") is also valid.
+
+gpg.ssh.revocationFile::
+	Either a SSH KRL or a list of revoked public keys (without the principal prefix).
+	See ssh-keygen(1) for details.
+	If a public key is found in this file then it will always be treated
+	as having trust level "never" and signatures will show as invalid.
+
+
+grep.lineNumber::
+	If set to true, enable `-n` option by default.
+
+grep.column::
+	If set to true, enable the `--column` option by default.
+
+grep.patternType::
+	Set the default matching behavior. Using a value of 'basic', 'extended',
+	'fixed', or 'perl' will enable the `--basic-regexp`, `--extended-regexp`,
+	`--fixed-strings`, or `--perl-regexp` option accordingly, while the
+	value 'default' will use the `grep.extendedRegexp` option to choose
+	between 'basic' and 'extended'.
+
+grep.extendedRegexp::
+	If set to true, enable `--extended-regexp` option by default. This
+	option is ignored when the `grep.patternType` option is set to a value
+	other than 'default'.
+
+grep.threads::
+	Number of grep worker threads to use. If unset (or set to 0), Git will
+	use as many threads as the number of logical cores available.
+
+grep.fullName::
+	If set to true, enable `--full-name` option by default.
+
+grep.fallbackToNoIndex::
+	If set to true, fall back to `git grep --no-index` if `git grep`
+	is executed outside of a git repository.  Defaults to false.
+
+
+gui.commitMsgWidth::
+	Defines how wide the commit message window is in the
+	linkgit:git-gui[1]. "75" is the default.
+
+gui.diffContext::
+	Specifies how many context lines should be used in calls to diff
+	made by the linkgit:git-gui[1]. The default is "5".
+
+gui.displayUntracked::
+	Determines if linkgit:git-gui[1] shows untracked files
+	in the file list. The default is "true".
+
+gui.encoding::
+	Specifies the default character encoding to use for displaying of
+	file contents in linkgit:git-gui[1] and linkgit:gitk[1].
+	It can be overridden by setting the 'encoding' attribute
+	for relevant files (see linkgit:gitattributes[5]).
+	If this option is not set, the tools default to the
+	locale encoding.
+
+gui.matchTrackingBranch::
+	Determines if new branches created with linkgit:git-gui[1] should
+	default to tracking remote branches with matching names or
+	not. Default: "false".
+
+gui.newBranchTemplate::
+	Is used as a suggested name when creating new branches using the
+	linkgit:git-gui[1].
+
+gui.pruneDuringFetch::
+	"true" if linkgit:git-gui[1] should prune remote-tracking branches when
+	performing a fetch. The default value is "false".
+
+gui.trustmtime::
+	Determines if linkgit:git-gui[1] should trust the file modification
+	timestamp or not. By default the timestamps are not trusted.
+
+gui.spellingDictionary::
+	Specifies the dictionary used for spell checking commit messages in
+	the linkgit:git-gui[1]. When set to "none" spell checking is turned
+	off.
+
+gui.fastCopyBlame::
+	If true, 'git gui blame' uses `-C` instead of `-C -C` for original
+	location detection. It makes blame significantly faster on huge
+	repositories at the expense of less thorough copy detection.
+
+gui.copyBlameThreshold::
+	Specifies the threshold to use in 'git gui blame' original location
+	detection, measured in alphanumeric characters. See the
+	linkgit:git-blame[1] manual for more information on copy detection.
+
+gui.blamehistoryctx::
+	Specifies the radius of history context in days to show in
+	linkgit:gitk[1] for the selected commit, when the `Show History
+	Context` menu item is invoked from 'git gui blame'. If this
+	variable is set to zero, the whole history is shown.
+
+
+guitool.<name>.cmd::
+	Specifies the shell command line to execute when the corresponding item
+	of the linkgit:git-gui[1] `Tools` menu is invoked. This option is
+	mandatory for every tool. The command is executed from the root of
+	the working directory, and in the environment it receives the name of
+	the tool as `GIT_GUITOOL`, the name of the currently selected file as
+	'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if
+	the head is detached, 'CUR_BRANCH' is empty).
+
+guitool.<name>.needsFile::
+	Run the tool only if a diff is selected in the GUI. It guarantees
+	that 'FILENAME' is not empty.
+
+guitool.<name>.noConsole::
+	Run the command silently, without creating a window to display its
+	output.
+
+guitool.<name>.noRescan::
+	Don't rescan the working directory for changes after the tool
+	finishes execution.
+
+guitool.<name>.confirm::
+	Show a confirmation dialog before actually running the tool.
+
+guitool.<name>.argPrompt::
+	Request a string argument from the user, and pass it to the tool
+	through the `ARGS` environment variable. Since requesting an
+	argument implies confirmation, the 'confirm' option has no effect
+	if this is enabled. If the option is set to 'true', 'yes', or '1',
+	the dialog uses a built-in generic prompt; otherwise the exact
+	value of the variable is used.
+
+guitool.<name>.revPrompt::
+	Request a single valid revision from the user, and set the
+	`REVISION` environment variable. In other aspects this option
+	is similar to 'argPrompt', and can be used together with it.
+
+guitool.<name>.revUnmerged::
+	Show only unmerged branches in the 'revPrompt' subdialog.
+	This is useful for tools similar to merge or rebase, but not
+	for things like checkout or reset.
+
+guitool.<name>.title::
+	Specifies the title to use for the prompt dialog. The default
+	is the tool name.
+
+guitool.<name>.prompt::
+	Specifies the general prompt string to display at the top of
+	the dialog, before subsections for 'argPrompt' and 'revPrompt'.
+	The default value includes the actual command.
+
+
+help.browser::
+	Specify the browser that will be used to display help in the
+	'web' format. See linkgit:git-help[1].
+
+help.format::
+	Override the default help format used by linkgit:git-help[1].
+	Values 'man', 'info', 'web' and 'html' are supported. 'man' is
+	the default. 'web' and 'html' are the same.
+
+help.autoCorrect::
+	If git detects typos and can identify exactly one valid command similar
+	to the error, git will try to suggest the correct command or even
+	run the suggestion automatically. Possible config values are:
+	 - 0 (default): show the suggested command.
+	 - positive number: run the suggested command after specified
+deciseconds (0.1 sec).
+	 - "immediate": run the suggested command immediately.
+	 - "prompt": show the suggestion and prompt for confirmation to run
+the command.
+	 - "never": don't run or show any suggested command.
+
+help.htmlPath::
+	Specify the path where the HTML documentation resides. File system paths
+	and URLs are supported. HTML pages will be prefixed with this path when
+	help is displayed in the 'web' format. This defaults to the documentation
+	path of your Git installation.
+
+
+http.proxy::
+	Override the HTTP proxy, normally configured using the 'http_proxy',
+	'https_proxy', and 'all_proxy' environment variables (see `curl(1)`). In
+	addition to the syntax understood by curl, it is possible to specify a
+	proxy string with a user name but no password, in which case git will
+	attempt to acquire one in the same way it does for other credentials. See
+	linkgit:gitcredentials[7] for more information. The syntax thus is
+	'[protocol://][user[:password]@]proxyhost[:port]'. This can be overridden
+	on a per-remote basis; see remote.<name>.proxy
++
+Any proxy, however configured, must be completely transparent and must not
+modify, transform, or buffer the request or response in any way.  Proxies which
+are not completely transparent are known to cause various forms of breakage
+with Git.
+
+http.proxyAuthMethod::
+	Set the method with which to authenticate against the HTTP proxy. This
+	only takes effect if the configured proxy string contains a user name part
+	(i.e. is of the form 'user@host' or 'user@host:port'). This can be
+	overridden on a per-remote basis; see `remote.<name>.proxyAuthMethod`.
+	Both can be overridden by the `GIT_HTTP_PROXY_AUTHMETHOD` environment
+	variable.  Possible values are:
++
+--
+* `anyauth` - Automatically pick a suitable authentication method. It is
+  assumed that the proxy answers an unauthenticated request with a 407
+  status code and one or more Proxy-authenticate headers with supported
+  authentication methods. This is the default.
+* `basic` - HTTP Basic authentication
+* `digest` - HTTP Digest authentication; this prevents the password from being
+  transmitted to the proxy in clear text
+* `negotiate` - GSS-Negotiate authentication (compare the --negotiate option
+  of `curl(1)`)
+* `ntlm` - NTLM authentication (compare the --ntlm option of `curl(1)`)
+--
+
+http.proxySSLCert::
+	The pathname of a file that stores a client certificate to use to authenticate
+	with an HTTPS proxy. Can be overridden by the `GIT_PROXY_SSL_CERT` environment
+	variable.
+
+http.proxySSLKey::
+	The pathname of a file that stores a private key to use to authenticate with
+	an HTTPS proxy. Can be overridden by the `GIT_PROXY_SSL_KEY` environment
+	variable.
+
+http.proxySSLCertPasswordProtected::
+	Enable Git's password prompt for the proxy SSL certificate.  Otherwise OpenSSL
+	will prompt the user, possibly many times, if the certificate or private key
+	is encrypted. Can be overridden by the `GIT_PROXY_SSL_CERT_PASSWORD_PROTECTED`
+	environment variable.
+
+http.proxySSLCAInfo::
+	Pathname to the file containing the certificate bundle that should be used to
+	verify the proxy with when using an HTTPS proxy. Can be overridden by the
+	`GIT_PROXY_SSL_CAINFO` environment variable.
+
+http.emptyAuth::
+	Attempt authentication without seeking a username or password.  This
+	can be used to attempt GSS-Negotiate authentication without specifying
+	a username in the URL, as libcurl normally requires a username for
+	authentication.
+
+http.proactiveAuth::
+	Attempt authentication without first making an unauthenticated attempt and
+	receiving a 401 response. This can be used to ensure that all requests are
+	authenticated. If `http.emptyAuth` is set to true, this value has no effect.
++
+If the credential helper used specifies an authentication scheme (i.e., via the
+`authtype` field), that value will be used; if a username and password is
+provided without a scheme, then Basic authentication is used.  The value of the
+option determines the scheme requested from the helper. Possible values are:
++
+--
+* `basic` - Request Basic authentication from the helper.
+* `auto` - Allow the helper to pick an appropriate scheme.
+* `none` - Disable proactive authentication.
+--
++
+Note that TLS should always be used with this configuration, since otherwise it
+is easy to accidentally expose plaintext credentials if Basic authentication
+is selected.
+
+http.delegation::
+	Control GSSAPI credential delegation. The delegation is disabled
+	by default in libcurl since version 7.21.7. Set parameter to tell
+	the server what it is allowed to delegate when it comes to user
+	credentials. Used with GSS/kerberos. Possible values are:
++
+--
+* `none` - Don't allow any delegation.
+* `policy` - Delegates if and only if the OK-AS-DELEGATE flag is set in the
+  Kerberos service ticket, which is a matter of realm policy.
+* `always` - Unconditionally allow the server to delegate.
+--
+
+
+http.extraHeader::
+	Pass an additional HTTP header when communicating with a server.  If
+	more than one such entry exists, all of them are added as extra
+	headers.  To allow overriding the settings inherited from the system
+	config, an empty value will reset the extra headers to the empty list.
+
+http.cookieFile::
+	The pathname of a file containing previously stored cookie lines,
+	which should be used
+	in the Git http session, if they match the server. The file format
+	of the file to read cookies from should be plain HTTP headers or
+	the Netscape/Mozilla cookie file format (see `curl(1)`).
+	Set it to an empty string, to accept only new cookies from
+	the server and send them back in successive requests within same
+	connection.
+	NOTE that the file specified with http.cookieFile is used only as
+	input unless http.saveCookies is set.
+
+http.saveCookies::
+	If set, store cookies received during requests to the file specified by
+	http.cookieFile. Has no effect if http.cookieFile is unset, or set to
+	an empty string.
+
+http.version::
+	Use the specified HTTP protocol version when communicating with a server.
+	If you want to force the default. The available and default version depend
+	on libcurl. Currently the possible values of
+	this option are:
+
+	- HTTP/2
+	- HTTP/1.1
+
+http.curloptResolve::
+	Hostname resolution information that will be used first by
+	libcurl when sending HTTP requests.  This information should
+	be in one of the following formats:
+
+	- [+]HOST:PORT:ADDRESS[,ADDRESS]
+	- -HOST:PORT
+
++
+The first format redirects all requests to the given `HOST:PORT`
+to the provided `ADDRESS`(s). The second format clears all
+previous config values for that `HOST:PORT` combination.  To
+allow easy overriding of all the settings inherited from the
+system config, an empty value will reset all resolution
+information to the empty list.
+
+http.sslVersion::
+	The SSL version to use when negotiating an SSL connection, if you
+	want to force the default.  The available and default version
+	depend on whether libcurl was built against NSS or OpenSSL and the
+	particular configuration of the crypto library in use. Internally
+	this sets the 'CURLOPT_SSL_VERSION' option; see the libcurl
+	documentation for more details on the format of this option and
+	for the ssl version supported. Currently the possible values of
+	this option are:
+
+	- sslv2
+	- sslv3
+	- tlsv1
+	- tlsv1.0
+	- tlsv1.1
+	- tlsv1.2
+	- tlsv1.3
+
++
+Can be overridden by the `GIT_SSL_VERSION` environment variable.
+To force git to use libcurl's default ssl version and ignore any
+explicit http.sslversion option, set `GIT_SSL_VERSION` to the
+empty string.
+
+http.sslCipherList::
+  A list of SSL ciphers to use when negotiating an SSL connection.
+  The available ciphers depend on whether libcurl was built against
+  NSS or OpenSSL and the particular configuration of the crypto
+  library in use.  Internally this sets the 'CURLOPT_SSL_CIPHER_LIST'
+  option; see the libcurl documentation for more details on the format
+  of this list.
++
+Can be overridden by the `GIT_SSL_CIPHER_LIST` environment variable.
+To force git to use libcurl's default cipher list and ignore any
+explicit http.sslCipherList option, set `GIT_SSL_CIPHER_LIST` to the
+empty string.
+
+http.sslVerify::
+	Whether to verify the SSL certificate when fetching or pushing
+	over HTTPS. Defaults to true. Can be overridden by the
+	`GIT_SSL_NO_VERIFY` environment variable.
+
+http.sslCert::
+	File containing the SSL certificate when fetching or pushing
+	over HTTPS. Can be overridden by the `GIT_SSL_CERT` environment
+	variable.
+
+http.sslKey::
+	File containing the SSL private key when fetching or pushing
+	over HTTPS. Can be overridden by the `GIT_SSL_KEY` environment
+	variable.
+
+http.sslCertPasswordProtected::
+	Enable Git's password prompt for the SSL certificate.  Otherwise
+	OpenSSL will prompt the user, possibly many times, if the
+	certificate or private key is encrypted.  Can be overridden by the
+	`GIT_SSL_CERT_PASSWORD_PROTECTED` environment variable.
+
+http.sslCAInfo::
+	File containing the certificates to verify the peer with when
+	fetching or pushing over HTTPS. Can be overridden by the
+	`GIT_SSL_CAINFO` environment variable.
+
+http.sslCAPath::
+	Path containing files with the CA certificates to verify the peer
+	with when fetching or pushing over HTTPS. Can be overridden
+	by the `GIT_SSL_CAPATH` environment variable.
+
+http.sslBackend::
+	Name of the SSL backend to use (e.g. "openssl" or "schannel").
+	This option is ignored if cURL lacks support for choosing the SSL
+	backend at runtime.
+
+http.schannelCheckRevoke::
+	Used to enforce or disable certificate revocation checks in cURL
+	when http.sslBackend is set to "schannel". Defaults to `true` if
+	unset. Only necessary to disable this if Git consistently errors
+	and the message is about checking the revocation status of a
+	certificate. This option is ignored if cURL lacks support for
+	setting the relevant SSL option at runtime.
+
+http.schannelUseSSLCAInfo::
+	As of cURL v7.60.0, the Secure Channel backend can use the
+	certificate bundle provided via `http.sslCAInfo`, but that would
+	override the Windows Certificate Store. Since this is not desirable
+	by default, Git will tell cURL not to use that bundle by default
+	when the `schannel` backend was configured via `http.sslBackend`,
+	unless `http.schannelUseSSLCAInfo` overrides this behavior.
+
+http.pinnedPubkey::
+	Public key of the https service. It may either be the filename of
+	a PEM or DER encoded public key file or a string starting with
+	'sha256//' followed by the base64 encoded sha256 hash of the
+	public key. See also libcurl 'CURLOPT_PINNEDPUBLICKEY'. git will
+	exit with an error if this option is set but not supported by
+	cURL.
+
+http.sslTry::
+	Attempt to use AUTH SSL/TLS and encrypted data transfers
+	when connecting via regular FTP protocol. This might be needed
+	if the FTP server requires it for security reasons or you wish
+	to connect securely whenever remote FTP server supports it.
+	Default is false since it might trigger certificate verification
+	errors on misconfigured servers.
+
+http.maxRequests::
+	How many HTTP requests to launch in parallel. Can be overridden
+	by the `GIT_HTTP_MAX_REQUESTS` environment variable. Default is 5.
+
+http.minSessions::
+	The number of curl sessions (counted across slots) to be kept across
+	requests. They will not be ended with curl_easy_cleanup() until
+	http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
+	value will be capped at 1. Defaults to 1.
+
+http.postBuffer::
+	Maximum size in bytes of the buffer used by smart HTTP
+	transports when POSTing data to the remote system.
+	For requests larger than this buffer size, HTTP/1.1 and
+	Transfer-Encoding: chunked is used to avoid creating a
+	massive pack file locally.  Default is 1 MiB, which is
+	sufficient for most requests.
++
+Note that raising this limit is only effective for disabling chunked
+transfer encoding and therefore should be used only where the remote
+server or a proxy only supports HTTP/1.0 or is noncompliant with the
+HTTP standard.  Raising this is not, in general, an effective solution
+for most push problems, but can increase memory consumption
+significantly since the entire buffer is allocated even for small
+pushes.
+
+http.lowSpeedLimit, http.lowSpeedTime::
+	If the HTTP transfer speed, in bytes per second, is less than
+	'http.lowSpeedLimit' for longer than 'http.lowSpeedTime' seconds,
+	the transfer is aborted.
+	Can be overridden by the `GIT_HTTP_LOW_SPEED_LIMIT` and
+	`GIT_HTTP_LOW_SPEED_TIME` environment variables.
+
+http.noEPSV::
+	A boolean which disables using of EPSV ftp command by curl.
+	This can be helpful with some "poor" ftp servers which don't
+	support EPSV mode. Can be overridden by the `GIT_CURL_FTP_NO_EPSV`
+	environment variable. Default is false (curl will use EPSV).
+
+http.userAgent::
+	The HTTP USER_AGENT string presented to an HTTP server.  The default
+	value represents the version of the Git client such as git/1.7.1.
+	This option allows you to override this value to a more common value
+	such as Mozilla/4.0.  This may be necessary, for instance, if
+	connecting through a firewall that restricts HTTP connections to a set
+	of common USER_AGENT strings (but not including those like git/1.7.1).
+	Can be overridden by the `GIT_HTTP_USER_AGENT` environment variable.
+
+http.followRedirects::
+	Whether git should follow HTTP redirects. If set to `true`, git
+	will transparently follow any redirect issued by a server it
+	encounters. If set to `false`, git will treat all redirects as
+	errors. If set to `initial`, git will follow redirects only for
+	the initial request to a remote, but not for subsequent
+	follow-up HTTP requests. Since git uses the redirected URL as
+	the base for the follow-up requests, this is generally
+	sufficient. The default is `initial`.
+
+http.<url>.*::
+	Any of the http.* options above can be applied selectively to some URLs.
+	For a config key to match a URL, each element of the config key is
+	compared to that of the URL, in the following order:
++
+--
+. Scheme (e.g., `https` in `https://example.com/`). This field
+  must match exactly between the config key and the URL.
+
+. Host/domain name (e.g., `example.com` in `https://example.com/`).
+  This field must match between the config key and the URL. It is
+  possible to specify a `*` as part of the host name to match all subdomains
+  at this level. `https://*.example.com/` for example would match
+  `https://foo.example.com/`, but not `https://foo.bar.example.com/`.
+
+. Port number (e.g., `8080` in `http://example.com:8080/`).
+  This field must match exactly between the config key and the URL.
+  Omitted port numbers are automatically converted to the correct
+  default for the scheme before matching.
+
+. Path (e.g., `repo.git` in `https://example.com/repo.git`). The
+  path field of the config key must match the path field of the URL
+  either exactly or as a prefix of slash-delimited path elements.  This means
+  a config key with path `foo/` matches URL path `foo/bar`.  A prefix can only
+  match on a slash (`/`) boundary.  Longer matches take precedence (so a config
+  key with path `foo/bar` is a better match to URL path `foo/bar` than a config
+  key with just path `foo/`).
+
+. User name (e.g., `user` in `https://user@example.com/repo.git`). If
+  the config key has a user name it must match the user name in the
+  URL exactly. If the config key does not have a user name, that
+  config key will match a URL with any user name (including none),
+  but at a lower precedence than a config key with a user name.
+--
++
+The list above is ordered by decreasing precedence; a URL that matches
+a config key's path is preferred to one that matches its user name. For example,
+if the URL is `https://user@example.com/foo/bar` a config key match of
+`https://example.com/foo` will be preferred over a config key match of
+`https://user@example.com`.
++
+All URLs are normalized before attempting any matching (the password part,
+if embedded in the URL, is always ignored for matching purposes) so that
+equivalent URLs that are simply spelled differently will match properly.
+Environment variable settings always override any matches.  The URLs that are
+matched against are those given directly to Git commands.  This means any URLs
+visited as a result of a redirection do not participate in matching.
+
+
+i18n.commitEncoding::
+	Character encoding the commit messages are stored in; Git itself
+	does not care per se, but this information is necessary e.g. when
+	importing commits from emails or in the gitk graphical history
+	browser (and possibly in other places in the future or in other
+	porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.
+
+i18n.logOutputEncoding::
+	Character encoding the commit messages are converted to when
+	running 'git log' and friends.
+
+
+imap.folder::
+	The folder to drop the mails into, which is typically the Drafts
+	folder. For example: "INBOX.Drafts", "INBOX/Drafts" or
+	"[Gmail]/Drafts". Required.
+
+imap.tunnel::
+	Command used to set up a tunnel to the IMAP server through which
+	commands will be piped instead of using a direct network connection
+	to the server. Required when imap.host is not set.
+
+imap.host::
+	A URL identifying the server. Use an `imap://` prefix for non-secure
+	connections and an `imaps://` prefix for secure connections.
+	Ignored when imap.tunnel is set, but required otherwise.
+
+imap.user::
+	The username to use when logging in to the server.
+
+imap.pass::
+	The password to use when logging in to the server.
+
+imap.port::
+	An integer port number to connect to on the server.
+	Defaults to 143 for imap:// hosts and 993 for imaps:// hosts.
+	Ignored when imap.tunnel is set.
+
+imap.sslverify::
+	A boolean to enable/disable verification of the server certificate
+	used by the SSL/TLS connection. Default is `true`. Ignored when
+	imap.tunnel is set.
+
+imap.preformattedHTML::
+	A boolean to enable/disable the use of html encoding when sending
+	a patch.  An html encoded patch will be bracketed with <pre>
+	and have a content type of text/html.  Ironically, enabling this
+	option causes Thunderbird to send the patch as a plain/text,
+	format=fixed email.  Default is `false`.
+
+imap.authMethod::
+	Specify the authentication method for authenticating with the IMAP server.
+	If Git was built with the NO_CURL option, or if your curl version is older
+	than 7.34.0, or if you're running git-imap-send with the `--no-curl`
+	option, the only supported method is 'CRAM-MD5'. If this is not set
+	then 'git imap-send' uses the basic IMAP plaintext LOGIN command.
+
+
+include.path::
+includeIf.<condition>.path::
+	Special variables to include other configuration files. See
+	the "CONFIGURATION FILE" section in the main
+	linkgit:git-config[1] documentation,
+	specifically the "Includes" and "Conditional Includes" subsections.
+
+
+index.recordEndOfIndexEntries::
+	Specifies whether the index file should include an "End Of Index
+	Entry" section. This reduces index load time on multiprocessor
+	machines but produces a message "ignoring EOIE extension" when
+	reading the index using Git versions before 2.20. Defaults to
+	'true' if index.threads has been explicitly enabled, 'false'
+	otherwise.
+
+index.recordOffsetTable::
+	Specifies whether the index file should include an "Index Entry
+	Offset Table" section. This reduces index load time on
+	multiprocessor machines but produces a message "ignoring IEOT
+	extension" when reading the index using Git versions before 2.20.
+	Defaults to 'true' if index.threads has been explicitly enabled,
+	'false' otherwise.
+
+index.sparse::
+	When enabled, write the index using sparse-directory entries. This
+	has no effect unless `core.sparseCheckout` and
+	`core.sparseCheckoutCone` are both enabled. Defaults to 'false'.
+
+index.threads::
+	Specifies the number of threads to spawn when loading the index.
+	This is meant to reduce index load time on multiprocessor machines.
+	Specifying 0 or 'true' will cause Git to auto-detect the number of
+	CPUs and set the number of threads accordingly. Specifying 1 or
+	'false' will disable multithreading. Defaults to 'true'.
+
+index.version::
+	Specify the version with which new index files should be
+	initialized.  This does not affect existing repositories.
+	If `feature.manyFiles` is enabled, then the default is 4.
+
+index.skipHash::
+	When enabled, do not compute the trailing hash for the index file.
+	This accelerates Git commands that manipulate the index, such as
+	`git add`, `git commit`, or `git status`. Instead of storing the
+	checksum, write a trailing set of bytes with value zero, indicating
+	that the computation was skipped.
++
+If you enable `index.skipHash`, then Git clients older than 2.13.0 will
+refuse to parse the index and Git clients older than 2.40.0 will report an
+error during `git fsck`.
+
+
+:see-git-init:
+ifndef::git-init[]
+:see-git-init: (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)
+endif::[]
+
+`init.templateDir`::
+	Specify the directory from which templates will be copied. {see-git-init}
+`init.defaultBranch`::
+	Allows overriding the default branch name e.g. when initializing
+	a new repository.
+
+
+instaweb.browser::
+	Specify the program that will be used to browse your working
+	repository in gitweb. See linkgit:git-instaweb[1].
+
+instaweb.httpd::
+	The HTTP daemon command-line to start gitweb on your working
+	repository. See linkgit:git-instaweb[1].
+
+instaweb.local::
+	If true the web server started by linkgit:git-instaweb[1] will
+	be bound to the local IP (127.0.0.1).
+
+instaweb.modulePath::
+	The default module path for linkgit:git-instaweb[1] to use
+	instead of /usr/lib/apache2/modules.  Only used if httpd
+	is Apache.
+
+instaweb.port::
+	The port number to bind the gitweb httpd to. See
+	linkgit:git-instaweb[1].
+
+
+interactive.singleKey::
+	When set to true, allow the user to provide one-letter input
+	with a single key (i.e., without hitting the Enter key) in
+	interactive commands.  This is currently used by the `--patch`
+	mode of linkgit:git-add[1], linkgit:git-checkout[1],
+	linkgit:git-restore[1], linkgit:git-commit[1],
+	linkgit:git-reset[1], and linkgit:git-stash[1].
+
+interactive.diffFilter::
+	When an interactive command (such as `git add --patch`) shows
+	a colorized diff, git will pipe the diff through the shell
+	command defined by this configuration variable. The command may
+	mark up the diff further for human consumption, provided that it
+	retains a one-to-one correspondence with the lines in the
+	original diff. Defaults to disabled (no filtering).
+
+
+log.abbrevCommit::
+	If true, makes linkgit:git-log[1], linkgit:git-show[1], and
+	linkgit:git-whatchanged[1] assume `--abbrev-commit`. You may
+	override this option with `--no-abbrev-commit`.
+
+log.date::
+	Set the default date-time mode for the 'log' command.
+	Setting a value for log.date is similar to using 'git log''s
+	`--date` option.  See linkgit:git-log[1] for details.
++
+If the format is set to "auto:foo" and the pager is in use, format
+"foo" will be used for the date format. Otherwise, "default" will
+be used.
+
+log.decorate::
+	Print out the ref names of any commits that are shown by the log
+	command. If 'short' is specified, the ref name prefixes 'refs/heads/',
+	'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is
+	specified, the full ref name (including prefix) will be printed.
+	If 'auto' is specified, then if the output is going to a terminal,
+	the ref names are shown as if 'short' were given, otherwise no ref
+	names are shown. This is the same as the `--decorate` option
+	of the `git log`.
+
+log.initialDecorationSet::
+	By default, `git log` only shows decorations for certain known ref
+	namespaces. If 'all' is specified, then show all refs as
+	decorations.
+
+log.excludeDecoration::
+	Exclude the specified patterns from the log decorations. This is
+	similar to the `--decorate-refs-exclude` command-line option, but
+	the config option can be overridden by the `--decorate-refs`
+	option.
+
+log.diffMerges::
+	Set diff format to be used when `--diff-merges=on` is
+	specified, see `--diff-merges` in linkgit:git-log[1] for
+	details. Defaults to `separate`.
+
+log.follow::
+	If `true`, `git log` will act as if the `--follow` option was used when
+	a single <path> is given.  This has the same limitations as `--follow`,
+	i.e. it cannot be used to follow multiple files and does not work well
+	on non-linear history.
+
+log.graphColors::
+	A list of colors, separated by commas, that can be used to draw
+	history lines in `git log --graph`.
+
+log.showRoot::
+	If true, the initial commit will be shown as a big creation event.
+	This is equivalent to a diff against an empty tree.
+	Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which
+	normally hide the root commit will now show it. True by default.
+
+log.showSignature::
+	If true, makes linkgit:git-log[1], linkgit:git-show[1], and
+	linkgit:git-whatchanged[1] assume `--show-signature`.
+
+log.mailmap::
+	If true, makes linkgit:git-log[1], linkgit:git-show[1], and
+	linkgit:git-whatchanged[1] assume `--use-mailmap`, otherwise
+	assume `--no-use-mailmap`. True by default.
+
+
+lsrefs.unborn::
+	May be "advertise" (the default), "allow", or "ignore". If "advertise",
+	the server will respond to the client sending "unborn" (as described in
+	linkgit:gitprotocol-v2[5]) and will advertise support for this feature during the
+	protocol v2 capability advertisement. "allow" is the same as
+	"advertise" except that the server will not advertise support for this
+	feature; this is useful for load-balanced servers that cannot be
+	updated atomically (for example), since the administrator could
+	configure "allow", then after a delay, configure "advertise".
+
+
+mailinfo.scissors::
+	If true, makes linkgit:git-mailinfo[1] (and therefore
+	linkgit:git-am[1]) act by default as if the --scissors option
+	was provided on the command-line. When active, this feature
+	removes everything from the message body before a scissors
+	line (i.e. consisting mainly of ">8", "8<" and "-").
+
+
+mailmap.file::
+	The location of an augmenting mailmap file. The default
+	mailmap, located in the root of the repository, is loaded
+	first, then the mailmap file pointed to by this variable.
+	The location of the mailmap file may be in a repository
+	subdirectory, or somewhere outside of the repository itself.
+	See linkgit:git-shortlog[1] and linkgit:git-blame[1].
+
+mailmap.blob::
+	Like `mailmap.file`, but consider the value as a reference to a
+	blob in the repository. If both `mailmap.file` and
+	`mailmap.blob` are given, both are parsed, with entries from
+	`mailmap.file` taking precedence. In a bare repository, this
+	defaults to `HEAD:.mailmap`. In a non-bare repository, it
+	defaults to empty.
+
+
+maintenance.auto::
+	This boolean config option controls whether some commands run
+	`git maintenance run --auto` after doing their normal work. Defaults
+	to true.
+
+maintenance.strategy::
+	This string config option provides a way to specify one of a few
+	recommended schedules for background maintenance. This only affects
+	which tasks are run during `git maintenance run --schedule=X`
+	commands, provided no `--task=<task>` arguments are provided.
+	Further, if a `maintenance.<task>.schedule` config value is set,
+	then that value is used instead of the one provided by
+	`maintenance.strategy`. The possible strategy strings are:
++
+* `none`: This default setting implies no tasks are run at any schedule.
+* `incremental`: This setting optimizes for performing small maintenance
+  activities that do not delete any data. This does not schedule the `gc`
+  task, but runs the `prefetch` and `commit-graph` tasks hourly, the
+  `loose-objects` and `incremental-repack` tasks daily, and the `pack-refs`
+  task weekly.
+
+maintenance.<task>.enabled::
+	This boolean config option controls whether the maintenance task
+	with name `<task>` is run when no `--task` option is specified to
+	`git maintenance run`. These config values are ignored if a
+	`--task` option exists. By default, only `maintenance.gc.enabled`
+	is true.
+
+maintenance.<task>.schedule::
+	This config option controls whether or not the given `<task>` runs
+	during a `git maintenance run --schedule=<frequency>` command. The
+	value must be one of "hourly", "daily", or "weekly".
+
+maintenance.commit-graph.auto::
+	This integer config option controls how often the `commit-graph` task
+	should be run as part of `git maintenance run --auto`. If zero, then
+	the `commit-graph` task will not run with the `--auto` option. A
+	negative value will force the task to run every time. Otherwise, a
+	positive value implies the command should run when the number of
+	reachable commits that are not in the commit-graph file is at least
+	the value of `maintenance.commit-graph.auto`. The default value is
+	100.
+
+maintenance.loose-objects.auto::
+	This integer config option controls how often the `loose-objects` task
+	should be run as part of `git maintenance run --auto`. If zero, then
+	the `loose-objects` task will not run with the `--auto` option. A
+	negative value will force the task to run every time. Otherwise, a
+	positive value implies the command should run when the number of
+	loose objects is at least the value of `maintenance.loose-objects.auto`.
+	The default value is 100.
+
+maintenance.incremental-repack.auto::
+	This integer config option controls how often the `incremental-repack`
+	task should be run as part of `git maintenance run --auto`. If zero,
+	then the `incremental-repack` task will not run with the `--auto`
+	option. A negative value will force the task to run every time.
+	Otherwise, a positive value implies the command should run when the
+	number of pack-files not in the multi-pack-index is at least the value
+	of `maintenance.incremental-repack.auto`. The default value is 10.
+
+
+man.viewer::
+	Specify the programs that may be used to display help in the
+	'man' format. See linkgit:git-help[1].
+
+man.<tool>.cmd::
+	Specify the command to invoke the specified man viewer. The
+	specified command is evaluated in shell with the man page
+	passed as an argument. (See linkgit:git-help[1].)
+
+man.<tool>.path::
+	Override the path for the given tool that may be used to
+	display help in the 'man' format. See linkgit:git-help[1].
+
+
+merge.conflictStyle::
+	Specify the style in which conflicted hunks are written out to
+	working tree files upon merge.  The default is "merge", which
+	shows a `<<<<<<<` conflict marker, changes made by one side,
+	a `=======` marker, changes made by the other side, and then
+	a `>>>>>>>` marker.  An alternate style, "diff3", adds a `|||||||`
+	marker and the original text before the `=======` marker.  The
+	"merge" style tends to produce smaller conflict regions than diff3,
+	both because of the exclusion of the original text, and because
+	when a subset of lines match on the two sides, they are just pulled
+	out of the conflict region.  Another alternate style, "zdiff3", is
+	similar to diff3 but removes matching lines on the two sides from
+	the conflict region when those matching lines appear near either
+	the beginning or end of a conflict region.
+
+merge.defaultToUpstream::
+	If merge is called without any commit argument, merge the upstream
+	branches configured for the current branch by using their last
+	observed values stored in their remote-tracking branches.
+	The values of the `branch.<current branch>.merge` that name the
+	branches at the remote named by `branch.<current branch>.remote`
+	are consulted, and then they are mapped via `remote.<remote>.fetch`
+	to their corresponding remote-tracking branches, and the tips of
+	these tracking branches are merged. Defaults to true.
+
+merge.ff::
+	By default, Git does not create an extra merge commit when merging
+	a commit that is a descendant of the current commit. Instead, the
+	tip of the current branch is fast-forwarded. When set to `false`,
+	this variable tells Git to create an extra merge commit in such
+	a case (equivalent to giving the `--no-ff` option from the command
+	line). When set to `only`, only such fast-forward merges are
+	allowed (equivalent to giving the `--ff-only` option from the
+	command line).
+
+merge.verifySignatures::
+	If true, this is equivalent to the --verify-signatures command
+	line option. See linkgit:git-merge[1] for details.
+
+merge.branchdesc::
+	In addition to branch names, populate the log message with
+	the branch description text associated with them.  Defaults
+	to false.
+
+merge.log::
+	In addition to branch names, populate the log message with at
+	most the specified number of one-line descriptions from the
+	actual commits that are being merged.  Defaults to false, and
+	true is a synonym for 20.
+
+merge.suppressDest::
+	By adding a glob that matches the names of integration
+	branches to this multi-valued configuration variable, the
+	default merge message computed for merges into these
+	integration branches will omit "into <branch name>" from
+	its title.
++
+An element with an empty value can be used to clear the list
+of globs accumulated from previous configuration entries.
+When there is no `merge.suppressDest` variable defined, the
+default value of `master` is used for backward compatibility.
+
+
+merge.renameLimit::
+	The number of files to consider in the exhaustive portion of
+	rename detection during a merge.  If not specified, defaults
+	to the value of diff.renameLimit.  If neither
+	merge.renameLimit nor diff.renameLimit are specified,
+	currently defaults to 7000.  This setting has no effect if
+	rename detection is turned off.
+
+merge.renames::
+	Whether Git detects renames.  If set to "false", rename detection
+	is disabled. If set to "true", basic rename detection is enabled.
+	Defaults to the value of diff.renames.
+
+merge.directoryRenames::
+	Whether Git detects directory renames, affecting what happens at
+	merge time to new files added to a directory on one side of
+	history when that directory was renamed on the other side of
+	history.  If merge.directoryRenames is set to "false", directory
+	rename detection is disabled, meaning that such new files will be
+	left behind in the old directory.  If set to "true", directory
+	rename detection is enabled, meaning that such new files will be
+	moved into the new directory.  If set to "conflict", a conflict
+	will be reported for such paths.  If merge.renames is false,
+	merge.directoryRenames is ignored and treated as false.  Defaults
+	to "conflict".
+
+merge.renormalize::
+	Tell Git that canonical representation of files in the
+	repository has changed over time (e.g. earlier commits record
+	text files with CRLF line endings, but recent ones use LF line
+	endings).  In such a repository, Git can convert the data
+	recorded in commits to a canonical form before performing a
+	merge to reduce unnecessary conflicts.  For more information,
+	see section "Merging branches with differing checkin/checkout
+	attributes" in linkgit:gitattributes[5].
+
+merge.stat::
+	Whether to print the diffstat between ORIG_HEAD and the merge result
+	at the end of the merge.  True by default.
+
+merge.autoStash::
+	When set to true, automatically create a temporary stash entry
+	before the operation begins, and apply it after the operation
+	ends.  This means that you can run merge on a dirty worktree.
+	However, use with care: the final stash application after a
+	successful merge might result in non-trivial conflicts.
+	This option can be overridden by the `--no-autostash` and
+	`--autostash` options of linkgit:git-merge[1].
+	Defaults to false.
+
+merge.tool::
+	Controls which merge tool is used by linkgit:git-mergetool[1].
+	The list below shows the valid built-in values.
+	Any other value is treated as a custom merge tool and requires
+	that a corresponding mergetool.<tool>.cmd variable is defined.
+
+merge.guitool::
+	Controls which merge tool is used by linkgit:git-mergetool[1] when the
+	-g/--gui flag is specified. The list below shows the valid built-in values.
+	Any other value is treated as a custom merge tool and requires that a
+	corresponding mergetool.<guitool>.cmd variable is defined.
+
+ * araxis
+ * bc
+ * codecompare
+ * deltawalker
+ * diffmerge
+ * diffuse
+ * ecmerge
+ * emerge
+ * examdiff
+ * guiffy
+ * gvimdiff
+ * kdiff3
+ * meld
+ * nvimdiff
+ * opendiff
+ * p4merge
+ * smerge
+ * tkdiff
+ * tortoisemerge
+ * vimdiff
+ * winmerge
+ * xxdiff
+
+
+merge.verbosity::
+	Controls the amount of output shown by the recursive merge
+	strategy.  Level 0 outputs nothing except a final error
+	message if conflicts were detected. Level 1 outputs only
+	conflicts, 2 outputs conflicts and file changes.  Level 5 and
+	above outputs debugging information.  The default is level 2.
+	Can be overridden by the `GIT_MERGE_VERBOSITY` environment variable.
+
+merge.<driver>.name::
+	Defines a human-readable name for a custom low-level
+	merge driver.  See linkgit:gitattributes[5] for details.
+
+merge.<driver>.driver::
+	Defines the command that implements a custom low-level
+	merge driver.  See linkgit:gitattributes[5] for details.
+
+merge.<driver>.recursive::
+	Names a low-level merge driver to be used when
+	performing an internal merge between common ancestors.
+	See linkgit:gitattributes[5] for details.
+
+
+mergetool.<tool>.path::
+	Override the path for the given tool.  This is useful in case
+	your tool is not in the PATH.
+
+mergetool.<tool>.cmd::
+	Specify the command to invoke the specified merge tool.  The
+	specified command is evaluated in shell with the following
+	variables available: 'BASE' is the name of a temporary file
+	containing the common base of the files to be merged, if available;
+	'LOCAL' is the name of a temporary file containing the contents of
+	the file on the current branch; 'REMOTE' is the name of a temporary
+	file containing the contents of the file from the branch being
+	merged; 'MERGED' contains the name of the file to which the merge
+	tool should write the results of a successful merge.
+
+mergetool.<tool>.hideResolved::
+	Allows the user to override the global `mergetool.hideResolved` value
+	for a specific tool. See `mergetool.hideResolved` for the full
+	description.
+
+mergetool.<tool>.trustExitCode::
+	For a custom merge command, specify whether the exit code of
+	the merge command can be used to determine whether the merge was
+	successful.  If this is not set to true then the merge target file
+	timestamp is checked, and the merge is assumed to have been successful
+	if the file has been updated; otherwise, the user is prompted to
+	indicate the success of the merge.
+
+mergetool.meld.hasOutput::
+	Older versions of `meld` do not support the `--output` option.
+	Git will attempt to detect whether `meld` supports `--output`
+	by inspecting the output of `meld --help`.  Configuring
+	`mergetool.meld.hasOutput` will make Git skip these checks and
+	use the configured value instead.  Setting `mergetool.meld.hasOutput`
+	to `true` tells Git to unconditionally use the `--output` option,
+	and `false` avoids using `--output`.
+
+mergetool.meld.useAutoMerge::
+	When the `--auto-merge` is given, meld will merge all non-conflicting
+	parts automatically, highlight the conflicting parts, and wait for
+	user decision.  Setting `mergetool.meld.useAutoMerge` to `true` tells
+	Git to unconditionally use the `--auto-merge` option with `meld`.
+	Setting this value to `auto` makes git detect whether `--auto-merge`
+	is supported and will only use `--auto-merge` when available.  A
+	value of `false` avoids using `--auto-merge` altogether, and is the
+	default value.
+
+mergetool.<vimdiff variant>.layout::
+	Configure the split window layout for vimdiff's `<variant>`, which is any of `vimdiff`,
+	`nvimdiff`, `gvimdiff`.
+	Upon launching `git mergetool` with `--tool=<variant>` (or without `--tool`
+	if `merge.tool` is configured as `<variant>`), Git will consult
+	`mergetool.<variant>.layout` to determine the tool's layout. If the
+	variant-specific configuration is not available, `vimdiff`'s is used as
+	fallback.  If that too is not available, a default layout with 4 windows
+	will be used.  To configure the layout, see the `BACKEND SPECIFIC HINTS`
+ifdef::git-mergetool[]
+	section.
+endif::[]
+ifndef::git-mergetool[]
+	section in linkgit:git-mergetool[1].
+endif::[]
+
+mergetool.hideResolved::
+	During a merge, Git will automatically resolve as many conflicts as
+	possible and write the 'MERGED' file containing conflict markers around
+	any conflicts that it cannot resolve; 'LOCAL' and 'REMOTE' normally
+	represent the versions of the file from before Git's conflict
+	resolution. This flag causes 'LOCAL' and 'REMOTE' to be overwritten so
+	that only the unresolved conflicts are presented to the merge tool. Can
+	be configured per-tool via the `mergetool.<tool>.hideResolved`
+	configuration variable. Defaults to `false`.
+
+mergetool.keepBackup::
+	After performing a merge, the original file with conflict markers
+	can be saved as a file with a `.orig` extension.  If this variable
+	is set to `false` then this file is not preserved.  Defaults to
+	`true` (i.e. keep the backup files).
+
+mergetool.keepTemporaries::
+	When invoking a custom merge tool, Git uses a set of temporary
+	files to pass to the tool. If the tool returns an error and this
+	variable is set to `true`, then these temporary files will be
+	preserved; otherwise, they will be removed after the tool has
+	exited. Defaults to `false`.
+
+mergetool.writeToTemp::
+	Git writes temporary 'BASE', 'LOCAL', and 'REMOTE' versions of
+	conflicting files in the worktree by default.  Git will attempt
+	to use a temporary directory for these files when set `true`.
+	Defaults to `false`.
+
+mergetool.prompt::
+	Prompt before each invocation of the merge resolution program.
+
+mergetool.guiDefault::
+	Set `true` to use the `merge.guitool` by default (equivalent to
+	specifying the `--gui` argument), or `auto` to select `merge.guitool`
+	or `merge.tool` depending on the presence of a `DISPLAY` environment
+	variable value. The default is `false`, where the `--gui` argument
+	must be provided explicitly for the `merge.guitool` to be used.
+
+
+notes.mergeStrategy::
+	Which merge strategy to choose by default when resolving notes
+	conflicts.  Must be one of `manual`, `ours`, `theirs`, `union`, or
+	`cat_sort_uniq`.  Defaults to `manual`.  See the "NOTES MERGE STRATEGIES"
+	section of linkgit:git-notes[1] for more information on each strategy.
++
+This setting can be overridden by passing the `--strategy` option to
+linkgit:git-notes[1].
+
+notes.<name>.mergeStrategy::
+	Which merge strategy to choose when doing a notes merge into
+	refs/notes/<name>.  This overrides the more general
+	"notes.mergeStrategy".  See the "NOTES MERGE STRATEGIES" section in
+	linkgit:git-notes[1] for more information on the available strategies.
+
+notes.displayRef::
+	Which ref (or refs, if a glob or specified more than once), in
+	addition to the default set by `core.notesRef` or
+	`GIT_NOTES_REF`, to read notes from when showing commit
+	messages with the 'git log' family of commands.
++
+This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`
+environment variable, which must be a colon separated list of refs or
+globs.
++
+A warning will be issued for refs that do not exist,
+but a glob that does not match any refs is silently ignored.
++
+This setting can be disabled by the `--no-notes` option to the 'git
+log' family of commands, or by the `--notes=<ref>` option accepted by
+those commands.
++
+The effective value of "core.notesRef" (possibly overridden by
+GIT_NOTES_REF) is also implicitly added to the list of refs to be
+displayed.
+
+notes.rewrite.<command>::
+	When rewriting commits with <command> (currently `amend` or
+	`rebase`), if this variable is `false`, git will not copy
+	notes from the original to the rewritten commit.  Defaults to
+	`true`.  See also "`notes.rewriteRef`" below.
++
+This setting can be overridden with the `GIT_NOTES_REWRITE_REF`
+environment variable, which must be a colon separated list of refs or
+globs.
+
+notes.rewriteMode::
+	When copying notes during a rewrite (see the
+	"notes.rewrite.<command>" option), determines what to do if
+	the target commit already has a note.  Must be one of
+	`overwrite`, `concatenate`, `cat_sort_uniq`, or `ignore`.
+	Defaults to `concatenate`.
++
+This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`
+environment variable.
+
+notes.rewriteRef::
+	When copying notes during a rewrite, specifies the (fully
+	qualified) ref whose notes should be copied.  May be a glob,
+	in which case notes in all matching refs will be copied.  You
+	may also specify this configuration several times.
++
+Does not have a default value; you must configure this variable to
+enable note rewriting.  Set it to `refs/notes/commits` to enable
+rewriting for the default commit notes.
++
+Can be overridden with the `GIT_NOTES_REWRITE_REF` environment variable.
+See `notes.rewrite.<command>` above for a further description of its format.
+
+
+pack.window::
+	The size of the window used by linkgit:git-pack-objects[1] when no
+	window size is given on the command line. Defaults to 10.
+
+pack.depth::
+	The maximum delta depth used by linkgit:git-pack-objects[1] when no
+	maximum depth is given on the command line. Defaults to 50.
+	Maximum value is 4095.
+
+pack.windowMemory::
+	The maximum size of memory that is consumed by each thread
+	in linkgit:git-pack-objects[1] for pack window memory when
+	no limit is given on the command line.  The value can be
+	suffixed with "k", "m", or "g".  When left unconfigured (or
+	set explicitly to 0), there will be no limit.
+
+pack.compression::
+	An integer -1..9, indicating the compression level for objects
+	in a pack file. -1 is the zlib default. 0 means no
+	compression, and 1..9 are various speed/size tradeoffs, 9 being
+	slowest.  If not set,  defaults to core.compression.  If that is
+	not set,  defaults to -1, the zlib default, which is "a default
+	compromise between speed and compression (currently equivalent
+	to level 6)."
++
+Note that changing the compression level will not automatically recompress
+all existing objects. You can force recompression by passing the -F option
+to linkgit:git-repack[1].
+
+pack.allowPackReuse::
+	When true or "single", and when reachability bitmaps are
+	enabled, pack-objects will try to send parts of the bitmapped
+	packfile verbatim. When "multi", and when a multi-pack
+	reachability bitmap is available, pack-objects will try to send
+	parts of all packs in the MIDX.
++
+If only a single pack bitmap is available, and `pack.allowPackReuse`
+is set to "multi", reuse parts of just the bitmapped packfile. This
+can reduce memory and CPU usage to serve fetches, but might result in
+sending a slightly larger pack. Defaults to true.
+
+pack.island::
+	An extended regular expression configuring a set of delta
+	islands. See "DELTA ISLANDS" in linkgit:git-pack-objects[1]
+	for details.
+
+pack.islandCore::
+	Specify an island name which gets to have its objects be
+	packed first. This creates a kind of pseudo-pack at the front
+	of one pack, so that the objects from the specified island are
+	hopefully faster to copy into any pack that should be served
+	to a user requesting these objects. In practice this means
+	that the island specified should likely correspond to what is
+	the most commonly cloned in the repo. See also "DELTA ISLANDS"
+	in linkgit:git-pack-objects[1].
+
+pack.deltaCacheSize::
+	The maximum memory in bytes used for caching deltas in
+	linkgit:git-pack-objects[1] before writing them out to a pack.
+	This cache is used to speed up the writing object phase by not
+	having to recompute the final delta result once the best match
+	for all objects is found.  Repacking large repositories on machines
+	which are tight with memory might be badly impacted by this though,
+	especially if this cache pushes the system into swapping.
+	A value of 0 means no limit. The smallest size of 1 byte may be
+	used to virtually disable this cache. Defaults to 256 MiB.
+
+pack.deltaCacheLimit::
+	The maximum size of a delta, that is cached in
+	linkgit:git-pack-objects[1]. This cache is used to speed up the
+	writing object phase by not having to recompute the final delta
+	result once the best match for all objects is found.
+	Defaults to 1000. Maximum value is 65535.
+
+pack.threads::
+	Specifies the number of threads to spawn when searching for best
+	delta matches.  This requires that linkgit:git-pack-objects[1]
+	be compiled with pthreads otherwise this option is ignored with a
+	warning. This is meant to reduce packing time on multiprocessor
+	machines. The required amount of memory for the delta search window
+	is however multiplied by the number of threads.
+	Specifying 0 will cause Git to auto-detect the number of CPUs
+	and set the number of threads accordingly.
+
+pack.indexVersion::
+	Specify the default pack index version.  Valid values are 1 for
+	legacy pack index used by Git versions prior to 1.5.2, and 2 for
+	the new pack index with capabilities for packs larger than 4 GB
+	as well as proper protection against the repacking of corrupted
+	packs.  Version 2 is the default.  Note that version 2 is enforced
+	and this config option is ignored whenever the corresponding pack is
+	larger than 2 GB.
++
+If you have an old Git that does not understand the version 2 `*.idx` file,
+cloning or fetching over a non-native protocol (e.g. "http")
+that will copy both `*.pack` file and corresponding `*.idx` file from the
+other side may give you a repository that cannot be accessed with your
+older version of Git. If the `*.pack` file is smaller than 2 GB, however,
+you can use linkgit:git-index-pack[1] on the *.pack file to regenerate
+the `*.idx` file.
+
+pack.packSizeLimit::
+	The maximum size of a pack.  This setting only affects
+	packing to a file when repacking, i.e. the git:// protocol
+	is unaffected.  It can be overridden by the `--max-pack-size`
+	option of linkgit:git-repack[1].  Reaching this limit results
+	in the creation of multiple packfiles.
++
+Note that this option is rarely useful, and may result in a larger total
+on-disk size (because Git will not store deltas between packs) and
+worse runtime performance (object lookup within multiple packs is
+slower than a single pack, and optimizations like reachability bitmaps
+cannot cope with multiple packs).
++
+If you need to actively run Git using smaller packfiles (e.g., because your
+filesystem does not support large files), this option may help. But if
+your goal is to transmit a packfile over a medium that supports limited
+sizes (e.g., removable media that cannot store the whole repository),
+you are likely better off creating a single large packfile and splitting
+it using a generic multi-volume archive tool (e.g., Unix `split`).
++
+The minimum size allowed is limited to 1 MiB. The default is unlimited.
+Common unit suffixes of 'k', 'm', or 'g' are supported.
+
+pack.useBitmaps::
+	When true, git will use pack bitmaps (if available) when packing
+	to stdout (e.g., during the server side of a fetch). Defaults to
+	true. You should not generally need to turn this off unless
+	you are debugging pack bitmaps.
+
+pack.useBitmapBoundaryTraversal::
+	When true, Git will use an experimental algorithm for computing
+	reachability queries with bitmaps. Instead of building up
+	complete bitmaps for all of the negated tips and then OR-ing
+	them together, consider negated tips with existing bitmaps as
+	additive (i.e. OR-ing them into the result if they exist,
+	ignoring them otherwise), and build up a bitmap at the boundary
+	instead.
++
+When using this algorithm, Git may include too many objects as a result
+of not opening up trees belonging to certain UNINTERESTING commits. This
+inexactness matches the non-bitmap traversal algorithm.
++
+In many cases, this can provide a speed-up over the exact algorithm,
+particularly when there is poor bitmap coverage of the negated side of
+the query.
+
+pack.useSparse::
+	When true, git will default to using the '--sparse' option in
+	'git pack-objects' when the '--revs' option is present. This
+	algorithm only walks trees that appear in paths that introduce new
+	objects. This can have significant performance benefits when
+	computing a pack to send a small change. However, it is possible
+	that extra objects are added to the pack-file if the included
+	commits contain certain types of direct renames. Default is
+	`true`.
+
+pack.preferBitmapTips::
+	When selecting which commits will receive bitmaps, prefer a
+	commit at the tip of any reference that is a suffix of any value
+	of this configuration over any other commits in the "selection
+	window".
++
+Note that setting this configuration to `refs/foo` does not mean that
+the commits at the tips of `refs/foo/bar` and `refs/foo/baz` will
+necessarily be selected. This is because commits are selected for
+bitmaps from within a series of windows of variable length.
++
+If a commit at the tip of any reference which is a suffix of any value
+of this configuration is seen in a window, it is immediately given
+preference over any other commit in that window.
+
+pack.writeBitmaps (deprecated)::
+	This is a deprecated synonym for `repack.writeBitmaps`.
+
+pack.writeBitmapHashCache::
+	When true, git will include a "hash cache" section in the bitmap
+	index (if one is written). This cache can be used to feed git's
+	delta heuristics, potentially leading to better deltas between
+	bitmapped and non-bitmapped objects (e.g., when serving a fetch
+	between an older, bitmapped pack and objects that have been
+	pushed since the last gc). The downside is that it consumes 4
+	bytes per object of disk space. Defaults to true.
++
+When writing a multi-pack reachability bitmap, no new namehashes are
+computed; instead, any namehashes stored in an existing bitmap are
+permuted into their appropriate location when writing a new bitmap.
+
+pack.writeBitmapLookupTable::
+	When true, Git will include a "lookup table" section in the
+	bitmap index (if one is written). This table is used to defer
+	loading individual bitmaps as late as possible. This can be
+	beneficial in repositories that have relatively large bitmap
+	indexes. Defaults to false.
+
+pack.readReverseIndex::
+	When true, git will read any .rev file(s) that may be available
+	(see: linkgit:gitformat-pack[5]). When false, the reverse index
+	will be generated from scratch and stored in memory. Defaults to
+	true.
+
+pack.writeReverseIndex::
+	When true, git will write a corresponding .rev file (see:
+	linkgit:gitformat-pack[5])
+	for each new packfile that it writes in all places except for
+	linkgit:git-fast-import[1] and in the bulk checkin mechanism.
+	Defaults to true.
+
+
+pager.<cmd>::
+	If the value is boolean, turns on or off pagination of the
+	output of a particular Git subcommand when writing to a tty.
+	Otherwise, turns on pagination for the subcommand using the
+	pager specified by the value of `pager.<cmd>`.  If `--paginate`
+	or `--no-pager` is specified on the command line, it takes
+	precedence over this option.  To disable pagination for all
+	commands, set `core.pager` or `GIT_PAGER` to `cat`.
+
+
+pretty.<name>::
+	Alias for a --pretty= format string, as specified in
+	linkgit:git-log[1]. Any aliases defined here can be used just
+	as the built-in pretty formats could. For example,
+	running `git config pretty.changelog "format:* %H %s"`
+	would cause the invocation `git log --pretty=changelog`
+	to be equivalent to running `git log "--pretty=format:* %H %s"`.
+	Note that an alias with the same name as a built-in format
+	will be silently ignored.
+
+
+promisor.quiet::
+	If set to "true" assume `--quiet` when fetching additional
+	objects for a partial clone.
+
+
+protocol.allow::
+	If set, provide a user defined default policy for all protocols which
+	don't explicitly have a policy (`protocol.<name>.allow`).  By default,
+	if unset, known-safe protocols (http, https, git, ssh) have a
+	default policy of `always`, known-dangerous protocols (ext) have a
+	default policy of `never`, and all other protocols (including file)
+	have a default policy of `user`.  Supported policies:
++
+--
+
+* `always` - protocol is always able to be used.
+
+* `never` - protocol is never able to be used.
+
+* `user` - protocol is only able to be used when `GIT_PROTOCOL_FROM_USER` is
+  either unset or has a value of 1.  This policy should be used when you want a
+  protocol to be directly usable by the user but don't want it used by commands which
+  execute clone/fetch/push commands without user input, e.g. recursive
+  submodule initialization.
+
+--
+
+protocol.<name>.allow::
+	Set a policy to be used by protocol `<name>` with clone/fetch/push
+	commands. See `protocol.allow` above for the available policies.
++
+The protocol names currently used by git are:
++
+--
+  - `file`: any local file-based path (including `file://` URLs,
+    or local paths)
+
+  - `git`: the anonymous git protocol over a direct TCP
+    connection (or proxy, if configured)
+
+  - `ssh`: git over ssh (including `host:path` syntax,
+    `ssh://`, etc).
+
+  - `http`: git over http, both "smart http" and "dumb http".
+    Note that this does _not_ include `https`; if you want to configure
+    both, you must do so individually.
+
+  - any external helpers are named by their protocol (e.g., use
+    `hg` to allow the `git-remote-hg` helper)
+--
+
+protocol.version::
+	If set, clients will attempt to communicate with a server
+	using the specified protocol version.  If the server does
+	not support it, communication falls back to version 0.
+	If unset, the default is `2`.
+	Supported versions:
++
+--
+
+* `0` - the original wire protocol.
+
+* `1` - the original wire protocol with the addition of a version string
+  in the initial response from the server.
+
+* `2` - Wire protocol version 2, see linkgit:gitprotocol-v2[5].
+
+--
+
+
+pull.ff::
+	By default, Git does not create an extra merge commit when merging
+	a commit that is a descendant of the current commit. Instead, the
+	tip of the current branch is fast-forwarded. When set to `false`,
+	this variable tells Git to create an extra merge commit in such
+	a case (equivalent to giving the `--no-ff` option from the command
+	line). When set to `only`, only such fast-forward merges are
+	allowed (equivalent to giving the `--ff-only` option from the
+	command line). This setting overrides `merge.ff` when pulling.
+
+pull.rebase::
+	When true, rebase branches on top of the fetched branch, instead
+	of merging the default branch from the default remote when "git
+	pull" is run. See "branch.<name>.rebase" for setting this on a
+	per-branch basis.
++
+When `merges` (or just 'm'), pass the `--rebase-merges` option to 'git rebase'
+so that the local merge commits are included in the rebase (see
+linkgit:git-rebase[1] for details).
++
+When the value is `interactive` (or just 'i'), the rebase is run in interactive
+mode.
++
+*NOTE*: this is a possibly dangerous operation; do *not* use
+it unless you understand the implications (see linkgit:git-rebase[1]
+for details).
+
+pull.octopus::
+	The default merge strategy to use when pulling multiple branches
+	at once.
+
+pull.twohead::
+	The default merge strategy to use when pulling a single branch.
+
+
+push.autoSetupRemote::
+	If set to "true" assume `--set-upstream` on default push when no
+	upstream tracking exists for the current branch; this option
+	takes effect with push.default options 'simple', 'upstream',
+	and 'current'. It is useful if by default you want new branches
+	to be pushed to the default remote (like the behavior of
+	'push.default=current') and you also want the upstream tracking
+	to be set. Workflows most likely to benefit from this option are
+	'simple' central workflows where all branches are expected to
+	have the same name on the remote.
+
+push.default::
+	Defines the action `git push` should take if no refspec is
+	given (whether from the command-line, config, or elsewhere).
+	Different values are well-suited for
+	specific workflows; for instance, in a purely central workflow
+	(i.e. the fetch source is equal to the push destination),
+	`upstream` is probably what you want.  Possible values are:
++
+--
+
+* `nothing` - do not push anything (error out) unless a refspec is
+  given. This is primarily meant for people who want to
+  avoid mistakes by always being explicit.
+
+* `current` - push the current branch to update a branch with the same
+  name on the receiving end.  Works in both central and non-central
+  workflows.
+
+* `upstream` - push the current branch back to the branch whose
+  changes are usually integrated into the current branch (which is
+  called `@{upstream}`).  This mode only makes sense if you are
+  pushing to the same repository you would normally pull from
+  (i.e. central workflow).
+
+* `tracking` - This is a deprecated synonym for `upstream`.
+
+* `simple` - push the current branch with the same name on the remote.
++
+If you are working on a centralized workflow (pushing to the same repository you
+pull from, which is typically `origin`), then you need to configure an upstream
+branch with the same name.
++
+This mode is the default since Git 2.0, and is the safest option suited for
+beginners.
+
+* `matching` - push all branches having the same name on both ends.
+  This makes the repository you are pushing to remember the set of
+  branches that will be pushed out (e.g. if you always push 'maint'
+  and 'master' there and no other branches, the repository you push
+  to will have these two branches, and your local 'maint' and
+  'master' will be pushed there).
++
+To use this mode effectively, you have to make sure _all_ the
+branches you would push out are ready to be pushed out before
+running 'git push', as the whole point of this mode is to allow you
+to push all of the branches in one go.  If you usually finish work
+on only one branch and push out the result, while other branches are
+unfinished, this mode is not for you.  Also this mode is not
+suitable for pushing into a shared central repository, as other
+people may add new branches there, or update the tip of existing
+branches outside your control.
++
+This used to be the default, but not since Git 2.0 (`simple` is the
+new default).
+
+--
+
+push.followTags::
+	If set to true, enable `--follow-tags` option by default.  You
+	may override this configuration at time of push by specifying
+	`--no-follow-tags`.
+
+push.gpgSign::
+	May be set to a boolean value, or the string 'if-asked'. A true
+	value causes all pushes to be GPG signed, as if `--signed` is
+	passed to linkgit:git-push[1]. The string 'if-asked' causes
+	pushes to be signed if the server supports it, as if
+	`--signed=if-asked` is passed to 'git push'. A false value may
+	override a value from a lower-priority config file. An explicit
+	command-line flag always overrides this config option.
+
+push.pushOption::
+	When no `--push-option=<option>` argument is given from the
+	command line, `git push` behaves as if each <value> of
+	this variable is given as `--push-option=<value>`.
++
+This is a multi-valued variable, and an empty value can be used in a
+higher priority configuration file (e.g. `.git/config` in a
+repository) to clear the values inherited from a lower priority
+configuration files (e.g. `$HOME/.gitconfig`).
++
+----
+
+Example:
+
+/etc/gitconfig
+  push.pushoption = a
+  push.pushoption = b
+
+~/.gitconfig
+  push.pushoption = c
+
+repo/.git/config
+  push.pushoption =
+  push.pushoption = b
+
+This will result in only b (a and c are cleared).
+
+----
+
+push.recurseSubmodules::
+	May be "check", "on-demand", "only", or "no", with the same behavior
+	as that of "push --recurse-submodules".
+	If not set, 'no' is used by default, unless 'submodule.recurse' is
+	set (in which case a 'true' value means 'on-demand').
+
+push.useForceIfIncludes::
+	If set to "true", it is equivalent to specifying
+	`--force-if-includes` as an option to linkgit:git-push[1]
+	in the command line. Adding `--no-force-if-includes` at the
+	time of push overrides this configuration setting.
+
+push.negotiate::
+	If set to "true", attempt to reduce the size of the packfile
+	sent by rounds of negotiation in which the client and the
+	server attempt to find commits in common. If "false", Git will
+	rely solely on the server's ref advertisement to find commits
+	in common.
+
+push.useBitmaps::
+	If set to "false", disable use of bitmaps for "git push" even if
+	`pack.useBitmaps` is "true", without preventing other git operations
+	from using bitmaps. Default is true.
+
+
+rebase.backend::
+	Default backend to use for rebasing.  Possible choices are
+	'apply' or 'merge'.  In the future, if the merge backend gains
+	all remaining capabilities of the apply backend, this setting
+	may become unused.
+
+rebase.stat::
+	Whether to show a diffstat of what changed upstream since the last
+	rebase. False by default.
+
+rebase.autoSquash::
+	If set to true, enable the `--autosquash` option of
+	linkgit:git-rebase[1] by default for interactive mode.
+	This can be overridden with the `--no-autosquash` option.
+
+rebase.autoStash::
+	When set to true, automatically create a temporary stash entry
+	before the operation begins, and apply it after the operation
+	ends.  This means that you can run rebase on a dirty worktree.
+	However, use with care: the final stash application after a
+	successful rebase might result in non-trivial conflicts.
+	This option can be overridden by the `--no-autostash` and
+	`--autostash` options of linkgit:git-rebase[1].
+	Defaults to false.
+
+rebase.updateRefs::
+	If set to true enable `--update-refs` option by default.
+
+rebase.missingCommitsCheck::
+	If set to "warn", git rebase -i will print a warning if some
+	commits are removed (e.g. a line was deleted), however the
+	rebase will still proceed. If set to "error", it will print
+	the previous warning and stop the rebase, 'git rebase
+	--edit-todo' can then be used to correct the error. If set to
+	"ignore", no checking is done.
+	To drop a commit without warning or error, use the `drop`
+	command in the todo list.
+	Defaults to "ignore".
+
+rebase.instructionFormat::
+	A format string, as specified in linkgit:git-log[1], to be used for the
+	todo list during an interactive rebase.  The format will
+	automatically have the commit hash prepended to the format.
+
+rebase.abbreviateCommands::
+	If set to true, `git rebase` will use abbreviated command names in the
+	todo list resulting in something like this:
++
+-------------------------------------------
+	p deadbee The oneline of the commit
+	p fa1afe1 The oneline of the next commit
+	...
+-------------------------------------------
++
+instead of:
++
+-------------------------------------------
+	pick deadbee The oneline of the commit
+	pick fa1afe1 The oneline of the next commit
+	...
+-------------------------------------------
++
+Defaults to false.
+
+rebase.rescheduleFailedExec::
+	Automatically reschedule `exec` commands that failed. This only makes
+	sense in interactive mode (or when an `--exec` option was provided).
+	This is the same as specifying the `--reschedule-failed-exec` option.
+
+rebase.forkPoint::
+	If set to false set `--no-fork-point` option by default.
+
+rebase.rebaseMerges::
+	Whether and how to set the `--rebase-merges` option by default. Can
+	be `rebase-cousins`, `no-rebase-cousins`, or a boolean. Setting to
+	true or to `no-rebase-cousins` is equivalent to
+	`--rebase-merges=no-rebase-cousins`, setting to `rebase-cousins` is
+	equivalent to `--rebase-merges=rebase-cousins`, and setting to false is
+	equivalent to `--no-rebase-merges`. Passing `--rebase-merges` on the
+	command line, with or without an argument, overrides any
+	`rebase.rebaseMerges` configuration.
+
+rebase.maxLabelLength::
+	When generating label names from commit subjects, truncate the names to
+	this length. By default, the names are truncated to a little less than
+	`NAME_MAX` (to allow e.g. `.lock` files to be written for the
+	corresponding loose refs).
+
+
+receive.advertiseAtomic::
+	By default, git-receive-pack will advertise the atomic push
+	capability to its clients. If you don't want to advertise this
+	capability, set this variable to false.
+
+receive.advertisePushOptions::
+	When set to true, git-receive-pack will advertise the push options
+	capability to its clients. False by default.
+
+receive.autogc::
+	By default, git-receive-pack will run "git maintenance run --auto" after
+	receiving data from git-push and updating refs.  You can stop
+	it by setting this variable to false.
+
+receive.certNonceSeed::
+	By setting this variable to a string, `git receive-pack`
+	will accept a `git push --signed` and verify it by using
+	a "nonce" protected by HMAC using this string as a secret
+	key.
+
+receive.certNonceSlop::
+	When a `git push --signed` sends a push certificate with a
+	"nonce" that was issued by a receive-pack serving the same
+	repository within this many seconds, export the "nonce"
+	found in the certificate to `GIT_PUSH_CERT_NONCE` to the
+	hooks (instead of what the receive-pack asked the sending
+	side to include).  This may allow writing checks in
+	`pre-receive` and `post-receive` a bit easier.  Instead of
+	checking `GIT_PUSH_CERT_NONCE_SLOP` environment variable
+	that records by how many seconds the nonce is stale to
+	decide if they want to accept the certificate, they only
+	can check `GIT_PUSH_CERT_NONCE_STATUS` is `OK`.
+
+receive.fsckObjects::
+	If it is set to true, git-receive-pack will check all received
+	objects. See `transfer.fsckObjects` for what's checked.
+	Defaults to false. If not set, the value of
+	`transfer.fsckObjects` is used instead.
+
+receive.fsck.<msg-id>::
+	Acts like `fsck.<msg-id>`, but is used by
+	linkgit:git-receive-pack[1] instead of
+	linkgit:git-fsck[1]. See the `fsck.<msg-id>` documentation for
+	details.
+
+receive.fsck.skipList::
+	Acts like `fsck.skipList`, but is used by
+	linkgit:git-receive-pack[1] instead of
+	linkgit:git-fsck[1]. See the `fsck.skipList` documentation for
+	details.
+
+receive.keepAlive::
+	After receiving the pack from the client, `receive-pack` may
+	produce no output (if `--quiet` was specified) while processing
+	the pack, causing some networks to drop the TCP connection.
+	With this option set, if `receive-pack` does not transmit
+	any data in this phase for `receive.keepAlive` seconds, it will
+	send a short keepalive packet.  The default is 5 seconds; set
+	to 0 to disable keepalives entirely.
+
+receive.unpackLimit::
+	If the number of objects received in a push is below this
+	limit then the objects will be unpacked into loose object
+	files. However if the number of received objects equals or
+	exceeds this limit then the received pack will be stored as
+	a pack, after adding any missing delta bases.  Storing the
+	pack from a push can make the push operation complete faster,
+	especially on slow filesystems.  If not set, the value of
+	`transfer.unpackLimit` is used instead.
+
+receive.maxInputSize::
+	If the size of the incoming pack stream is larger than this
+	limit, then git-receive-pack will error out, instead of
+	accepting the pack file. If not set or set to 0, then the size
+	is unlimited.
+
+receive.denyDeletes::
+	If set to true, git-receive-pack will deny a ref update that deletes
+	the ref. Use this to prevent such a ref deletion via a push.
+
+receive.denyDeleteCurrent::
+	If set to true, git-receive-pack will deny a ref update that
+	deletes the currently checked out branch of a non-bare repository.
+
+receive.denyCurrentBranch::
+	If set to true or "refuse", git-receive-pack will deny a ref update
+	to the currently checked out branch of a non-bare repository.
+	Such a push is potentially dangerous because it brings the HEAD
+	out of sync with the index and working tree. If set to "warn",
+	print a warning of such a push to stderr, but allow the push to
+	proceed. If set to false or "ignore", allow such pushes with no
+	message. Defaults to "refuse".
++
+Another option is "updateInstead" which will update the working
+tree if pushing into the current branch.  This option is
+intended for synchronizing working directories when one side is not easily
+accessible via interactive ssh (e.g. a live web site, hence the requirement
+that the working directory be clean). This mode also comes in handy when
+developing inside a VM to test and fix code on different Operating Systems.
++
+By default, "updateInstead" will refuse the push if the working tree or
+the index have any difference from the HEAD, but the `push-to-checkout`
+hook can be used to customize this.  See linkgit:githooks[5].
+
+receive.denyNonFastForwards::
+	If set to true, git-receive-pack will deny a ref update which is
+	not a fast-forward. Use this to prevent such an update via a push,
+	even if that push is forced. This configuration variable is
+	set when initializing a shared repository.
+
+receive.hideRefs::
+	This variable is the same as `transfer.hideRefs`, but applies
+	only to `receive-pack` (and so affects pushes, but not fetches).
+	An attempt to update or delete a hidden ref by `git push` is
+	rejected.
+
+receive.procReceiveRefs::
+	This is a multi-valued variable that defines reference prefixes
+	to match the commands in `receive-pack`.  Commands matching the
+	prefixes will be executed by an external hook "proc-receive",
+	instead of the internal `execute_commands` function.  If this
+	variable is not defined, the "proc-receive" hook will never be
+	used, and all commands will be executed by the internal
+	`execute_commands` function.
++
+For example, if this variable is set to "refs/for", pushing to reference
+such as "refs/for/master" will not create or update a reference named
+"refs/for/master", but may create or update a pull request directly by
+running the hook "proc-receive".
++
+Optional modifiers can be provided in the beginning of the value to filter
+commands for specific actions: create (a), modify (m), delete (d).
+A `!` can be included in the modifiers to negate the reference prefix entry.
+E.g.:
++
+	git config --system --add receive.procReceiveRefs ad:refs/heads
+	git config --system --add receive.procReceiveRefs !:refs/heads
+
+receive.updateServerInfo::
+	If set to true, git-receive-pack will run git-update-server-info
+	after receiving data from git-push and updating refs.
+
+receive.shallowUpdate::
+	If set to true, .git/shallow can be updated when new refs
+	require new shallow roots. Otherwise those refs are rejected.
+
+
+reftable.blockSize::
+	The size in bytes used by the reftable backend when writing blocks.
+	The block size is determined by the writer, and does not have to be a
+	power of 2. The block size must be larger than the longest reference
+	name or log entry used in the repository, as references cannot span
+	blocks.
++
+Powers of two that are friendly to the virtual memory system or
+filesystem (such as 4kB or 8kB) are recommended. Larger sizes (64kB) can
+yield better compression, with a possible increased cost incurred by
+readers during access.
++
+The largest block size is `16777215` bytes (15.99 MiB). The default value is
+`4096` bytes (4kB). A value of `0` will use the default value.
+
+reftable.restartInterval::
+	The interval at which to create restart points. The reftable backend
+	determines the restart points at file creation. Every 16 may be
+	more suitable for smaller block sizes (4k or 8k), every 64 for larger
+	block sizes (64k).
++
+More frequent restart points reduces prefix compression and increases
+space consumed by the restart table, both of which increase file size.
++
+Less frequent restart points makes prefix compression more effective,
+decreasing overall file size, with increased penalties for readers
+walking through more records after the binary search step.
++
+A maximum of `65535` restart points per block is supported.
++
+The default value is to create restart points every 16 records. A value of `0`
+will use the default value.
+
+reftable.indexObjects::
+	Whether the reftable backend shall write object blocks. Object blocks
+	are a reverse mapping of object ID to the references pointing to them.
++
+The default value is `true`.
+
+reftable.geometricFactor::
+	Whenever the reftable backend appends a new table to the stack, it
+	performs auto compaction to ensure that there is only a handful of
+	tables. The backend does this by ensuring that tables form a geometric
+	sequence regarding the respective sizes of each table.
++
+By default, the geometric sequence uses a factor of 2, meaning that for any
+table, the next-biggest table must at least be twice as big. A maximum factor
+of 256 is supported.
+
+
+remote.pushDefault::
+	The remote to push to by default.  Overrides
+	`branch.<name>.remote` for all branches, and is overridden by
+	`branch.<name>.pushRemote` for specific branches.
+
+remote.<name>.url::
+	The URL of a remote repository.  See linkgit:git-fetch[1] or
+	linkgit:git-push[1]. A configured remote can have multiple URLs;
+	in this case the first is used for fetching, and all are used
+	for pushing (assuming no `remote.<name>.pushurl` is defined).
+	Setting this key to the empty string clears the list of urls,
+	allowing you to override earlier config.
+
+remote.<name>.pushurl::
+	The push URL of a remote repository.  See linkgit:git-push[1].
+	If a `pushurl` option is present in a configured remote, it
+	is used for pushing instead of `remote.<name>.url`. A configured
+	remote can have multiple push URLs; in this case a push goes to
+	all of them. Setting this key to the empty string clears the
+	list of urls, allowing you to override earlier config.
+
+remote.<name>.proxy::
+	For remotes that require curl (http, https and ftp), the URL to
+	the proxy to use for that remote.  Set to the empty string to
+	disable proxying for that remote.
+
+remote.<name>.proxyAuthMethod::
+	For remotes that require curl (http, https and ftp), the method to use for
+	authenticating against the proxy in use (probably set in
+	`remote.<name>.proxy`). See `http.proxyAuthMethod`.
+
+remote.<name>.fetch::
+	The default set of "refspec" for linkgit:git-fetch[1]. See
+	linkgit:git-fetch[1].
+
+remote.<name>.push::
+	The default set of "refspec" for linkgit:git-push[1]. See
+	linkgit:git-push[1].
+
+remote.<name>.mirror::
+	If true, pushing to this remote will automatically behave
+	as if the `--mirror` option was given on the command line.
+
+remote.<name>.skipDefaultUpdate::
+	A deprecated synonym to `remote.<name>.skipFetchAll` (if
+	both are set in the configuration files with different
+	values, the value of the last occurrence will be used).
+
+remote.<name>.skipFetchAll::
+	If true, this remote will be skipped when updating
+	using linkgit:git-fetch[1], the `update` subcommand of
+	linkgit:git-remote[1], and ignored by the prefetch task
+	of `git maitenance`.
+
+remote.<name>.receivepack::
+	The default program to execute on the remote side when pushing.  See
+	option --receive-pack of linkgit:git-push[1].
+
+remote.<name>.uploadpack::
+	The default program to execute on the remote side when fetching.  See
+	option --upload-pack of linkgit:git-fetch-pack[1].
+
+remote.<name>.tagOpt::
+	Setting this value to --no-tags disables automatic tag following when
+	fetching from remote <name>. Setting it to --tags will fetch every
+	tag from remote <name>, even if they are not reachable from remote
+	branch heads. Passing these flags directly to linkgit:git-fetch[1] can
+	override this setting. See options --tags and --no-tags of
+	linkgit:git-fetch[1].
+
+remote.<name>.vcs::
+	Setting this to a value <vcs> will cause Git to interact with
+	the remote with the git-remote-<vcs> helper.
+
+remote.<name>.prune::
+	When set to true, fetching from this remote by default will also
+	remove any remote-tracking references that no longer exist on the
+	remote (as if the `--prune` option was given on the command line).
+	Overrides `fetch.prune` settings, if any.
+
+remote.<name>.pruneTags::
+	When set to true, fetching from this remote by default will also
+	remove any local tags that no longer exist on the remote if pruning
+	is activated in general via `remote.<name>.prune`, `fetch.prune` or
+	`--prune`. Overrides `fetch.pruneTags` settings, if any.
++
+See also `remote.<name>.prune` and the PRUNING section of
+linkgit:git-fetch[1].
+
+remote.<name>.promisor::
+	When set to true, this remote will be used to fetch promisor
+	objects.
+
+remote.<name>.partialclonefilter::
+	The filter that will be applied when fetching from this	promisor remote.
+	Changing or clearing this value will only affect fetches for new commits.
+	To fetch associated objects for commits already present in the local object
+	database, use the `--refetch` option of linkgit:git-fetch[1].
+
+
+remotes.<group>::
+	The list of remotes which are fetched by "git remote update
+	<group>".  See linkgit:git-remote[1].
+
+
+repack.useDeltaBaseOffset::
+	By default, linkgit:git-repack[1] creates packs that use
+	delta-base offset. If you need to share your repository with
+	Git older than version 1.4.4, either directly or via a dumb
+	protocol such as http, then you need to set this option to
+	"false" and repack. Access from old Git versions over the
+	native protocol are unaffected by this option.
+
+repack.packKeptObjects::
+	If set to true, makes `git repack` act as if
+	`--pack-kept-objects` was passed. See linkgit:git-repack[1] for
+	details. Defaults to `false` normally, but `true` if a bitmap
+	index is being written (either via `--write-bitmap-index` or
+	`repack.writeBitmaps`).
+
+repack.useDeltaIslands::
+	If set to true, makes `git repack` act as if `--delta-islands`
+	was passed. Defaults to `false`.
+
+repack.writeBitmaps::
+	When true, git will write a bitmap index when packing all
+	objects to disk (e.g., when `git repack -a` is run).  This
+	index can speed up the "counting objects" phase of subsequent
+	packs created for clones and fetches, at the cost of some disk
+	space and extra time spent on the initial repack.  This has
+	no effect if multiple packfiles are created.
+	Defaults to true on bare repos, false otherwise.
+
+repack.updateServerInfo::
+	If set to false, linkgit:git-repack[1] will not run
+	linkgit:git-update-server-info[1]. Defaults to true. Can be overridden
+	when true by the `-n` option of linkgit:git-repack[1].
+
+repack.cruftWindow::
+repack.cruftWindowMemory::
+repack.cruftDepth::
+repack.cruftThreads::
+	Parameters used by linkgit:git-pack-objects[1] when generating
+	a cruft pack and the respective parameters are not given over
+	the command line. See similarly named `pack.*` configuration
+	variables for defaults and meaning.
+
+
+rerere.autoUpdate::
+	When set to true, `git-rerere` updates the index with the
+	resulting contents after it cleanly resolves conflicts using
+	previously recorded resolutions.  Defaults to false.
+
+rerere.enabled::
+	Activate recording of resolved conflicts, so that identical
+	conflict hunks can be resolved automatically, should they be
+	encountered again.  By default, linkgit:git-rerere[1] is
+	enabled if there is an `rr-cache` directory under the
+	`$GIT_DIR`, e.g. if "rerere" was previously used in the
+	repository.
+
+
+revert.reference::
+	Setting this variable to true makes `git revert` behave
+	as if the `--reference` option is given.
+
+
+safe.bareRepository::
+	Specifies which bare repositories Git will work with. The currently
+	supported values are:
++
+* `all`: Git works with all bare repositories. This is the default.
+* `explicit`: Git only works with bare repositories specified via
+  the top-level `--git-dir` command-line option, or the `GIT_DIR`
+  environment variable (see linkgit:git[1]).
++
+If you do not use bare repositories in your workflow, then it may be
+beneficial to set `safe.bareRepository` to `explicit` in your global
+config. This will protect you from attacks that involve cloning a
+repository that contains a bare repository and running a Git command
+within that directory.
++
+This config setting is only respected in protected configuration (see
+<<SCOPES>>). This prevents untrusted repositories from tampering with
+this value.
+
+safe.directory::
+	These config entries specify Git-tracked directories that are
+	considered safe even if they are owned by someone other than the
+	current user. By default, Git will refuse to even parse a Git
+	config of a repository owned by someone else, let alone run its
+	hooks, and this config setting allows users to specify exceptions,
+	e.g. for intentionally shared repositories (see the `--shared`
+	option in linkgit:git-init[1]).
++
+This is a multi-valued setting, i.e. you can add more than one directory
+via `git config --add`. To reset the list of safe directories (e.g. to
+override any such directories specified in the system config), add a
+`safe.directory` entry with an empty value.
++
+This config setting is only respected in protected configuration (see
+<<SCOPES>>). This prevents untrusted repositories from tampering with this
+value.
++
+The value of this setting is interpolated, i.e. `~/<path>` expands to a
+path relative to the home directory and `%(prefix)/<path>` expands to a
+path relative to Git's (runtime) prefix.
++
+To completely opt-out of this security check, set `safe.directory` to the
+string `*`. This will allow all repositories to be treated as if their
+directory was listed in the `safe.directory` list. If `safe.directory=*`
+is set in system config and you want to re-enable this protection, then
+initialize your list with an empty value before listing the repositories
+that you deem safe.  Giving a directory with `/*` appended to it will
+allow access to all repositories under the named directory.
++
+As explained, Git only allows you to access repositories owned by
+yourself, i.e. the user who is running Git, by default.  When Git
+is running as 'root' in a non Windows platform that provides sudo,
+however, git checks the SUDO_UID environment variable that sudo creates
+and will allow access to the uid recorded as its value in addition to
+the id from 'root'.
+This is to make it easy to perform a common sequence during installation
+"make && sudo make install".  A git process running under 'sudo' runs as
+'root' but the 'sudo' command exports the environment variable to record
+which id the original user has.
+If that is not what you would prefer and want git to only trust
+repositories that are owned by root instead, then you can remove
+the `SUDO_UID` variable from root's environment before invoking git.
+
+
+sendemail.identity::
+	A configuration identity. When given, causes values in the
+	'sendemail.<identity>' subsection to take precedence over
+	values in the 'sendemail' section. The default identity is
+	the value of `sendemail.identity`.
+
+sendemail.smtpEncryption::
+	See linkgit:git-send-email[1] for description.  Note that this
+	setting is not subject to the 'identity' mechanism.
+
+sendemail.smtpSSLCertPath::
+	Path to ca-certificates (either a directory or a single file).
+	Set it to an empty string to disable certificate verification.
+
+sendemail.<identity>.*::
+	Identity-specific versions of the 'sendemail.*' parameters
+	found below, taking precedence over those when this
+	identity is selected, through either the command-line or
+	`sendemail.identity`.
+
+sendemail.multiEdit::
+	If true (default), a single editor instance will be spawned to edit
+	files you have to edit (patches when `--annotate` is used, and the
+	summary when `--compose` is used). If false, files will be edited one
+	after the other, spawning a new editor each time.
+
+sendemail.confirm::
+	Sets the default for whether to confirm before sending. Must be
+	one of 'always', 'never', 'cc', 'compose', or 'auto'. See `--confirm`
+	in the linkgit:git-send-email[1] documentation for the meaning of these
+	values.
+
+sendemail.aliasesFile::
+	To avoid typing long email addresses, point this to one or more
+	email aliases files.  You must also supply `sendemail.aliasFileType`.
+
+sendemail.aliasFileType::
+	Format of the file(s) specified in sendemail.aliasesFile. Must be
+	one of 'mutt', 'mailrc', 'pine', 'elm', 'gnus', or 'sendmail'.
++
+What an alias file in each format looks like can be found in
+the documentation of the email program of the same name. The
+differences and limitations from the standard formats are
+described below:
++
+--
+sendmail;;
+*	Quoted aliases and quoted addresses are not supported: lines that
+	contain a `"` symbol are ignored.
+*	Redirection to a file (`/path/name`) or pipe (`|command`) is not
+	supported.
+*	File inclusion (`:include: /path/name`) is not supported.
+*	Warnings are printed on the standard error output for any
+	explicitly unsupported constructs, and any other lines that are not
+	recognized by the parser.
+--
+sendemail.annotate::
+sendemail.bcc::
+sendemail.cc::
+sendemail.ccCmd::
+sendemail.chainReplyTo::
+sendemail.envelopeSender::
+sendemail.from::
+sendemail.headerCmd::
+sendemail.signedOffByCc::
+sendemail.smtpPass::
+sendemail.suppressCc::
+sendemail.suppressFrom::
+sendemail.to::
+sendemail.toCmd::
+sendemail.smtpDomain::
+sendemail.smtpServer::
+sendemail.smtpServerPort::
+sendemail.smtpServerOption::
+sendemail.smtpUser::
+sendemail.thread::
+sendemail.transferEncoding::
+sendemail.validate::
+sendemail.xmailer::
+	These configuration variables all provide a default for
+	linkgit:git-send-email[1] command-line options. See its
+	documentation for details.
+
+sendemail.signedOffCc (deprecated)::
+	Deprecated alias for `sendemail.signedOffByCc`.
+
+sendemail.smtpBatchSize::
+	Number of messages to be sent per connection, after that a relogin
+	will happen.  If the value is 0 or undefined, send all messages in
+	one connection.
+	See also the `--batch-size` option of linkgit:git-send-email[1].
+
+sendemail.smtpReloginDelay::
+	Seconds to wait before reconnecting to the smtp server.
+	See also the `--relogin-delay` option of linkgit:git-send-email[1].
+
+sendemail.forbidSendmailVariables::
+	To avoid common misconfiguration mistakes, linkgit:git-send-email[1]
+	will abort with a warning if any configuration options for "sendmail"
+	exist. Set this variable to bypass the check.
+
+
+sequence.editor::
+	Text editor used by `git rebase -i` for editing the rebase instruction file.
+	The value is meant to be interpreted by the shell when it is used.
+	It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable.
+	When not configured, the default commit message editor is used instead.
+
+
+showBranch.default::
+	The default set of branches for linkgit:git-show-branch[1].
+	See linkgit:git-show-branch[1].
+
+
+sparse.expectFilesOutsideOfPatterns::
+	Typically with sparse checkouts, files not matching any
+	sparsity patterns are marked with a SKIP_WORKTREE bit in the
+	index and are missing from the working tree.  Accordingly, Git
+	will ordinarily check whether files with the SKIP_WORKTREE bit
+	are in fact present in the working tree contrary to
+	expectations.  If Git finds any, it marks those paths as
+	present by clearing the relevant SKIP_WORKTREE bits.  This
+	option can be used to tell Git that such
+	present-despite-skipped files are expected and to stop
+	checking for them.
++
+The default is `false`, which allows Git to automatically recover
+from the list of files in the index and working tree falling out of
+sync.
++
+Set this to `true` if you are in a setup where some external factor
+relieves Git of the responsibility for maintaining the consistency
+between the presence of working tree files and sparsity patterns.  For
+example, if you have a Git-aware virtual file system that has a robust
+mechanism for keeping the working tree and the sparsity patterns up to
+date based on access patterns.
++
+Regardless of this setting, Git does not check for
+present-despite-skipped files unless sparse checkout is enabled, so
+this config option has no effect unless `core.sparseCheckout` is
+`true`.
+
+
+splitIndex.maxPercentChange::
+	When the split index feature is used, this specifies the
+	percent of entries the split index can contain compared to the
+	total number of entries in both the split index and the shared
+	index before a new shared index is written.
+	The value should be between 0 and 100. If the value is 0, then
+	a new shared index is always written; if it is 100, a new
+	shared index is never written.
+	By default, the value is 20, so a new shared index is written
+	if the number of entries in the split index would be greater
+	than 20 percent of the total number of entries.
+	See linkgit:git-update-index[1].
+
+splitIndex.sharedIndexExpire::
+	When the split index feature is used, shared index files that
+	were not modified since the time this variable specifies will
+	be removed when a new shared index file is created. The value
+	"now" expires all entries immediately, and "never" suppresses
+	expiration altogether.
+	The default value is "2.weeks.ago".
+	Note that a shared index file is considered modified (for the
+	purpose of expiration) each time a new split-index file is
+	either created based on it or read from it.
+	See linkgit:git-update-index[1].
+
+
+ssh.variant::
+	By default, Git determines the command line arguments to use
+	based on the basename of the configured SSH command (configured
+	using the environment variable `GIT_SSH` or `GIT_SSH_COMMAND` or
+	the config setting `core.sshCommand`). If the basename is
+	unrecognized, Git will attempt to detect support of OpenSSH
+	options by first invoking the configured SSH command with the
+	`-G` (print configuration) option and will subsequently use
+	OpenSSH options (if that is successful) or no options besides
+	the host and remote command (if it fails).
++
+The config variable `ssh.variant` can be set to override this detection.
+Valid values are `ssh` (to use OpenSSH options), `plink`, `putty`,
+`tortoiseplink`, `simple` (no options except the host and remote command).
+The default auto-detection can be explicitly requested using the value
+`auto`.  Any other value is treated as `ssh`.  This setting can also be
+overridden via the environment variable `GIT_SSH_VARIANT`.
++
+The current command-line parameters used for each variant are as
+follows:
++
+--
+
+* `ssh` - [-p port] [-4] [-6] [-o option] [username@]host command
+
+* `simple` - [username@]host command
+
+* `plink` or `putty` - [-P port] [-4] [-6] [username@]host command
+
+* `tortoiseplink` - [-P port] [-4] [-6] -batch [username@]host command
+
+--
++
+Except for the `simple` variant, command-line parameters are likely to
+change as git gains new features.
+
+
+stash.showIncludeUntracked::
+	If this is set to true, the `git stash show` command will show
+	the untracked files of a stash entry.  Defaults to false. See
+	the description of the 'show' command in linkgit:git-stash[1].
+
+stash.showPatch::
+	If this is set to true, the `git stash show` command without an
+	option will show the stash entry in patch form.  Defaults to false.
+	See the description of the 'show' command in linkgit:git-stash[1].
+
+stash.showStat::
+	If this is set to true, the `git stash show` command without an
+	option will show a diffstat of the stash entry.  Defaults to true.
+	See the description of the 'show' command in linkgit:git-stash[1].
+
+
+status.relativePaths::
+	By default, linkgit:git-status[1] shows paths relative to the
+	current directory. Setting this variable to `false` shows paths
+	relative to the repository root (this was the default for Git
+	prior to v1.5.4).
+
+status.short::
+	Set to true to enable --short by default in linkgit:git-status[1].
+	The option --no-short takes precedence over this variable.
+
+status.branch::
+	Set to true to enable --branch by default in linkgit:git-status[1].
+	The option --no-branch takes precedence over this variable.
+
+status.aheadBehind::
+	Set to true to enable `--ahead-behind` and false to enable
+	`--no-ahead-behind` by default in linkgit:git-status[1] for
+	non-porcelain status formats.  Defaults to true.
+
+status.displayCommentPrefix::
+	If set to true, linkgit:git-status[1] will insert a comment
+	prefix before each output line (starting with
+	`core.commentChar`, i.e. `#` by default). This was the
+	behavior of linkgit:git-status[1] in Git 1.8.4 and previous.
+	Defaults to false.
+
+status.renameLimit::
+	The number of files to consider when performing rename detection
+	in linkgit:git-status[1] and linkgit:git-commit[1]. Defaults to
+	the value of diff.renameLimit.
+
+status.renames::
+	Whether and how Git detects renames in linkgit:git-status[1] and
+	linkgit:git-commit[1] .  If set to "false", rename detection is
+	disabled. If set to "true", basic rename detection is enabled.
+	If set to "copies" or "copy", Git will detect copies, as well.
+	Defaults to the value of diff.renames.
+
+status.showStash::
+	If set to true, linkgit:git-status[1] will display the number of
+	entries currently stashed away.
+	Defaults to false.
+
+status.showUntrackedFiles::
+	By default, linkgit:git-status[1] and linkgit:git-commit[1] show
+	files which are not currently tracked by Git. Directories which
+	contain only untracked files, are shown with the directory name
+	only. Showing untracked files means that Git needs to lstat() all
+	the files in the whole repository, which might be slow on some
+	systems. So, this variable controls how the commands display
+	the untracked files. Possible values are:
++
+--
+* `no` - Show no untracked files.
+* `normal` - Show untracked files and directories.
+* `all` - Show also individual files in untracked directories.
+--
++
+If this variable is not specified, it defaults to 'normal'.
+All usual spellings for Boolean value `true` are taken as `normal`
+and `false` as `no`.
+This variable can be overridden with the -u|--untracked-files option
+of linkgit:git-status[1] and linkgit:git-commit[1].
+
+status.submoduleSummary::
+	Defaults to false.
+	If this is set to a non-zero number or true (identical to -1 or an
+	unlimited number), the submodule summary will be enabled and a
+	summary of commits for modified submodules will be shown (see
+	--summary-limit option of linkgit:git-submodule[1]). Please note
+	that the summary output command will be suppressed for all
+	submodules when `diff.ignoreSubmodules` is set to 'all' or only
+	for those submodules where `submodule.<name>.ignore=all`. The only
+	exception to that rule is that status and commit will show staged
+	submodule changes. To
+	also view the summary for ignored submodules you can either use
+	the --ignore-submodules=dirty command-line option or the 'git
+	submodule summary' command, which shows a similar output but does
+	not honor these settings.
+
+
+submodule.<name>.url::
+	The URL for a submodule. This variable is copied from the .gitmodules
+	file to the git config via 'git submodule init'. The user can change
+	the configured URL before obtaining the submodule via 'git submodule
+	update'. If neither submodule.<name>.active nor submodule.active are
+	set, the presence of this variable is used as a fallback to indicate
+	whether the submodule is of interest to git commands.
+	See linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.
+
+submodule.<name>.update::
+	The method by which a submodule is updated by 'git submodule update',
+	which is the only affected command, others such as
+	'git checkout --recurse-submodules' are unaffected. It exists for
+	historical reasons, when 'git submodule' was the only command to
+	interact with submodules; settings like `submodule.active`
+	and `pull.rebase` are more specific. It is populated by
+	`git submodule init` from the linkgit:gitmodules[5] file.
+	See description of 'update' command in linkgit:git-submodule[1].
+
+submodule.<name>.branch::
+	The remote branch name for a submodule, used by `git submodule
+	update --remote`.  Set this option to override the value found in
+	the `.gitmodules` file.  See linkgit:git-submodule[1] and
+	linkgit:gitmodules[5] for details.
+
+submodule.<name>.fetchRecurseSubmodules::
+	This option can be used to control recursive fetching of this
+	submodule. It can be overridden by using the --[no-]recurse-submodules
+	command-line option to "git fetch" and "git pull".
+	This setting will override that from in the linkgit:gitmodules[5]
+	file.
+
+submodule.<name>.ignore::
+	Defines under what circumstances "git status" and the diff family show
+	a submodule as modified. When set to "all", it will never be considered
+	modified (but it will nonetheless show up in the output of status and
+	commit when it has been staged), "dirty" will ignore all changes
+	to the submodule's work tree and
+	takes only differences between the HEAD of the submodule and the commit
+	recorded in the superproject into account. "untracked" will additionally
+	let submodules with modified tracked files in their work tree show up.
+	Using "none" (the default when this option is not set) also shows
+	submodules that have untracked files in their work tree as changed.
+	This setting overrides any setting made in .gitmodules for this submodule,
+	both settings can be overridden on the command line by using the
+	"--ignore-submodules" option. The 'git submodule' commands are not
+	affected by this setting.
+
+submodule.<name>.active::
+	Boolean value indicating if the submodule is of interest to git
+	commands.  This config option takes precedence over the
+	submodule.active config option. See linkgit:gitsubmodules[7] for
+	details.
+
+submodule.active::
+	A repeated field which contains a pathspec used to match against a
+	submodule's path to determine if the submodule is of interest to git
+	commands. See linkgit:gitsubmodules[7] for details.
+
+submodule.recurse::
+	A boolean indicating if commands should enable the `--recurse-submodules`
+	option by default. Defaults to false.
++
+When set to true, it can be deactivated via the
+`--no-recurse-submodules` option. Note that some Git commands
+lacking this option may call some of the above commands affected by
+`submodule.recurse`; for instance `git remote update` will call
+`git fetch` but does not have a `--no-recurse-submodules` option.
+For these commands a workaround is to temporarily change the
+configuration value by using `git -c submodule.recurse=0`.
++
+The following list shows the commands that accept
+`--recurse-submodules` and whether they are supported by this
+setting.
+
+* `checkout`, `fetch`, `grep`, `pull`, `push`, `read-tree`,
+`reset`, `restore` and `switch` are always supported.
+* `clone` and `ls-files` are not supported.
+* `branch` is supported only if `submodule.propagateBranches` is
+enabled
+
+submodule.propagateBranches::
+	[EXPERIMENTAL] A boolean that enables branching support when
+	using `--recurse-submodules` or `submodule.recurse=true`.
+	Enabling this will allow certain commands to accept
+	`--recurse-submodules` and certain commands that already accept
+	`--recurse-submodules` will now consider branches.
+	Defaults to false.
+
+submodule.fetchJobs::
+	Specifies how many submodules are fetched/cloned at the same time.
+	A positive integer allows up to that number of submodules fetched
+	in parallel. A value of 0 will give some reasonable default.
+	If unset, it defaults to 1.
+
+submodule.alternateLocation::
+	Specifies how the submodules obtain alternates when submodules are
+	cloned. Possible values are `no`, `superproject`.
+	By default `no` is assumed, which doesn't add references. When the
+	value is set to `superproject` the submodule to be cloned computes
+	its alternates location relative to the superprojects alternate.
+
+submodule.alternateErrorStrategy::
+	Specifies how to treat errors with the alternates for a submodule
+	as computed via `submodule.alternateLocation`. Possible values are
+	`ignore`, `info`, `die`. Default is `die`. Note that if set to `ignore`
+	or `info`, and if there is an error with the computed alternate, the
+	clone proceeds as if no alternate was specified.
+
+
+tag.forceSignAnnotated::
+	A boolean to specify whether annotated tags created should be GPG signed.
+	If `--annotate` is specified on the command line, it takes
+	precedence over this option.
+
+tag.sort::
+	This variable controls the sort ordering of tags when displayed by
+	linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the
+	value of this variable will be used as the default.
+
+tag.gpgSign::
+	A boolean to specify whether all tags should be GPG signed.
+	Use of this option when running in an automated script can
+	result in a large number of tags being signed. It is therefore
+	convenient to use an agent to avoid typing your gpg passphrase
+	several times. Note that this option doesn't affect tag signing
+	behavior enabled by "-u <keyid>" or "--local-user=<keyid>" options.
+
+
+tar.umask::
+	This variable can be used to restrict the permission bits of
+	tar archive entries.  The default is 0002, which turns off the
+	world write bit.  The special value "user" indicates that the
+	archiving user's umask will be used instead.  See umask(2) and
+	linkgit:git-archive[1].
+
+
+Trace2 config settings are only read from the system and global
+config files; repository local and worktree config files and `-c`
+command line arguments are not respected.
+
+trace2.normalTarget::
+	This variable controls the normal target destination.
+	It may be overridden by the `GIT_TRACE2` environment variable.
+	The following table shows possible values.
+
+trace2.perfTarget::
+	This variable controls the performance target destination.
+	It may be overridden by the `GIT_TRACE2_PERF` environment variable.
+	The following table shows possible values.
+
+trace2.eventTarget::
+	This variable controls the event target destination.
+	It may be overridden by the `GIT_TRACE2_EVENT` environment variable.
+	The following table shows possible values.
++
+--
+* `0` or `false` - Disables the target.
+* `1` or `true` - Writes to `STDERR`.
+* `[2-9]` - Writes to the already opened file descriptor.
+* `<absolute-pathname>` - Writes to the file in append mode. If the target
+already exists and is a directory, the traces will be written to files (one
+per process) underneath the given directory.
+* `af_unix:[<socket-type>:]<absolute-pathname>` - Write to a
+Unix DomainSocket (on platforms that support them).  Socket
+type can be either `stream` or `dgram`; if omitted Git will
+try both.
+--
+
+
+trace2.normalBrief::
+	Boolean.  When true `time`, `filename`, and `line` fields are
+	omitted from normal output.  May be overridden by the
+	`GIT_TRACE2_BRIEF` environment variable.  Defaults to false.
+
+trace2.perfBrief::
+	Boolean.  When true `time`, `filename`, and `line` fields are
+	omitted from PERF output.  May be overridden by the
+	`GIT_TRACE2_PERF_BRIEF` environment variable.  Defaults to false.
+
+trace2.eventBrief::
+	Boolean.  When true `time`, `filename`, and `line` fields are
+	omitted from event output.  May be overridden by the
+	`GIT_TRACE2_EVENT_BRIEF` environment variable.  Defaults to false.
+
+trace2.eventNesting::
+	Integer.  Specifies desired depth of nested regions in the
+	event output.  Regions deeper than this value will be
+	omitted.  May be overridden by the `GIT_TRACE2_EVENT_NESTING`
+	environment variable.  Defaults to 2.
+
+trace2.configParams::
+	A comma-separated list of patterns of "important" config
+	settings that should be recorded in the trace2 output.
+	For example, `core.*,remote.*.url` would cause the trace2
+	output to contain events listing each configured remote.
+	May be overridden by the `GIT_TRACE2_CONFIG_PARAMS` environment
+	variable.  Unset by default.
+
+trace2.envVars::
+	A comma-separated list of "important" environment variables that should
+	be recorded in the trace2 output.  For example,
+	`GIT_HTTP_USER_AGENT,GIT_CONFIG` would cause the trace2 output to
+	contain events listing the overrides for HTTP user agent and the
+	location of the Git configuration file (assuming any are set).  May be
+	overridden by the `GIT_TRACE2_ENV_VARS` environment variable.  Unset by
+	default.
+
+trace2.destinationDebug::
+	Boolean.  When true Git will print error messages when a
+	trace target destination cannot be opened for writing.
+	By default, these errors are suppressed and tracing is
+	silently disabled.  May be overridden by the
+	`GIT_TRACE2_DST_DEBUG` environment variable.
+
+trace2.maxFiles::
+	Integer.  When writing trace files to a target directory, do not
+	write additional traces if doing so would exceed this many files. Instead,
+	write a sentinel file that will block further tracing to this
+	directory. Defaults to 0, which disables this check.
+
+
+transfer.credentialsInUrl::
+	A configured URL can contain plaintext credentials in the form
+	`<protocol>://<user>:<password>@<domain>/<path>`. You may want
+	to warn or forbid the use of such configuration (in favor of
+	using linkgit:git-credential[1]). This will be used on
+	linkgit:git-clone[1], linkgit:git-fetch[1], linkgit:git-push[1],
+	and any other direct use of the configured URL.
++
+Note that this is currently limited to detecting credentials in
+`remote.<name>.url` configuration; it won't detect credentials in
+`remote.<name>.pushurl` configuration.
++
+You might want to enable this to prevent inadvertent credentials
+exposure, e.g. because:
++
+* The OS or system where you're running git may not provide a way or
+  otherwise allow you to configure the permissions of the
+  configuration file where the username and/or password are stored.
+* Even if it does, having such data stored "at rest" might expose you
+  in other ways, e.g. a backup process might copy the data to another
+  system.
+* The git programs will pass the full URL to one another as arguments
+  on the command-line, meaning the credentials will be exposed to other
+  unprivileged users on systems that allow them to see the full
+  process list of other users. On linux the "hidepid" setting
+  documented in procfs(5) allows for configuring this behavior.
++
+If such concerns don't apply to you then you probably don't need to be
+concerned about credentials exposure due to storing sensitive
+data in git's configuration files. If you do want to use this, set
+`transfer.credentialsInUrl` to one of these values:
++
+* `allow` (default): Git will proceed with its activity without warning.
+* `warn`: Git will write a warning message to `stderr` when parsing a URL
+  with a plaintext credential.
+* `die`: Git will write a failure message to `stderr` when parsing a URL
+  with a plaintext credential.
+
+transfer.fsckObjects::
+	When `fetch.fsckObjects` or `receive.fsckObjects` are
+	not set, the value of this variable is used instead.
+	Defaults to false.
++
+When set, the fetch or receive will abort in the case of a malformed
+object or a link to a nonexistent object. In addition, various other
+issues are checked for, including legacy issues (see `fsck.<msg-id>`),
+and potential security issues like the existence of a `.GIT` directory
+or a malicious `.gitmodules` file (see the release notes for v2.2.1
+and v2.17.1 for details). Other sanity and security checks may be
+added in future releases.
++
+On the receiving side, failing fsckObjects will make those objects
+unreachable, see "QUARANTINE ENVIRONMENT" in
+linkgit:git-receive-pack[1]. On the fetch side, malformed objects will
+instead be left unreferenced in the repository.
++
+Due to the non-quarantine nature of the `fetch.fsckObjects`
+implementation it cannot be relied upon to leave the object store
+clean like `receive.fsckObjects` can.
++
+As objects are unpacked they're written to the object store, so there
+can be cases where malicious objects get introduced even though the
+"fetch" failed, only to have a subsequent "fetch" succeed because only
+new incoming objects are checked, not those that have already been
+written to the object store. That difference in behavior should not be
+relied upon. In the future, such objects may be quarantined for
+"fetch" as well.
++
+For now, the paranoid need to find some way to emulate the quarantine
+environment if they'd like the same protection as "push". E.g. in the
+case of an internal mirror do the mirroring in two steps, one to fetch
+the untrusted objects, and then do a second "push" (which will use the
+quarantine) to another internal repo, and have internal clients
+consume this pushed-to repository, or embargo internal fetches and
+only allow them once a full "fsck" has run (and no new fetches have
+happened in the meantime).
+
+transfer.hideRefs::
+	String(s) `receive-pack` and `upload-pack` use to decide which
+	refs to omit from their initial advertisements.  Use more than
+	one definition to specify multiple prefix strings. A ref that is
+	under the hierarchies listed in the value of this variable is
+	excluded, and is hidden when responding to `git push` or `git
+	fetch`.  See `receive.hideRefs` and `uploadpack.hideRefs` for
+	program-specific versions of this config.
++
+You may also include a `!` in front of the ref name to negate the entry,
+explicitly exposing it, even if an earlier entry marked it as hidden.
+If you have multiple hideRefs values, later entries override earlier ones
+(and entries in more-specific config files override less-specific ones).
++
+If a namespace is in use, the namespace prefix is stripped from each
+reference before it is matched against `transfer.hiderefs` patterns. In
+order to match refs before stripping, add a `^` in front of the ref name. If
+you combine `!` and `^`, `!` must be specified first.
++
+For example, if `refs/heads/master` is specified in `transfer.hideRefs` and
+the current namespace is `foo`, then `refs/namespaces/foo/refs/heads/master`
+is omitted from the advertisements. If `uploadpack.allowRefInWant` is set,
+`upload-pack` will treat `want-ref refs/heads/master` in a protocol v2
+`fetch` command as if `refs/namespaces/foo/refs/heads/master` did not exist.
+`receive-pack`, on the other hand, will still advertise the object id the
+ref is pointing to without mentioning its name (a so-called ".have" line).
++
+Even if you hide refs, a client may still be able to steal the target
+objects via the techniques described in the "SECURITY" section of the
+linkgit:gitnamespaces[7] man page; it's best to keep private data in a
+separate repository.
+
+transfer.unpackLimit::
+	When `fetch.unpackLimit` or `receive.unpackLimit` are
+	not set, the value of this variable is used instead.
+	The default value is 100.
+
+transfer.advertiseSID::
+	Boolean. When true, client and server processes will advertise their
+	unique session IDs to their remote counterpart. Defaults to false.
+
+transfer.bundleURI::
+	When `true`, local `git clone` commands will request bundle
+	information from the remote server (if advertised) and download
+	bundles before continuing the clone through the Git protocol.
+	Defaults to `false`.
+
+transfer.advertiseObjectInfo::
+	When `true`, the `object-info` capability is advertised by
+	servers. Defaults to false.
+
+
+uploadarchive.allowUnreachable::
+	If true, allow clients to use `git archive --remote` to request
+	any tree, whether reachable from the ref tips or not. See the
+	discussion in the "SECURITY" section of
+	linkgit:git-upload-archive[1] for more details. Defaults to
+	`false`.
+
+
+uploadpack.hideRefs::
+	This variable is the same as `transfer.hideRefs`, but applies
+	only to `upload-pack` (and so affects only fetches, not pushes).
+	An attempt to fetch a hidden ref by `git fetch` will fail.  See
+	also `uploadpack.allowTipSHA1InWant`.
+
+uploadpack.allowTipSHA1InWant::
+	When `uploadpack.hideRefs` is in effect, allow `upload-pack`
+	to accept a fetch request that asks for an object at the tip
+	of a hidden ref (by default, such a request is rejected).
+	See also `uploadpack.hideRefs`.  Even if this is false, a client
+	may be able to steal objects via the techniques described in the
+	"SECURITY" section of the linkgit:gitnamespaces[7] man page; it's
+	best to keep private data in a separate repository.
+
+uploadpack.allowReachableSHA1InWant::
+	Allow `upload-pack` to accept a fetch request that asks for an
+	object that is reachable from any ref tip. However, note that
+	calculating object reachability is computationally expensive.
+	Defaults to `false`.  Even if this is false, a client may be able
+	to steal objects via the techniques described in the "SECURITY"
+	section of the linkgit:gitnamespaces[7] man page; it's best to
+	keep private data in a separate repository.
+
+uploadpack.allowAnySHA1InWant::
+	Allow `upload-pack` to accept a fetch request that asks for any
+	object at all.
+	Defaults to `false`.
+
+uploadpack.keepAlive::
+	When `upload-pack` has started `pack-objects`, there may be a
+	quiet period while `pack-objects` prepares the pack. Normally
+	it would output progress information, but if `--quiet` was used
+	for the fetch, `pack-objects` will output nothing at all until
+	the pack data begins. Some clients and networks may consider
+	the server to be hung and give up. Setting this option instructs
+	`upload-pack` to send an empty keepalive packet every
+	`uploadpack.keepAlive` seconds. Setting this option to 0
+	disables keepalive packets entirely. The default is 5 seconds.
+
+uploadpack.packObjectsHook::
+	If this option is set, when `upload-pack` would run
+	`git pack-objects` to create a packfile for a client, it will
+	run this shell command instead.  The `pack-objects` command and
+	arguments it _would_ have run (including the `git pack-objects`
+	at the beginning) are appended to the shell command. The stdin
+	and stdout of the hook are treated as if `pack-objects` itself
+	was run. I.e., `upload-pack` will feed input intended for
+	`pack-objects` to the hook, and expects a completed packfile on
+	stdout.
++
+Note that this configuration variable is only respected when it is specified
+in protected configuration (see <<SCOPES>>). This is a safety measure
+against fetching from untrusted repositories.
+
+uploadpack.allowFilter::
+	If this option is set, `upload-pack` will support partial
+	clone and partial fetch object filtering.
+
+uploadpackfilter.allow::
+	Provides a default value for unspecified object filters (see: the
+	below configuration variable). If set to `true`, this will also
+	enable all filters which get added in the future.
+	Defaults to `true`.
+
+uploadpackfilter.<filter>.allow::
+	Explicitly allow or ban the object filter corresponding to
+	`<filter>`, where `<filter>` may be one of: `blob:none`,
+	`blob:limit`, `object:type`, `tree`, `sparse:oid`, or `combine`.
+	If using combined filters, both `combine` and all of the nested
+	filter kinds must be allowed. Defaults to `uploadpackfilter.allow`.
+
+uploadpackfilter.tree.maxDepth::
+	Only allow `--filter=tree:<n>` when `<n>` is no more than the value of
+	`uploadpackfilter.tree.maxDepth`. If set, this also implies
+	`uploadpackfilter.tree.allow=true`, unless this configuration
+	variable had already been set. Has no effect if unset.
+
+uploadpack.allowRefInWant::
+	If this option is set, `upload-pack` will support the `ref-in-want`
+	feature of the protocol version 2 `fetch` command.  This feature
+	is intended for the benefit of load-balanced servers which may
+	not have the same view of what OIDs their refs point to due to
+	replication delay.
+
+
+url.<base>.insteadOf::
+	Any URL that starts with this value will be rewritten to
+	start, instead, with <base>. In cases where some site serves a
+	large number of repositories, and serves them with multiple
+	access methods, and some users need to use different access
+	methods, this feature allows people to specify any of the
+	equivalent URLs and have Git automatically rewrite the URL to
+	the best alternative for the particular user, even for a
+	never-before-seen repository on the site.  When more than one
+	insteadOf strings match a given URL, the longest match is used.
++
+Note that any protocol restrictions will be applied to the rewritten
+URL. If the rewrite changes the URL to use a custom protocol or remote
+helper, you may need to adjust the `protocol.*.allow` config to permit
+the request.  In particular, protocols you expect to use for submodules
+must be set to `always` rather than the default of `user`. See the
+description of `protocol.allow` above.
+
+url.<base>.pushInsteadOf::
+	Any URL that starts with this value will not be pushed to;
+	instead, it will be rewritten to start with <base>, and the
+	resulting URL will be pushed to. In cases where some site serves
+	a large number of repositories, and serves them with multiple
+	access methods, some of which do not allow push, this feature
+	allows people to specify a pull-only URL and have Git
+	automatically use an appropriate URL to push, even for a
+	never-before-seen repository on the site.  When more than one
+	pushInsteadOf strings match a given URL, the longest match is
+	used.  If a remote has an explicit pushurl, Git will ignore this
+	setting for that remote.
+
+
+user.name::
+user.email::
+author.name::
+author.email::
+committer.name::
+committer.email::
+	The `user.name` and `user.email` variables determine what ends
+	up in the `author` and `committer` fields of commit
+	objects.
+	If you need the `author` or `committer` to be different, the
+	`author.name`, `author.email`, `committer.name`, or
+	`committer.email` variables can be set.
+	All of these can be overridden by the `GIT_AUTHOR_NAME`,
+	`GIT_AUTHOR_EMAIL`, `GIT_COMMITTER_NAME`,
+	`GIT_COMMITTER_EMAIL`, and `EMAIL` environment variables.
++
+Note that the `name` forms of these variables conventionally refer to
+some form of a personal name.  See linkgit:git-commit[1] and the
+environment variables section of linkgit:git[1] for more information on
+these settings and the `credential.username` option if you're looking
+for authentication credentials instead.
+
+user.useConfigOnly::
+	Instruct Git to avoid trying to guess defaults for `user.email`
+	and `user.name`, and instead retrieve the values only from the
+	configuration. For example, if you have multiple email addresses
+	and would like to use a different one for each repository, then
+	with this configuration option set to `true` in the global config
+	along with a name, Git will prompt you to set up an email before
+	making new commits in a newly cloned repository.
+	Defaults to `false`.
+
+user.signingKey::
+	If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the
+	key you want it to automatically when creating a signed tag or
+	commit, you can override the default selection with this variable.
+	This option is passed unchanged to gpg's --local-user parameter,
+	so you may specify a key using any method that gpg supports.
+	If gpg.format is set to `ssh` this can contain the path to either
+	your private ssh key or the public key when ssh-agent is used.
+	Alternatively it can contain a public key prefixed with `key::`
+	directly (e.g.: "key::ssh-rsa XXXXXX identifier"). The private key
+	needs to be available via ssh-agent. If not set Git will call
+	gpg.ssh.defaultKeyCommand (e.g.: "ssh-add -L") and try to use the
+	first key available. For backward compatibility, a raw key which
+	begins with "ssh-", such as "ssh-rsa XXXXXX identifier", is treated
+	as "key::ssh-rsa XXXXXX identifier", but this form is deprecated;
+	use the `key::` form instead.
+
+
+versionsort.prereleaseSuffix (deprecated)::
+	Deprecated alias for `versionsort.suffix`.  Ignored if
+	`versionsort.suffix` is set.
+
+versionsort.suffix::
+	Even when version sort is used in linkgit:git-tag[1], tagnames
+	with the same base version but different suffixes are still sorted
+	lexicographically, resulting e.g. in prerelease tags appearing
+	after the main release (e.g. "1.0-rc1" after "1.0").  This
+	variable can be specified to determine the sorting order of tags
+	with different suffixes.
++
+By specifying a single suffix in this variable, any tagname containing
+that suffix will appear before the corresponding main release.  E.g. if
+the variable is set to "-rc", then all "1.0-rcX" tags will appear before
+"1.0".  If specified multiple times, once per suffix, then the order of
+suffixes in the configuration will determine the sorting order of tagnames
+with those suffixes.  E.g. if "-pre" appears before "-rc" in the
+configuration, then all "1.0-preX" tags will be listed before any
+"1.0-rcX" tags.  The placement of the main release tag relative to tags
+with various suffixes can be determined by specifying the empty suffix
+among those other suffixes.  E.g. if the suffixes "-rc", "", "-ck", and
+"-bfs" appear in the configuration in this order, then all "v4.8-rcX" tags
+are listed first, followed by "v4.8", then "v4.8-ckX" and finally
+"v4.8-bfsX".
++
+If more than one suffix matches the same tagname, then that tagname will
+be sorted according to the suffix which starts at the earliest position in
+the tagname.  If more than one different matching suffix starts at
+that earliest position, then that tagname will be sorted according to the
+longest of those suffixes.
+The sorting order between different suffixes is undefined if they are
+in multiple config files.
+
+
+web.browser::
+	Specify a web browser that may be used by some commands.
+	Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]
+	may use it.
+
+
+worktree.guessRemote::
+	If no branch is specified and neither `-b` nor `-B` nor
+	`--detach` is used, then `git worktree add` defaults to
+	creating a new branch from HEAD.  If `worktree.guessRemote` is
+	set to true, `worktree add` tries to find a remote-tracking
+	branch whose name uniquely matches the new branch name.  If
+	such a branch exists, it is checked out and set as "upstream"
+	for the new branch.  If no such match can be found, it falls
+	back to creating a new branch from the current HEAD.
+
+
+
+BUGS
+----
+When using the deprecated `[section.subsection]` syntax, changing a value
+will result in adding a multi-line key instead of a change, if the subsection
+is given with at least one uppercase character. For example when the config
+looks like
+
+--------
+  [section.subsection]
+    key = value1
+--------
+
+and running `git config section.Subsection.key value2` will result in
+
+--------
+  [section.subsection]
+    key = value1
+    key = value2
+--------
+
+
+GIT
+---
+Part of the linkgit:git[1] suite
diff --git a/external/docs/asciidoc/d470969260e7a605742fb34733463f6434be4872 b/external/docs/asciidoc/d470969260e7a605742fb34733463f6434be4872
new file mode 100644
index 0000000000..333e27aa43
--- /dev/null
+++ b/external/docs/asciidoc/d470969260e7a605742fb34733463f6434be4872
@@ -0,0 +1,1318 @@
+git-pull(1)
+===========
+
+NAME
+----
+git-pull - Fetch from and integrate with another repository or a local branch
+
+
+SYNOPSIS
+--------
+[verse]
+'git pull' [<options>] [<repository> [<refspec>...]]
+
+
+DESCRIPTION
+-----------
+
+Incorporates changes from a remote repository into the current branch.
+If the current branch is behind the remote, then by default it will
+fast-forward the current branch to match the remote.  If the current
+branch and the remote have diverged, the user needs to specify how to
+reconcile the divergent branches with `--rebase` or `--no-rebase` (or
+the corresponding configuration option in `pull.rebase`).
+
+More precisely, `git pull` runs `git fetch` with the given parameters
+and then depending on configuration options or command line flags,
+will call either `git rebase` or `git merge` to reconcile diverging
+branches.
+
+<repository> should be the name of a remote repository as
+passed to linkgit:git-fetch[1].  <refspec> can name an
+arbitrary remote ref (for example, the name of a tag) or even
+a collection of refs with corresponding remote-tracking branches
+(e.g., refs/heads/{asterisk}:refs/remotes/origin/{asterisk}),
+but usually it is the name of a branch in the remote repository.
+
+Default values for <repository> and <branch> are read from the
+"remote" and "merge" configuration for the current branch
+as set by linkgit:git-branch[1] `--track`.
+
+Assume the following history exists and the current branch is
+"`master`":
+
+------------
+	  A---B---C master on origin
+	 /
+    D---E---F---G master
+	^
+	origin/master in your repository
+------------
+
+Then "`git pull`" will fetch and replay the changes from the remote
+`master` branch since it diverged from the local `master` (i.e., `E`)
+until its current commit (`C`) on top of `master` and record the
+result in a new commit along with the names of the two parent commits
+and a log message from the user describing the changes.
+
+------------
+	  A---B---C origin/master
+	 /         \
+    D---E---F---G---H master
+------------
+
+See linkgit:git-merge[1] for details, including how conflicts
+are presented and handled.
+
+In Git 1.7.0 or later, to cancel a conflicting merge, use
+`git reset --merge`.  *Warning*: In older versions of Git, running 'git pull'
+with uncommitted changes is discouraged: while possible, it leaves you
+in a state that may be hard to back out of in the case of a conflict.
+
+If any of the remote changes overlap with local uncommitted changes,
+the merge will be automatically canceled and the work tree untouched.
+It is generally best to get any local changes in working order before
+pulling or stash them away with linkgit:git-stash[1].
+
+OPTIONS
+-------
+
+-q::
+--quiet::
+	This is passed to both underlying git-fetch to squelch reporting of
+	during transfer, and underlying git-merge to squelch output during
+	merging.
+
+-v::
+--verbose::
+	Pass --verbose to git-fetch and git-merge.
+
+--[no-]recurse-submodules[=(yes|on-demand|no)]::
+	This option controls if new commits of populated submodules should
+	be fetched, and if the working trees of active submodules should be
+	updated, too (see linkgit:git-fetch[1], linkgit:git-config[1] and
+	linkgit:gitmodules[5]).
++
+If the checkout is done via rebase, local submodule commits are rebased as well.
++
+If the update is done via merge, the submodule conflicts are resolved and checked out.
+
+Options related to merging
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+:git-pull: 1
+
+--commit::
+--no-commit::
+	Perform the merge and commit the result. This option can
+	be used to override --no-commit.
+ifdef::git-pull[]
+	Only useful when merging.
+endif::git-pull[]
++
+With --no-commit perform the merge and stop just before creating
+a merge commit, to give the user a chance to inspect and further
+tweak the merge result before committing.
++
+Note that fast-forward updates do not create a merge commit and
+therefore there is no way to stop those merges with --no-commit.
+Thus, if you want to ensure your branch is not changed or updated
+by the merge command, use --no-ff with --no-commit.
+
+--edit::
+-e::
+--no-edit::
+	Invoke an editor before committing successful mechanical merge to
+	further edit the auto-generated merge message, so that the user
+	can explain and justify the merge. The `--no-edit` option can be
+	used to accept the auto-generated message (this is generally
+	discouraged).
+ifndef::git-pull[]
+The `--edit` (or `-e`) option is still useful if you are
+giving a draft message with the `-m` option from the command line
+and want to edit it in the editor.
+endif::git-pull[]
++
+Older scripts may depend on the historical behaviour of not allowing the
+user to edit the merge log message. They will see an editor opened when
+they run `git merge`. To make it easier to adjust such scripts to the
+updated behaviour, the environment variable `GIT_MERGE_AUTOEDIT` can be
+set to `no` at the beginning of them.
+
+--cleanup=<mode>::
+	This option determines how the merge message will be cleaned up before
+	committing. See linkgit:git-commit[1] for more details. In addition, if
+	the '<mode>' is given a value of `scissors`, scissors will be appended
+	to `MERGE_MSG` before being passed on to the commit machinery in the
+	case of a merge conflict.
+
+ifdef::git-merge[]
+--ff::
+--no-ff::
+--ff-only::
+	Specifies how a merge is handled when the merged-in history is
+	already a descendant of the current history.  `--ff` is the
+	default unless merging an annotated (and possibly signed) tag
+	that is not stored in its natural place in the `refs/tags/`
+	hierarchy, in which case `--no-ff` is assumed.
+endif::git-merge[]
+ifdef::git-pull[]
+--ff-only::
+	Only update to the new history if there is no divergent local
+	history.  This is the default when no method for reconciling
+	divergent histories is provided (via the --rebase=* flags).
+
+--ff::
+--no-ff::
+	When merging rather than rebasing, specifies how a merge is
+	handled when the merged-in history is already a descendant of
+	the current history.  If merging is requested, `--ff` is the
+	default unless merging an annotated (and possibly signed) tag
+	that is not stored in its natural place in the `refs/tags/`
+	hierarchy, in which case `--no-ff` is assumed.
+endif::git-pull[]
++
+With `--ff`, when possible resolve the merge as a fast-forward (only
+update the branch pointer to match the merged branch; do not create a
+merge commit).  When not possible (when the merged-in history is not a
+descendant of the current history), create a merge commit.
++
+With `--no-ff`, create a merge commit in all cases, even when the merge
+could instead be resolved as a fast-forward.
+ifdef::git-merge[]
++
+With `--ff-only`, resolve the merge as a fast-forward when possible.
+When not possible, refuse to merge and exit with a non-zero status.
+endif::git-merge[]
+
+-S[<keyid>]::
+--gpg-sign[=<keyid>]::
+--no-gpg-sign::
+	GPG-sign the resulting merge commit. The `keyid` argument is
+	optional and defaults to the committer identity; if specified,
+	it must be stuck to the option without a space. `--no-gpg-sign`
+	is useful to countermand both `commit.gpgSign` configuration variable,
+	and earlier `--gpg-sign`.
+
+--log[=<n>]::
+--no-log::
+	In addition to branch names, populate the log message with
+	one-line descriptions from at most <n> actual commits that are being
+	merged. See also linkgit:git-fmt-merge-msg[1].
+ifdef::git-pull[]
+	Only useful when merging.
+endif::git-pull[]
++
+With --no-log do not list one-line descriptions from the
+actual commits being merged.
+
+ifdef::git-commit[]
+-s::
+endif::git-commit[]
+--signoff::
+--no-signoff::
+	Add a `Signed-off-by` trailer by the committer at the end of the commit
+	log message.  The meaning of a signoff depends on the project
+	to which you're committing.  For example, it may certify that
+	the committer has the rights to submit the work under the
+	project's license or agrees to some contributor representation,
+	such as a Developer Certificate of Origin.
+	(See https://developercertificate.org for the one used by the
+	Linux kernel and Git projects.)  Consult the documentation or
+	leadership of the project to which you're contributing to
+	understand how the signoffs are used in that project.
++
+The --no-signoff option can be used to countermand an earlier --signoff
+option on the command line.
+
+
+--stat::
+-n::
+--no-stat::
+	Show a diffstat at the end of the merge. The diffstat is also
+	controlled by the configuration option merge.stat.
++
+With -n or --no-stat do not show a diffstat at the end of the
+merge.
+
+--squash::
+--no-squash::
+	Produce the working tree and index state as if a real merge
+	happened (except for the merge information), but do not actually
+	make a commit, move the `HEAD`, or record `$GIT_DIR/MERGE_HEAD`
+	(to cause the next `git commit` command to create a merge
+	commit).  This allows you to create a single commit on top of
+	the current branch whose effect is the same as merging another
+	branch (or more in case of an octopus).
++
+With --no-squash perform the merge and commit the result. This
+option can be used to override --squash.
++
+With --squash, --commit is not allowed, and will fail.
+ifdef::git-pull[]
++
+Only useful when merging.
+endif::git-pull[]
+
+--[no-]verify::
+	By default, the pre-merge and commit-msg hooks are run.
+	When `--no-verify` is given, these are bypassed.
+	See also linkgit:githooks[5].
+ifdef::git-pull[]
+	Only useful when merging.
+endif::git-pull[]
+
+-s <strategy>::
+--strategy=<strategy>::
+	Use the given merge strategy; can be supplied more than
+	once to specify them in the order they should be tried.
+	If there is no `-s` option, a built-in list of strategies
+	is used instead (`ort` when merging a single head,
+	`octopus` otherwise).
+
+-X <option>::
+--strategy-option=<option>::
+	Pass merge strategy specific option through to the merge
+	strategy.
+
+--verify-signatures::
+--no-verify-signatures::
+	Verify that the tip commit of the side branch being merged is
+	signed with a valid key, i.e. a key that has a valid uid: in the
+	default trust model, this means the signing key has been signed by
+	a trusted key.  If the tip commit of the side branch is not signed
+	with a valid key, the merge is aborted.
+ifdef::git-pull[]
++
+Only useful when merging.
+endif::git-pull[]
+
+--summary::
+--no-summary::
+	Synonyms to --stat and --no-stat; these are deprecated and will be
+	removed in the future.
+
+ifndef::git-pull[]
+-q::
+--quiet::
+	Operate quietly. Implies --no-progress.
+
+-v::
+--verbose::
+	Be verbose.
+
+--progress::
+--no-progress::
+	Turn progress on/off explicitly. If neither is specified,
+	progress is shown if standard error is connected to a terminal.
+	Note that not all merge strategies may support progress
+	reporting.
+
+endif::git-pull[]
+
+--autostash::
+--no-autostash::
+	Automatically create a temporary stash entry before the operation
+	begins, record it in the ref `MERGE_AUTOSTASH`
+	and apply it after the operation ends.  This means
+	that you can run the operation on a dirty worktree.  However, use
+	with care: the final stash application after a successful
+	merge might result in non-trivial conflicts.
+
+--allow-unrelated-histories::
+	By default, `git merge` command refuses to merge histories
+	that do not share a common ancestor.  This option can be
+	used to override this safety when merging histories of two
+	projects that started their lives independently. As that is
+	a very rare occasion, no configuration variable to enable
+	this by default exists and will not be added.
+ifdef::git-pull[]
++
+Only useful when merging.
+endif::git-pull[]
+
+
+-r::
+--rebase[=(false|true|merges|interactive)]::
+	When true, rebase the current branch on top of the upstream
+	branch after fetching. If there is a remote-tracking branch
+	corresponding to the upstream branch and the upstream branch
+	was rebased since last fetched, the rebase uses that information
+	to avoid rebasing non-local changes.
++
+When set to `merges`, rebase using `git rebase --rebase-merges` so that
+the local merge commits are included in the rebase (see
+linkgit:git-rebase[1] for details).
++
+When false, merge the upstream branch into the current branch.
++
+When `interactive`, enable the interactive mode of rebase.
++
+See `pull.rebase`, `branch.<name>.rebase` and `branch.autoSetupRebase` in
+linkgit:git-config[1] if you want to make `git pull` always use
+`--rebase` instead of merging.
++
+[NOTE]
+This is a potentially _dangerous_ mode of operation.
+It rewrites history, which does not bode well when you
+published that history already.  Do *not* use this option
+unless you have read linkgit:git-rebase[1] carefully.
+
+--no-rebase::
+	This is shorthand for --rebase=false.
+
+Options related to fetching
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+--[no-]all::
+	Fetch all remotes, except for the ones that has the
+	`remote.<name>.skipFetchAll` configuration variable set.
+	This overrides the configuration variable fetch.all`.
+
+-a::
+--append::
+	Append ref names and object names of fetched refs to the
+	existing contents of `.git/FETCH_HEAD`.  Without this
+	option old data in `.git/FETCH_HEAD` will be overwritten.
+
+--atomic::
+	Use an atomic transaction to update local refs. Either all refs are
+	updated, or on error, no refs are updated.
+
+--depth=<depth>::
+	Limit fetching to the specified number of commits from the tip of
+	each remote branch history. If fetching to a 'shallow' repository
+	created by `git clone` with `--depth=<depth>` option (see
+	linkgit:git-clone[1]), deepen or shorten the history to the specified
+	number of commits. Tags for the deepened commits are not fetched.
+
+--deepen=<depth>::
+	Similar to --depth, except it specifies the number of commits
+	from the current shallow boundary instead of from the tip of
+	each remote branch history.
+
+--shallow-since=<date>::
+	Deepen or shorten the history of a shallow repository to
+	include all reachable commits after <date>.
+
+--shallow-exclude=<revision>::
+	Deepen or shorten the history of a shallow repository to
+	exclude commits reachable from a specified remote branch or tag.
+	This option can be specified multiple times.
+
+--unshallow::
+	If the source repository is complete, convert a shallow
+	repository to a complete one, removing all the limitations
+	imposed by shallow repositories.
++
+If the source repository is shallow, fetch as much as possible so that
+the current repository has the same history as the source repository.
+
+--update-shallow::
+	By default when fetching from a shallow repository,
+	`git fetch` refuses refs that require updating
+	.git/shallow. This option updates .git/shallow and accepts such
+	refs.
+
+--negotiation-tip=<commit|glob>::
+	By default, Git will report, to the server, commits reachable
+	from all local refs to find common commits in an attempt to
+	reduce the size of the to-be-received packfile. If specified,
+	Git will only report commits reachable from the given tips.
+	This is useful to speed up fetches when the user knows which
+	local ref is likely to have commits in common with the
+	upstream ref being fetched.
++
+This option may be specified more than once; if so, Git will report
+commits reachable from any of the given commits.
++
+The argument to this option may be a glob on ref names, a ref, or the (possibly
+abbreviated) SHA-1 of a commit. Specifying a glob is equivalent to specifying
+this option multiple times, one for each matching ref name.
++
+See also the `fetch.negotiationAlgorithm` and `push.negotiate`
+configuration variables documented in linkgit:git-config[1], and the
+`--negotiate-only` option below.
+
+--negotiate-only::
+	Do not fetch anything from the server, and instead print the
+	ancestors of the provided `--negotiation-tip=*` arguments,
+	which we have in common with the server.
++
+This is incompatible with `--recurse-submodules=[yes|on-demand]`.
+Internally this is used to implement the `push.negotiate` option, see
+linkgit:git-config[1].
+
+--dry-run::
+	Show what would be done, without making any changes.
+
+--porcelain::
+	Print the output to standard output in an easy-to-parse format for
+	scripts. See section OUTPUT in linkgit:git-fetch[1] for details.
++
+This is incompatible with `--recurse-submodules=[yes|on-demand]` and takes
+precedence over the `fetch.output` config option.
+
+ifndef::git-pull[]
+--[no-]write-fetch-head::
+	Write the list of remote refs fetched in the `FETCH_HEAD`
+	file directly under `$GIT_DIR`.  This is the default.
+	Passing `--no-write-fetch-head` from the command line tells
+	Git not to write the file.  Under `--dry-run` option, the
+	file is never written.
+endif::git-pull[]
+
+-f::
+--force::
+	When 'git fetch' is used with `<src>:<dst>` refspec, it may
+	refuse to update the local branch as discussed
+ifdef::git-pull[]
+	in the `<refspec>` part of the linkgit:git-fetch[1]
+	documentation.
+endif::git-pull[]
+ifndef::git-pull[]
+	in the `<refspec>` part below.
+endif::git-pull[]
+	This option overrides that check.
+
+-k::
+--keep::
+	Keep downloaded pack.
+
+ifndef::git-pull[]
+--multiple::
+	Allow several <repository> and <group> arguments to be
+	specified. No <refspec>s may be specified.
+
+--[no-]auto-maintenance::
+--[no-]auto-gc::
+	Run `git maintenance run --auto` at the end to perform automatic
+	repository maintenance if needed. (`--[no-]auto-gc` is a synonym.)
+	This is enabled by default.
+
+--[no-]write-commit-graph::
+	Write a commit-graph after fetching. This overrides the config
+	setting `fetch.writeCommitGraph`.
+endif::git-pull[]
+
+--prefetch::
+	Modify the configured refspec to place all refs into the
+	`refs/prefetch/` namespace. See the `prefetch` task in
+	linkgit:git-maintenance[1].
+
+-p::
+--prune::
+	Before fetching, remove any remote-tracking references that no
+	longer exist on the remote.  Tags are not subject to pruning
+	if they are fetched only because of the default tag
+	auto-following or due to a --tags option.  However, if tags
+	are fetched due to an explicit refspec (either on the command
+	line or in the remote configuration, for example if the remote
+	was cloned with the --mirror option), then they are also
+	subject to pruning. Supplying `--prune-tags` is a shorthand for
+	providing the tag refspec.
+ifndef::git-pull[]
++
+See the PRUNING section below for more details.
+
+-P::
+--prune-tags::
+	Before fetching, remove any local tags that no longer exist on
+	the remote if `--prune` is enabled. This option should be used
+	more carefully, unlike `--prune` it will remove any local
+	references (local tags) that have been created. This option is
+	a shorthand for providing the explicit tag refspec along with
+	`--prune`, see the discussion about that in its documentation.
++
+See the PRUNING section below for more details.
+
+endif::git-pull[]
+
+ifndef::git-pull[]
+-n::
+endif::git-pull[]
+--no-tags::
+	By default, tags that point at objects that are downloaded
+	from the remote repository are fetched and stored locally.
+	This option disables this automatic tag following. The default
+	behavior for a remote may be specified with the remote.<name>.tagOpt
+	setting. See linkgit:git-config[1].
+
+ifndef::git-pull[]
+--refetch::
+	Instead of negotiating with the server to avoid transferring commits and
+	associated objects that are already present locally, this option fetches
+	all objects as a fresh clone would. Use this to reapply a partial clone
+	filter from configuration or using `--filter=` when the filter
+	definition has changed. Automatic post-fetch maintenance will perform
+	object database pack consolidation to remove any duplicate objects.
+endif::git-pull[]
+
+--refmap=<refspec>::
+	When fetching refs listed on the command line, use the
+	specified refspec (can be given more than once) to map the
+	refs to remote-tracking branches, instead of the values of
+	`remote.*.fetch` configuration variables for the remote
+	repository.  Providing an empty `<refspec>` to the
+	`--refmap` option causes Git to ignore the configured
+	refspecs and rely entirely on the refspecs supplied as
+	command-line arguments. See section on "Configured Remote-tracking
+	Branches" for details.
+
+-t::
+--tags::
+	Fetch all tags from the remote (i.e., fetch remote tags
+	`refs/tags/*` into local tags with the same name), in addition
+	to whatever else would otherwise be fetched.  Using this
+	option alone does not subject tags to pruning, even if --prune
+	is used (though tags may be pruned anyway if they are also the
+	destination of an explicit refspec; see `--prune`).
+
+ifndef::git-pull[]
+--recurse-submodules[=(yes|on-demand|no)]::
+	This option controls if and under what conditions new commits of
+	submodules should be fetched too. When recursing through submodules,
+	`git fetch` always attempts to fetch "changed" submodules, that is, a
+	submodule that has commits that are referenced by a newly fetched
+	superproject commit but are missing in the local submodule clone. A
+	changed submodule can be fetched as long as it is present locally e.g.
+	in `$GIT_DIR/modules/` (see linkgit:gitsubmodules[7]); if the upstream
+	adds a new submodule, that submodule cannot be fetched until it is
+	cloned e.g. by `git submodule update`.
++
+When set to 'on-demand', only changed submodules are fetched. When set
+to 'yes', all populated submodules are fetched and submodules that are
+both unpopulated and changed are fetched. When set to 'no', submodules
+are never fetched.
++
+When unspecified, this uses the value of `fetch.recurseSubmodules` if it
+is set (see linkgit:git-config[1]), defaulting to 'on-demand' if unset.
+When this option is used without any value, it defaults to 'yes'.
+endif::git-pull[]
+
+-j::
+--jobs=<n>::
+	Number of parallel children to be used for all forms of fetching.
++
+If the `--multiple` option was specified, the different remotes will be fetched
+in parallel. If multiple submodules are fetched, they will be fetched in
+parallel. To control them independently, use the config settings
+`fetch.parallel` and `submodule.fetchJobs` (see linkgit:git-config[1]).
++
+Typically, parallel recursive and multi-remote fetches will be faster. By
+default fetches are performed sequentially, not in parallel.
+
+ifndef::git-pull[]
+--no-recurse-submodules::
+	Disable recursive fetching of submodules (this has the same effect as
+	using the `--recurse-submodules=no` option).
+endif::git-pull[]
+
+--set-upstream::
+	If the remote is fetched successfully, add upstream
+	(tracking) reference, used by argument-less
+	linkgit:git-pull[1] and other commands. For more information,
+	see `branch.<name>.merge` and `branch.<name>.remote` in
+	linkgit:git-config[1].
+
+ifndef::git-pull[]
+--submodule-prefix=<path>::
+	Prepend <path> to paths printed in informative messages
+	such as "Fetching submodule foo".  This option is used
+	internally when recursing over submodules.
+
+--recurse-submodules-default=[yes|on-demand]::
+	This option is used internally to temporarily provide a
+	non-negative default value for the --recurse-submodules
+	option.  All other methods of configuring fetch's submodule
+	recursion (such as settings in linkgit:gitmodules[5] and
+	linkgit:git-config[1]) override this option, as does
+	specifying --[no-]recurse-submodules directly.
+
+-u::
+--update-head-ok::
+	By default 'git fetch' refuses to update the head which
+	corresponds to the current branch.  This flag disables the
+	check.  This is purely for the internal use for 'git pull'
+	to communicate with 'git fetch', and unless you are
+	implementing your own Porcelain you are not supposed to
+	use it.
+endif::git-pull[]
+
+--upload-pack <upload-pack>::
+	When given, and the repository to fetch from is handled
+	by 'git fetch-pack', `--exec=<upload-pack>` is passed to
+	the command to specify non-default path for the command
+	run on the other end.
+
+ifndef::git-pull[]
+-q::
+--quiet::
+	Pass --quiet to git-fetch-pack and silence any other internally
+	used git commands. Progress is not reported to the standard error
+	stream.
+
+-v::
+--verbose::
+	Be verbose.
+endif::git-pull[]
+
+--progress::
+	Progress status is reported on the standard error stream
+	by default when it is attached to a terminal, unless -q
+	is specified. This flag forces progress status even if the
+	standard error stream is not directed to a terminal.
+
+-o <option>::
+--server-option=<option>::
+	Transmit the given string to the server when communicating using
+	protocol version 2.  The given string must not contain a NUL or LF
+	character.  The server's handling of server options, including
+	unknown ones, is server-specific.
+	When multiple `--server-option=<option>` are given, they are all
+	sent to the other side in the order listed on the command line.
+
+--show-forced-updates::
+	By default, git checks if a branch is force-updated during
+	fetch. This can be disabled through fetch.showForcedUpdates, but
+	the --show-forced-updates option guarantees this check occurs.
+	See linkgit:git-config[1].
+
+--no-show-forced-updates::
+	By default, git checks if a branch is force-updated during
+	fetch. Pass --no-show-forced-updates or set fetch.showForcedUpdates
+	to false to skip this check for performance reasons. If used during
+	'git-pull' the --ff-only option will still check for forced updates
+	before attempting a fast-forward update. See linkgit:git-config[1].
+
+-4::
+--ipv4::
+	Use IPv4 addresses only, ignoring IPv6 addresses.
+
+-6::
+--ipv6::
+	Use IPv6 addresses only, ignoring IPv4 addresses.
+
+
+<repository>::
+	The "remote" repository that is the source of a fetch
+	or pull operation.  This parameter can be either a URL
+	(see the section <<URLS,GIT URLS>> below) or the name
+	of a remote (see the section <<REMOTES,REMOTES>> below).
+
+ifndef::git-pull[]
+<group>::
+	A name referring to a list of repositories as the value
+	of remotes.<group> in the configuration file.
+	(See linkgit:git-config[1]).
+endif::git-pull[]
+
+<refspec>::
+	Specifies which refs to fetch and which local refs to update.
+	When no <refspec>s appear on the command line, the refs to fetch
+	are read from `remote.<repository>.fetch` variables instead
+ifndef::git-pull[]
+	(see <<CRTB,CONFIGURED REMOTE-TRACKING BRANCHES>> below).
+endif::git-pull[]
+ifdef::git-pull[]
+	(see the section "CONFIGURED REMOTE-TRACKING BRANCHES"
+	in linkgit:git-fetch[1]).
+endif::git-pull[]
++
+The format of a <refspec> parameter is an optional plus
+`+`, followed by the source <src>, followed
+by a colon `:`, followed by the destination ref <dst>.
+The colon can be omitted when <dst> is empty.  <src> is
+typically a ref, but it can also be a fully spelled hex object
+name.
++
+A <refspec> may contain a `*` in its <src> to indicate a simple pattern
+match. Such a refspec functions like a glob that matches any ref with the
+same prefix. A pattern <refspec> must have a `*` in both the <src> and
+<dst>. It will map refs to the destination by replacing the `*` with the
+contents matched from the source.
++
+If a refspec is prefixed by `^`, it will be interpreted as a negative
+refspec. Rather than specifying which refs to fetch or which local refs to
+update, such a refspec will instead specify refs to exclude. A ref will be
+considered to match if it matches at least one positive refspec, and does
+not match any negative refspec. Negative refspecs can be useful to restrict
+the scope of a pattern refspec so that it will not include specific refs.
+Negative refspecs can themselves be pattern refspecs. However, they may only
+contain a <src> and do not specify a <dst>. Fully spelled out hex object
+names are also not supported.
++
+`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`;
+it requests fetching everything up to the given tag.
++
+The remote ref that matches <src>
+is fetched, and if <dst> is not an empty string, an attempt
+is made to update the local ref that matches it.
++
+Whether that update is allowed without `--force` depends on the ref
+namespace it's being fetched to, the type of object being fetched, and
+whether the update is considered to be a fast-forward. Generally, the
+same rules apply for fetching as when pushing, see the `<refspec>...`
+section of linkgit:git-push[1] for what those are. Exceptions to those
+rules particular to 'git fetch' are noted below.
++
+Until Git version 2.20, and unlike when pushing with
+linkgit:git-push[1], any updates to `refs/tags/*` would be accepted
+without `+` in the refspec (or `--force`). When fetching, we promiscuously
+considered all tag updates from a remote to be forced fetches.  Since
+Git version 2.20, fetching to update `refs/tags/*` works the same way
+as when pushing. I.e. any updates will be rejected without `+` in the
+refspec (or `--force`).
++
+Unlike when pushing with linkgit:git-push[1], any updates outside of
+`refs/{tags,heads}/*` will be accepted without `+` in the refspec (or
+`--force`), whether that's swapping e.g. a tree object for a blob, or
+a commit for another commit that doesn't have the previous commit as
+an ancestor etc.
++
+Unlike when pushing with linkgit:git-push[1], there is no
+configuration which'll amend these rules, and nothing like a
+`pre-fetch` hook analogous to the `pre-receive` hook.
++
+As with pushing with linkgit:git-push[1], all of the rules described
+above about what's not allowed as an update can be overridden by
+adding an optional leading `+` to a refspec (or using the `--force`
+command line option). The only exception to this is that no amount of
+forcing will make the `refs/heads/*` namespace accept a non-commit
+object.
++
+[NOTE]
+When the remote branch you want to fetch is known to
+be rewound and rebased regularly, it is expected that
+its new tip will not be a descendant of its previous tip
+(as stored in your remote-tracking branch the last time
+you fetched).  You would want
+to use the `+` sign to indicate non-fast-forward updates
+will be needed for such branches.  There is no way to
+determine or declare that a branch will be made available
+in a repository with this behavior; the pulling user simply
+must know this is the expected usage pattern for a branch.
+ifdef::git-pull[]
++
+[NOTE]
+There is a difference between listing multiple <refspec>
+directly on 'git pull' command line and having multiple
+`remote.<repository>.fetch` entries in your configuration
+for a <repository> and running a
+'git pull' command without any explicit <refspec> parameters.
+<refspec>s listed explicitly on the command line are always
+merged into the current branch after fetching.  In other words,
+if you list more than one remote ref, 'git pull' will create
+an Octopus merge.  On the other hand, if you do not list any
+explicit <refspec> parameter on the command line, 'git pull'
+will fetch all the <refspec>s it finds in the
+`remote.<repository>.fetch` configuration and merge
+only the first <refspec> found into the current branch.
+This is because making an
+Octopus from remote refs is rarely done, while keeping track
+of multiple remote heads in one-go by fetching more than one
+is often useful.
+endif::git-pull[]
+
+
+GIT URLS[[URLS]]
+----------------
+
+In general, URLs contain information about the transport protocol, the
+address of the remote server, and the path to the repository.
+Depending on the transport protocol, some of this information may be
+absent.
+
+Git supports ssh, git, http, and https protocols (in addition, ftp
+and ftps can be used for fetching, but this is inefficient and
+deprecated; do not use them).
+
+The native transport (i.e. git:// URL) does no authentication and
+should be used with caution on unsecured networks.
+
+The following syntaxes may be used with them:
+
+- ++ssh://++{startsb}__<user>__++@++{endsb}__<host>__{startsb}++:++__<port>__{endsb}++/++__<path-to-git-repo>__
+- ++git://++__<host>__{startsb}:__<port>__{endsb}++/++__<path-to-git-repo>__
+- ++http++{startsb}++s++{endsb}++://++__<host>__{startsb}++:++__<port>__{endsb}++/++__<path-to-git-repo>__
+- ++ftp++{startsb}++s++{endsb}++://++__<host>__{startsb}++:++__<port>__{endsb}++/++__<path-to-git-repo>__
+
+An alternative scp-like syntax may also be used with the ssh protocol:
+
+- {startsb}__<user>__++@++{endsb}__<host>__++:/++__<path-to-git-repo>__
+
+This syntax is only recognized if there are no slashes before the
+first colon. This helps differentiate a local path that contains a
+colon. For example the local path `foo:bar` could be specified as an
+absolute path or `./foo:bar` to avoid being misinterpreted as an ssh
+url.
+
+The ssh and git protocols additionally support ++~++__<username>__ expansion:
+
+- ++ssh://++{startsb}__<user>__++@++{endsb}__<host>__{startsb}++:++__<port>__{endsb}++/~++__<user>__++/++__<path-to-git-repo>__
+- ++git://++__<host>__{startsb}++:++__<port>__{endsb}++/~++__<user>__++/++__<path-to-git-repo>__
+- {startsb}__<user>__++@++{endsb}__<host>__++:~++__<user>__++/++__<path-to-git-repo>__
+
+For local repositories, also supported by Git natively, the following
+syntaxes may be used:
+
+- `/path/to/repo.git/`
+- ++file:///path/to/repo.git/++
+
+ifndef::git-clone[]
+These two syntaxes are mostly equivalent, except when cloning, when
+the former implies `--local` option. See linkgit:git-clone[1] for
+details.
+endif::git-clone[]
+
+ifdef::git-clone[]
+These two syntaxes are mostly equivalent, except the former implies
+`--local` option.
+endif::git-clone[]
+
+`git clone`, `git fetch` and `git pull`, but not `git push`, will also
+accept a suitable bundle file. See linkgit:git-bundle[1].
+
+When Git doesn't know how to handle a certain transport protocol, it
+attempts to use the `remote-`{empty}__<transport>__ remote helper, if one
+exists. To explicitly request a remote helper, the following syntax
+may be used:
+
+- _<transport>_::__<address>__
+
+where _<address>_ may be a path, a server and path, or an arbitrary
+URL-like string recognized by the specific remote helper being
+invoked. See linkgit:gitremote-helpers[7] for details.
+
+If there are a large number of similarly-named remote repositories and
+you want to use a different format for them (such that the URLs you
+use will be rewritten into URLs that work), you can create a
+configuration section of the form:
+
+[verse]
+--
+	[url "__<actual-url-base>__"]
+		insteadOf = _<other-url-base>_
+--
+
+For example, with this:
+
+------------
+	[url "git://git.host.xz/"]
+		insteadOf = host.xz:/path/to/
+		insteadOf = work:
+------------
+
+a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
+rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".
+
+If you want to rewrite URLs for push only, you can create a
+configuration section of the form:
+
+[verse]
+--
+	[url "__<actual-url-base>__"]
+		pushInsteadOf = _<other-url-base>_
+--
+
+For example, with this:
+
+------------
+	[url "ssh://example.org/"]
+		pushInsteadOf = git://example.org/
+------------
+
+a URL like "git://example.org/path/to/repo.git" will be rewritten to
+"ssh://example.org/path/to/repo.git" for pushes, but pulls will still
+use the original URL.
+
+
+REMOTES[[REMOTES]]
+------------------
+
+The name of one of the following can be used instead
+of a URL as `<repository>` argument:
+
+* a remote in the Git configuration file: `$GIT_DIR/config`,
+* a file in the `$GIT_DIR/remotes` directory, or
+* a file in the `$GIT_DIR/branches` directory.
+
+All of these also allow you to omit the refspec from the command line
+because they each contain a refspec which git will use by default.
+
+Named remote in configuration file
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can choose to provide the name of a remote which you had previously
+configured using linkgit:git-remote[1], linkgit:git-config[1]
+or even by a manual edit to the `$GIT_DIR/config` file.  The URL of
+this remote will be used to access the repository.  The refspec
+of this remote will be used by default when you do
+not provide a refspec on the command line.  The entry in the
+config file would appear like this:
+
+------------
+	[remote "<name>"]
+		url = <URL>
+		pushurl = <pushurl>
+		push = <refspec>
+		fetch = <refspec>
+------------
+
+The `<pushurl>` is used for pushes only. It is optional and defaults
+to `<URL>`. Pushing to a remote affects all defined pushurls or all
+defined urls if no pushurls are defined. Fetch, however, will only
+fetch from the first defined url if multiple urls are defined.
+
+Named file in `$GIT_DIR/remotes`
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can choose to provide the name of a
+file in `$GIT_DIR/remotes`.  The URL
+in this file will be used to access the repository.  The refspec
+in this file will be used as default when you do not
+provide a refspec on the command line.  This file should have the
+following format:
+
+------------
+	URL: one of the above URL formats
+	Push: <refspec>
+	Pull: <refspec>
+
+------------
+
+`Push:` lines are used by 'git push' and
+`Pull:` lines are used by 'git pull' and 'git fetch'.
+Multiple `Push:` and `Pull:` lines may
+be specified for additional branch mappings.
+
+Named file in `$GIT_DIR/branches`
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can choose to provide the name of a
+file in `$GIT_DIR/branches`.
+The URL in this file will be used to access the repository.
+This file should have the following format:
+
+
+------------
+	<URL>#<head>
+------------
+
+`<URL>` is required; `#<head>` is optional.
+
+Depending on the operation, git will use one of the following
+refspecs, if you don't provide one on the command line.
+`<branch>` is the name of this file in `$GIT_DIR/branches` and
+`<head>` defaults to `master`.
+
+git fetch uses:
+
+------------
+	refs/heads/<head>:refs/heads/<branch>
+------------
+
+git push uses:
+
+------------
+	HEAD:refs/heads/<head>
+------------
+
+
+
+
+
+
+MERGE STRATEGIES
+----------------
+
+The merge mechanism (`git merge` and `git pull` commands) allows the
+backend 'merge strategies' to be chosen with `-s` option.  Some strategies
+can also take their own options, which can be passed by giving `-X<option>`
+arguments to `git merge` and/or `git pull`.
+
+ort::
+	This is the default merge strategy when pulling or merging one
+	branch.  This strategy can only resolve two heads using a
+	3-way merge algorithm.  When there is more than one common
+	ancestor that can be used for 3-way merge, it creates a merged
+	tree of the common ancestors and uses that as the reference
+	tree for the 3-way merge.  This has been reported to result in
+	fewer merge conflicts without causing mismerges by tests done
+	on actual merge commits taken from Linux 2.6 kernel
+	development history.  Additionally this strategy can detect
+	and handle merges involving renames.  It does not make use of
+	detected copies.  The name for this algorithm is an acronym
+	("Ostensibly Recursive's Twin") and came from the fact that it
+	was written as a replacement for the previous default
+	algorithm, `recursive`.
++
+The 'ort' strategy can take the following options:
+
+ours;;
+	This option forces conflicting hunks to be auto-resolved cleanly by
+	favoring 'our' version.  Changes from the other tree that do not
+	conflict with our side are reflected in the merge result.
+	For a binary file, the entire contents are taken from our side.
++
+This should not be confused with the 'ours' merge strategy, which does not
+even look at what the other tree contains at all.  It discards everything
+the other tree did, declaring 'our' history contains all that happened in it.
+
+theirs;;
+	This is the opposite of 'ours'; note that, unlike 'ours', there is
+	no 'theirs' merge strategy to confuse this merge option with.
+
+ignore-space-change;;
+ignore-all-space;;
+ignore-space-at-eol;;
+ignore-cr-at-eol;;
+	Treats lines with the indicated type of whitespace change as
+	unchanged for the sake of a three-way merge.  Whitespace
+	changes mixed with other changes to a line are not ignored.
+	See also linkgit:git-diff[1] `-b`, `-w`,
+	`--ignore-space-at-eol`, and `--ignore-cr-at-eol`.
++
+* If 'their' version only introduces whitespace changes to a line,
+  'our' version is used;
+* If 'our' version introduces whitespace changes but 'their'
+  version includes a substantial change, 'their' version is used;
+* Otherwise, the merge proceeds in the usual way.
+
+renormalize;;
+	This runs a virtual check-out and check-in of all three stages
+	of a file when resolving a three-way merge.  This option is
+	meant to be used when merging branches with different clean
+	filters or end-of-line normalization rules.  See "Merging
+	branches with differing checkin/checkout attributes" in
+	linkgit:gitattributes[5] for details.
+
+no-renormalize;;
+	Disables the `renormalize` option.  This overrides the
+	`merge.renormalize` configuration variable.
+
+find-renames[=<n>];;
+	Turn on rename detection, optionally setting the similarity
+	threshold.  This is the default. This overrides the
+	'merge.renames' configuration variable.
+	See also linkgit:git-diff[1] `--find-renames`.
+
+rename-threshold=<n>;;
+	Deprecated synonym for `find-renames=<n>`.
+
+subtree[=<path>];;
+	This option is a more advanced form of 'subtree' strategy, where
+	the strategy makes a guess on how two trees must be shifted to
+	match with each other when merging.  Instead, the specified path
+	is prefixed (or stripped from the beginning) to make the shape of
+	two trees to match.
+
+recursive::
+	This can only resolve two heads using a 3-way merge
+	algorithm.  When there is more than one common
+	ancestor that can be used for 3-way merge, it creates a
+	merged tree of the common ancestors and uses that as
+	the reference tree for the 3-way merge.  This has been
+	reported to result in fewer merge conflicts without
+	causing mismerges by tests done on actual merge commits
+	taken from Linux 2.6 kernel development history.
+	Additionally this can detect and handle merges involving
+	renames.  It does not make use of detected copies.  This was
+	the default strategy for resolving two heads from Git v0.99.9k
+	until v2.33.0.
++
+The 'recursive' strategy takes the same options as 'ort'.  However,
+there are three additional options that 'ort' ignores (not documented
+above) that are potentially useful with the 'recursive' strategy:
+
+patience;;
+	Deprecated synonym for `diff-algorithm=patience`.
+
+diff-algorithm=[patience|minimal|histogram|myers];;
+	Use a different diff algorithm while merging, which can help
+	avoid mismerges that occur due to unimportant matching lines
+	(such as braces from distinct functions).  See also
+	linkgit:git-diff[1] `--diff-algorithm`.  Note that `ort`
+	specifically uses `diff-algorithm=histogram`, while `recursive`
+	defaults to the `diff.algorithm` config setting.
+
+no-renames;;
+	Turn off rename detection. This overrides the `merge.renames`
+	configuration variable.
+	See also linkgit:git-diff[1] `--no-renames`.
+
+resolve::
+	This can only resolve two heads (i.e. the current branch
+	and another branch you pulled from) using a 3-way merge
+	algorithm.  It tries to carefully detect criss-cross
+	merge ambiguities.  It does not handle renames.
+
+octopus::
+	This resolves cases with more than two heads, but refuses to do
+	a complex merge that needs manual resolution.  It is
+	primarily meant to be used for bundling topic branch
+	heads together.  This is the default merge strategy when
+	pulling or merging more than one branch.
+
+ours::
+	This resolves any number of heads, but the resulting tree of the
+	merge is always that of the current branch head, effectively
+	ignoring all changes from all other branches.  It is meant to
+	be used to supersede old development history of side
+	branches.  Note that this is different from the -Xours option to
+	the 'recursive' merge strategy.
+
+subtree::
+	This is a modified `ort` strategy. When merging trees A and
+	B, if B corresponds to a subtree of A, B is first adjusted to
+	match the tree structure of A, instead of reading the trees at
+	the same level. This adjustment is also done to the common
+	ancestor tree.
+
+With the strategies that use 3-way merge (including the default, 'ort'),
+if a change is made on both branches, but later reverted on one of the
+branches, that change will be present in the merged result; some people find
+this behavior confusing.  It occurs because only the heads and the merge base
+are considered when performing a merge, not the individual commits.  The merge
+algorithm therefore considers the reverted change as no change at all, and
+substitutes the changed version instead.
+
+
+DEFAULT BEHAVIOUR
+-----------------
+
+Often people use `git pull` without giving any parameter.
+Traditionally, this has been equivalent to saying `git pull
+origin`.  However, when configuration `branch.<name>.remote` is
+present while on branch `<name>`, that value is used instead of
+`origin`.
+
+In order to determine what URL to use to fetch from, the value
+of the configuration `remote.<origin>.url` is consulted
+and if there is not any such variable, the value on the `URL:` line
+in `$GIT_DIR/remotes/<origin>` is used.
+
+In order to determine what remote branches to fetch (and
+optionally store in the remote-tracking branches) when the command is
+run without any refspec parameters on the command line, values
+of the configuration variable `remote.<origin>.fetch` are
+consulted, and if there aren't any, `$GIT_DIR/remotes/<origin>`
+is consulted and its `Pull:` lines are used.
+In addition to the refspec formats described in the OPTIONS
+section, you can have a globbing refspec that looks like this:
+
+------------
+refs/heads/*:refs/remotes/origin/*
+------------
+
+A globbing refspec must have a non-empty RHS (i.e. must store
+what were fetched in remote-tracking branches), and its LHS and RHS
+must end with `/*`.  The above specifies that all remote
+branches are tracked using remote-tracking branches in
+`refs/remotes/origin/` hierarchy under the same name.
+
+The rule to determine which remote branch to merge after
+fetching is a bit involved, in order not to break backward
+compatibility.
+
+If explicit refspecs were given on the command
+line of `git pull`, they are all merged.
+
+When no refspec was given on the command line, then `git pull`
+uses the refspec from the configuration or
+`$GIT_DIR/remotes/<origin>`.  In such cases, the following
+rules apply:
+
+. If `branch.<name>.merge` configuration for the current
+  branch `<name>` exists, that is the name of the branch at the
+  remote site that is merged.
+
+. If the refspec is a globbing one, nothing is merged.
+
+. Otherwise the remote branch of the first refspec is merged.
+
+
+EXAMPLES
+--------
+
+* Update the remote-tracking branches for the repository
+  you cloned from, then merge one of them into your
+  current branch:
++
+------------------------------------------------
+$ git pull
+$ git pull origin
+------------------------------------------------
++
+Normally the branch merged in is the HEAD of the remote repository,
+but the choice is determined by the branch.<name>.remote and
+branch.<name>.merge options; see linkgit:git-config[1] for details.
+
+* Merge into the current branch the remote branch `next`:
++
+------------------------------------------------
+$ git pull origin next
+------------------------------------------------
++
+This leaves a copy of `next` temporarily in FETCH_HEAD, and
+updates the remote-tracking branch `origin/next`.
+The same can be done by invoking fetch and merge:
++
+------------------------------------------------
+$ git fetch origin
+$ git merge origin/next
+------------------------------------------------
+
+
+If you tried a pull which resulted in complex conflicts and
+would want to start over, you can recover with 'git reset'.
+
+
+SECURITY
+--------
+The fetch and push protocols are not designed to prevent one side from
+stealing data from the other repository that was not intended to be
+shared. If you have private data that you need to protect from a malicious
+peer, your best option is to store it in another repository. This applies
+to both clients and servers. In particular, namespaces on a server are not
+effective for read access control; you should only grant read access to a
+namespace to clients that you would trust with read access to the entire
+repository.
+
+The known attack vectors are as follows:
+
+. The victim sends "have" lines advertising the IDs of objects it has that
+  are not explicitly intended to be shared but can be used to optimize the
+  transfer if the peer also has them. The attacker chooses an object ID X
+  to steal and sends a ref to X, but isn't required to send the content of
+  X because the victim already has it. Now the victim believes that the
+  attacker has X, and it sends the content of X back to the attacker
+  later. (This attack is most straightforward for a client to perform on a
+  server, by creating a ref to X in the namespace the client has access
+  to and then fetching it. The most likely way for a server to perform it
+  on a client is to "merge" X into a public branch and hope that the user
+  does additional work on this branch and pushes it back to the server
+  without noticing the merge.)
+
+. As in #1, the attacker chooses an object ID X to steal. The victim sends
+  an object Y that the attacker already has, and the attacker falsely
+  claims to have X and not Y, so the victim sends Y as a delta against X.
+  The delta reveals regions of X that are similar to Y to the attacker.
+
+
+BUGS
+----
+Using --recurse-submodules can only fetch new commits in already checked
+out submodules right now. When e.g. upstream added a new submodule in the
+just fetched commits of the superproject the submodule itself cannot be
+fetched, making it impossible to check out that submodule later without
+having to do a fetch again. This is expected to be fixed in a future Git
+version.
+
+SEE ALSO
+--------
+linkgit:git-fetch[1], linkgit:git-merge[1], linkgit:git-config[1]
+
+GIT
+---
+Part of the linkgit:git[1] suite
diff --git a/external/docs/content/docs/MyFirstContribution/2.46.0.html b/external/docs/content/docs/MyFirstContribution/2.46.0.html
index 075cc9f91e..570b901519 100644
--- a/external/docs/content/docs/MyFirstContribution/2.46.0.html
+++ b/external/docs/content/docs/MyFirstContribution/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/MyFirstContribution/2.46.0/index.html"
 - "/docs/MyFirstContribution/2.46.1/index.html"
+- "/docs/MyFirstContribution/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="summary"><a class="anchor" href="#summary"></a>Summary</h2>
diff --git a/external/docs/content/docs/MyFirstObjectWalk/2.45.0.html b/external/docs/content/docs/MyFirstObjectWalk/2.45.0.html
index a60f1278a5..3607cdb1e2 100644
--- a/external/docs/content/docs/MyFirstObjectWalk/2.45.0.html
+++ b/external/docs/content/docs/MyFirstObjectWalk/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/MyFirstObjectWalk/2.45.2/index.html"
 - "/docs/MyFirstObjectWalk/2.46.0/index.html"
 - "/docs/MyFirstObjectWalk/2.46.1/index.html"
+- "/docs/MyFirstObjectWalk/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_whats_an_object_walk"><a class="anchor" href="#_whats_an_object_walk"></a>What&#8217;s an Object Walk?</h2>
diff --git a/external/docs/content/docs/SubmittingPatches/2.46.0.html b/external/docs/content/docs/SubmittingPatches/2.46.0.html
index 15d1ea53e9..6ad6da949f 100644
--- a/external/docs/content/docs/SubmittingPatches/2.46.0.html
+++ b/external/docs/content/docs/SubmittingPatches/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/SubmittingPatches/2.46.0/index.html"
 - "/docs/SubmittingPatches/2.46.1/index.html"
+- "/docs/SubmittingPatches/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_guidelines"><a class="anchor" href="#_guidelines"></a>Guidelines</h2>
diff --git a/external/docs/content/docs/api-error-handling/2.37.0.html b/external/docs/content/docs/api-error-handling/2.37.0.html
index bc375ca878..25409b7ea6 100644
--- a/external/docs/content/docs/api-error-handling/2.37.0.html
+++ b/external/docs/content/docs/api-error-handling/2.37.0.html
@@ -53,6 +53,7 @@
 - "/docs/api-error-handling/2.45.2/index.html"
 - "/docs/api-error-handling/2.46.0/index.html"
 - "/docs/api-error-handling/2.46.1/index.html"
+- "/docs/api-error-handling/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/api-index-skel/2.43.0.html b/external/docs/content/docs/api-index-skel/2.43.0.html
index c03ece3273..ccfca41e69 100644
--- a/external/docs/content/docs/api-index-skel/2.43.0.html
+++ b/external/docs/content/docs/api-index-skel/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/api-index-skel/2.45.2/index.html"
 - "/docs/api-index-skel/2.46.0/index.html"
 - "/docs/api-index-skel/2.46.1/index.html"
+- "/docs/api-index-skel/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/api-merge/2.42.0.html b/external/docs/content/docs/api-merge/2.42.0.html
index f050eaf3e9..8a0fc0802a 100644
--- a/external/docs/content/docs/api-merge/2.42.0.html
+++ b/external/docs/content/docs/api-merge/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/api-merge/2.45.2/index.html"
 - "/docs/api-merge/2.46.0/index.html"
 - "/docs/api-merge/2.46.1/index.html"
+- "/docs/api-merge/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/api-parse-options/2.38.0.html b/external/docs/content/docs/api-parse-options/2.38.0.html
index b4e94afbd3..3847f14440 100644
--- a/external/docs/content/docs/api-parse-options/2.38.0.html
+++ b/external/docs/content/docs/api-parse-options/2.38.0.html
@@ -45,6 +45,7 @@
 - "/docs/api-parse-options/2.45.2/index.html"
 - "/docs/api-parse-options/2.46.0/index.html"
 - "/docs/api-parse-options/2.46.1/index.html"
+- "/docs/api-parse-options/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/api-simple-ipc/2.43.0.html b/external/docs/content/docs/api-simple-ipc/2.43.0.html
index e257ababd6..53b2675e83 100644
--- a/external/docs/content/docs/api-simple-ipc/2.43.0.html
+++ b/external/docs/content/docs/api-simple-ipc/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/api-simple-ipc/2.45.2/index.html"
 - "/docs/api-simple-ipc/2.46.0/index.html"
 - "/docs/api-simple-ipc/2.46.1/index.html"
+- "/docs/api-simple-ipc/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/api-trace2/2.44.0.html b/external/docs/content/docs/api-trace2/2.44.0.html
index d4f1df3ff9..c6972601b0 100644
--- a/external/docs/content/docs/api-trace2/2.44.0.html
+++ b/external/docs/content/docs/api-trace2/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/api-trace2/2.45.2/index.html"
 - "/docs/api-trace2/2.46.0/index.html"
 - "/docs/api-trace2/2.46.1/index.html"
+- "/docs/api-trace2/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/bitmap-format/2.46.0.html b/external/docs/content/docs/bitmap-format/2.46.0.html
index fd83a2c4ef..355affad0f 100644
--- a/external/docs/content/docs/bitmap-format/2.46.0.html
+++ b/external/docs/content/docs/bitmap-format/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/bitmap-format/2.46.0/index.html"
 - "/docs/bitmap-format/2.46.1/index.html"
+- "/docs/bitmap-format/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_pack_and_multi_pack_bitmaps"><a class="anchor" href="#_pack_and_multi_pack_bitmaps"></a>Pack and multi-pack bitmaps</h2>
diff --git a/external/docs/content/docs/bundle-uri/2.40.0.html b/external/docs/content/docs/bundle-uri/2.40.0.html
index 5b4d14aa77..f43816832d 100644
--- a/external/docs/content/docs/bundle-uri/2.40.0.html
+++ b/external/docs/content/docs/bundle-uri/2.40.0.html
@@ -33,6 +33,7 @@
 - "/docs/bundle-uri/2.45.2/index.html"
 - "/docs/bundle-uri/2.46.0/index.html"
 - "/docs/bundle-uri/2.46.1/index.html"
+- "/docs/bundle-uri/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/commit-graph/2.43.0.html b/external/docs/content/docs/commit-graph/2.43.0.html
index 6629e97ce0..587c46149e 100644
--- a/external/docs/content/docs/commit-graph/2.43.0.html
+++ b/external/docs/content/docs/commit-graph/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/commit-graph/2.45.2/index.html"
 - "/docs/commit-graph/2.46.0/index.html"
 - "/docs/commit-graph/2.46.1/index.html"
+- "/docs/commit-graph/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/diff-format/2.43.0.html b/external/docs/content/docs/diff-format/2.43.0.html
index 927445726f..f6a7b63d8f 100644
--- a/external/docs/content/docs/diff-format/2.43.0.html
+++ b/external/docs/content/docs/diff-format/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/diff-format/2.45.2/index.html"
 - "/docs/diff-format/2.46.0/index.html"
 - "/docs/diff-format/2.46.1/index.html"
+- "/docs/diff-format/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_raw_output_format"><a class="anchor" href="#_raw_output_format"></a>Raw output format</h2>
diff --git a/external/docs/content/docs/diff-generate-patch/2.43.0.html b/external/docs/content/docs/diff-generate-patch/2.43.0.html
index bbfed5c814..633b975954 100644
--- a/external/docs/content/docs/diff-generate-patch/2.43.0.html
+++ b/external/docs/content/docs/diff-generate-patch/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/diff-generate-patch/2.45.2/index.html"
 - "/docs/diff-generate-patch/2.46.0/index.html"
 - "/docs/diff-generate-patch/2.46.1/index.html"
+- "/docs/diff-generate-patch/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="generate_patch_text_with_p"><a class="anchor" href="#generate_patch_text_with_p"></a>Generating patch text with -p</h2>
diff --git a/external/docs/content/docs/diff-options/2.46.0.html b/external/docs/content/docs/diff-options/2.46.0.html
index 57ef92f73a..1a418c1889 100644
--- a/external/docs/content/docs/diff-options/2.46.0.html
+++ b/external/docs/content/docs/diff-options/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/diff-options/2.46.0/index.html"
 - "/docs/diff-options/2.46.1/index.html"
+- "/docs/diff-options/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/directory-rename-detection/2.33.1.html b/external/docs/content/docs/directory-rename-detection/2.33.1.html
index 4d67f1f881..41df652e25 100644
--- a/external/docs/content/docs/directory-rename-detection/2.33.1.html
+++ b/external/docs/content/docs/directory-rename-detection/2.33.1.html
@@ -86,6 +86,7 @@
 - "/docs/directory-rename-detection/2.45.2/index.html"
 - "/docs/directory-rename-detection/2.46.0/index.html"
 - "/docs/directory-rename-detection/2.46.1/index.html"
+- "/docs/directory-rename-detection/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/fetch-options.html b/external/docs/content/docs/fetch-options.html
index cc47df51ca..ad5db8b0be 100644
--- a/external/docs/content/docs/fetch-options.html
+++ b/external/docs/content/docs/fetch-options.html
@@ -6,8 +6,8 @@
 subsection: manual
 title: Git - fetch-options Documentation
 docname: fetch-options
-version: 2.45.0
-latest-changes: 2.45.0
+version: 2.46.2
+latest-changes: 2.46.2
 aliases:
 - "/docs/fetch-options/index.html"
 ---
@@ -17,8 +17,9 @@
 <dl>
 <dt class="hdlist1" id="Documentation/fetch-options.txt---no-all"> <a class="anchor" href="#Documentation/fetch-options.txt---no-all"></a>--[no-]all </dt>
 <dd>
-<p>Fetch all remotes. This overrides the configuration variable
-<code>fetch.all</code>.</p>
+<p>Fetch all remotes, except for the ones that has the
+<code>remote.&lt;name&gt;.skipFetchAll</code> configuration variable set.
+This overrides the configuration variable fetch.all`.</p>
 </dd>
 <dt class="hdlist1" id="Documentation/fetch-options.txt--a"> <a class="anchor" href="#Documentation/fetch-options.txt--a"></a>-a </dt>
 <dt class="hdlist1" id="Documentation/fetch-options.txt---append"> <a class="anchor" href="#Documentation/fetch-options.txt---append"></a>--append </dt>
diff --git a/external/docs/content/docs/fetch-options/2.46.2.html b/external/docs/content/docs/fetch-options/2.46.2.html
new file mode 100644
index 0000000000..747626aa96
--- /dev/null
+++ b/external/docs/content/docs/fetch-options/2.46.2.html
@@ -0,0 +1,378 @@
+---
+### DO NOT EDIT! Generated by script/update-docs.rb
+
+category: manual
+section: documentation
+subsection: manual
+title: Git - fetch-options Documentation
+docname: fetch-options
+version: 2.46.2
+aliases:
+- "/docs/fetch-options/2.46.2/index.html"
+---
+<div id="preamble">
+<div class="sectionbody">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---no-all"> <a class="anchor" href="#Documentation/fetch-options.txt---no-all"></a>--[no-]all </dt>
+<dd>
+<p>Fetch all remotes, except for the ones that has the
+<code>remote.&lt;name&gt;.skipFetchAll</code> configuration variable set.
+This overrides the configuration variable fetch.all`.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--a"> <a class="anchor" href="#Documentation/fetch-options.txt--a"></a>-a </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---append"> <a class="anchor" href="#Documentation/fetch-options.txt---append"></a>--append </dt>
+<dd>
+<p>Append ref names and object names of fetched refs to the
+existing contents of <code>.git/FETCH_HEAD</code>.  Without this
+option old data in <code>.git/FETCH_HEAD</code> will be overwritten.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---atomic"> <a class="anchor" href="#Documentation/fetch-options.txt---atomic"></a>--atomic </dt>
+<dd>
+<p>Use an atomic transaction to update local refs. Either all refs are
+updated, or on error, no refs are updated.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---depthltdepthgt"> <a class="anchor" href="#Documentation/fetch-options.txt---depthltdepthgt"></a>--depth=&lt;depth&gt; </dt>
+<dd>
+<p>Limit fetching to the specified number of commits from the tip of
+each remote branch history. If fetching to a <em>shallow</em> repository
+created by <code>git clone</code> with <code>--depth=&lt;depth&gt;</code> option (see
+<a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a>), deepen or shorten the history to the specified
+number of commits. Tags for the deepened commits are not fetched.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---deepenltdepthgt"> <a class="anchor" href="#Documentation/fetch-options.txt---deepenltdepthgt"></a>--deepen=&lt;depth&gt; </dt>
+<dd>
+<p>Similar to --depth, except it specifies the number of commits
+from the current shallow boundary instead of from the tip of
+each remote branch history.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---shallow-sinceltdategt"> <a class="anchor" href="#Documentation/fetch-options.txt---shallow-sinceltdategt"></a>--shallow-since=&lt;date&gt; </dt>
+<dd>
+<p>Deepen or shorten the history of a shallow repository to
+include all reachable commits after &lt;date&gt;.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---shallow-excludeltrevisiongt"> <a class="anchor" href="#Documentation/fetch-options.txt---shallow-excludeltrevisiongt"></a>--shallow-exclude=&lt;revision&gt; </dt>
+<dd>
+<p>Deepen or shorten the history of a shallow repository to
+exclude commits reachable from a specified remote branch or tag.
+This option can be specified multiple times.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---unshallow"> <a class="anchor" href="#Documentation/fetch-options.txt---unshallow"></a>--unshallow </dt>
+<dd>
+<p>If the source repository is complete, convert a shallow
+repository to a complete one, removing all the limitations
+imposed by shallow repositories.</p>
+<div class="paragraph">
+<p>If the source repository is shallow, fetch as much as possible so that
+the current repository has the same history as the source repository.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---update-shallow"> <a class="anchor" href="#Documentation/fetch-options.txt---update-shallow"></a>--update-shallow </dt>
+<dd>
+<p>By default when fetching from a shallow repository,
+<code>git fetch</code> refuses refs that require updating
+.git/shallow. This option updates .git/shallow and accepts such
+refs.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---negotiation-tipltcommitglobgt"> <a class="anchor" href="#Documentation/fetch-options.txt---negotiation-tipltcommitglobgt"></a>--negotiation-tip=&lt;commit|glob&gt; </dt>
+<dd>
+<p>By default, Git will report, to the server, commits reachable
+from all local refs to find common commits in an attempt to
+reduce the size of the to-be-received packfile. If specified,
+Git will only report commits reachable from the given tips.
+This is useful to speed up fetches when the user knows which
+local ref is likely to have commits in common with the
+upstream ref being fetched.</p>
+<div class="paragraph">
+<p>This option may be specified more than once; if so, Git will report
+commits reachable from any of the given commits.</p>
+</div>
+<div class="paragraph">
+<p>The argument to this option may be a glob on ref names, a ref, or the (possibly
+abbreviated) SHA-1 of a commit. Specifying a glob is equivalent to specifying
+this option multiple times, one for each matching ref name.</p>
+</div>
+<div class="paragraph">
+<p>See also the <code>fetch.negotiationAlgorithm</code> and <code>push.negotiate</code>
+configuration variables documented in <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>, and the
+<code>--negotiate-only</code> option below.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---negotiate-only"> <a class="anchor" href="#Documentation/fetch-options.txt---negotiate-only"></a>--negotiate-only </dt>
+<dd>
+<p>Do not fetch anything from the server, and instead print the
+ancestors of the provided <code>--negotiation-tip=*</code> arguments,
+which we have in common with the server.</p>
+<div class="paragraph">
+<p>This is incompatible with <code>--recurse-submodules=[yes|on-demand]</code>.
+Internally this is used to implement the <code>push.negotiate</code> option, see
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---dry-run"> <a class="anchor" href="#Documentation/fetch-options.txt---dry-run"></a>--dry-run </dt>
+<dd>
+<p>Show what would be done, without making any changes.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---porcelain"> <a class="anchor" href="#Documentation/fetch-options.txt---porcelain"></a>--porcelain </dt>
+<dd>
+<p>Print the output to standard output in an easy-to-parse format for
+scripts. See section OUTPUT in <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> for details.</p>
+<div class="paragraph">
+<p>This is incompatible with <code>--recurse-submodules=[yes|on-demand]</code> and takes
+precedence over the <code>fetch.output</code> config option.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---no-write-fetch-head"> <a class="anchor" href="#Documentation/fetch-options.txt---no-write-fetch-head"></a>--[no-]write-fetch-head </dt>
+<dd>
+<p>Write the list of remote refs fetched in the <code>FETCH_HEAD</code>
+file directly under <code>$GIT_DIR</code>.  This is the default.
+Passing <code>--no-write-fetch-head</code> from the command line tells
+Git not to write the file.  Under <code>--dry-run</code> option, the
+file is never written.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--f"> <a class="anchor" href="#Documentation/fetch-options.txt--f"></a>-f </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---force"> <a class="anchor" href="#Documentation/fetch-options.txt---force"></a>--force </dt>
+<dd>
+<p>When <em>git fetch</em> is used with <code>&lt;src&gt;:&lt;dst&gt;</code> refspec, it may
+refuse to update the local branch as discussed
+in the <code>&lt;refspec&gt;</code> part below.
+This option overrides that check.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--k"> <a class="anchor" href="#Documentation/fetch-options.txt--k"></a>-k </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---keep"> <a class="anchor" href="#Documentation/fetch-options.txt---keep"></a>--keep </dt>
+<dd>
+<p>Keep downloaded pack.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---multiple"> <a class="anchor" href="#Documentation/fetch-options.txt---multiple"></a>--multiple </dt>
+<dd>
+<p>Allow several &lt;repository&gt; and &lt;group&gt; arguments to be
+specified. No &lt;refspec&gt;s may be specified.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---no-auto-maintenance"> <a class="anchor" href="#Documentation/fetch-options.txt---no-auto-maintenance"></a>--[no-]auto-maintenance </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---no-auto-gc"> <a class="anchor" href="#Documentation/fetch-options.txt---no-auto-gc"></a>--[no-]auto-gc </dt>
+<dd>
+<p>Run <code>git maintenance run --auto</code> at the end to perform automatic
+repository maintenance if needed. (<code>--[no-]auto-gc</code> is a synonym.)
+This is enabled by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---no-write-commit-graph"> <a class="anchor" href="#Documentation/fetch-options.txt---no-write-commit-graph"></a>--[no-]write-commit-graph </dt>
+<dd>
+<p>Write a commit-graph after fetching. This overrides the config
+setting <code>fetch.writeCommitGraph</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---prefetch"> <a class="anchor" href="#Documentation/fetch-options.txt---prefetch"></a>--prefetch </dt>
+<dd>
+<p>Modify the configured refspec to place all refs into the
+<code>refs/prefetch/</code> namespace. See the <code>prefetch</code> task in
+<a href='{{< relurl "docs/git-maintenance" >}}'>git-maintenance[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--p"> <a class="anchor" href="#Documentation/fetch-options.txt--p"></a>-p </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---prune"> <a class="anchor" href="#Documentation/fetch-options.txt---prune"></a>--prune </dt>
+<dd>
+<p>Before fetching, remove any remote-tracking references that no
+longer exist on the remote.  Tags are not subject to pruning
+if they are fetched only because of the default tag
+auto-following or due to a --tags option.  However, if tags
+are fetched due to an explicit refspec (either on the command
+line or in the remote configuration, for example if the remote
+was cloned with the --mirror option), then they are also
+subject to pruning. Supplying <code>--prune-tags</code> is a shorthand for
+providing the tag refspec.</p>
+<div class="paragraph">
+<p>See the PRUNING section below for more details.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--P"> <a class="anchor" href="#Documentation/fetch-options.txt--P"></a>-P </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---prune-tags"> <a class="anchor" href="#Documentation/fetch-options.txt---prune-tags"></a>--prune-tags </dt>
+<dd>
+<p>Before fetching, remove any local tags that no longer exist on
+the remote if <code>--prune</code> is enabled. This option should be used
+more carefully, unlike <code>--prune</code> it will remove any local
+references (local tags) that have been created. This option is
+a shorthand for providing the explicit tag refspec along with
+<code>--prune</code>, see the discussion about that in its documentation.</p>
+<div class="paragraph">
+<p>See the PRUNING section below for more details.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--n"> <a class="anchor" href="#Documentation/fetch-options.txt--n"></a>-n </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---no-tags"> <a class="anchor" href="#Documentation/fetch-options.txt---no-tags"></a>--no-tags </dt>
+<dd>
+<p>By default, tags that point at objects that are downloaded
+from the remote repository are fetched and stored locally.
+This option disables this automatic tag following. The default
+behavior for a remote may be specified with the remote.&lt;name&gt;.tagOpt
+setting. See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---refetch"> <a class="anchor" href="#Documentation/fetch-options.txt---refetch"></a>--refetch </dt>
+<dd>
+<p>Instead of negotiating with the server to avoid transferring commits and
+associated objects that are already present locally, this option fetches
+all objects as a fresh clone would. Use this to reapply a partial clone
+filter from configuration or using <code>--filter=</code> when the filter
+definition has changed. Automatic post-fetch maintenance will perform
+object database pack consolidation to remove any duplicate objects.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---refmapltrefspecgt"> <a class="anchor" href="#Documentation/fetch-options.txt---refmapltrefspecgt"></a>--refmap=&lt;refspec&gt; </dt>
+<dd>
+<p>When fetching refs listed on the command line, use the
+specified refspec (can be given more than once) to map the
+refs to remote-tracking branches, instead of the values of
+<code>remote.*.fetch</code> configuration variables for the remote
+repository.  Providing an empty <code>&lt;refspec&gt;</code> to the
+<code>--refmap</code> option causes Git to ignore the configured
+refspecs and rely entirely on the refspecs supplied as
+command-line arguments. See section on "Configured Remote-tracking
+Branches" for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--t"> <a class="anchor" href="#Documentation/fetch-options.txt--t"></a>-t </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---tags"> <a class="anchor" href="#Documentation/fetch-options.txt---tags"></a>--tags </dt>
+<dd>
+<p>Fetch all tags from the remote (i.e., fetch remote tags
+<code>refs/tags/*</code> into local tags with the same name), in addition
+to whatever else would otherwise be fetched.  Using this
+option alone does not subject tags to pruning, even if --prune
+is used (though tags may be pruned anyway if they are also the
+destination of an explicit refspec; see <code>--prune</code>).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---recurse-submodulesyeson-demandno"> <a class="anchor" href="#Documentation/fetch-options.txt---recurse-submodulesyeson-demandno"></a>--recurse-submodules[=(yes|on-demand|no)] </dt>
+<dd>
+<p>This option controls if and under what conditions new commits of
+submodules should be fetched too. When recursing through submodules,
+<code>git fetch</code> always attempts to fetch "changed" submodules, that is, a
+submodule that has commits that are referenced by a newly fetched
+superproject commit but are missing in the local submodule clone. A
+changed submodule can be fetched as long as it is present locally e.g.
+in <code>$GIT_DIR/modules/</code> (see <a href='{{< relurl "docs/gitsubmodules" >}}'>gitsubmodules[7]</a>); if the upstream
+adds a new submodule, that submodule cannot be fetched until it is
+cloned e.g. by <code>git submodule update</code>.</p>
+<div class="paragraph">
+<p>When set to <em>on-demand</em>, only changed submodules are fetched. When set
+to <em>yes</em>, all populated submodules are fetched and submodules that are
+both unpopulated and changed are fetched. When set to <em>no</em>, submodules
+are never fetched.</p>
+</div>
+<div class="paragraph">
+<p>When unspecified, this uses the value of <code>fetch.recurseSubmodules</code> if it
+is set (see <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>), defaulting to <em>on-demand</em> if unset.
+When this option is used without any value, it defaults to <em>yes</em>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--j"> <a class="anchor" href="#Documentation/fetch-options.txt--j"></a>-j </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---jobsltngt"> <a class="anchor" href="#Documentation/fetch-options.txt---jobsltngt"></a>--jobs=&lt;n&gt; </dt>
+<dd>
+<p>Number of parallel children to be used for all forms of fetching.</p>
+<div class="paragraph">
+<p>If the <code>--multiple</code> option was specified, the different remotes will be fetched
+in parallel. If multiple submodules are fetched, they will be fetched in
+parallel. To control them independently, use the config settings
+<code>fetch.parallel</code> and <code>submodule.fetchJobs</code> (see <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>).</p>
+</div>
+<div class="paragraph">
+<p>Typically, parallel recursive and multi-remote fetches will be faster. By
+default fetches are performed sequentially, not in parallel.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---no-recurse-submodules"> <a class="anchor" href="#Documentation/fetch-options.txt---no-recurse-submodules"></a>--no-recurse-submodules </dt>
+<dd>
+<p>Disable recursive fetching of submodules (this has the same effect as
+using the <code>--recurse-submodules=no</code> option).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---set-upstream"> <a class="anchor" href="#Documentation/fetch-options.txt---set-upstream"></a>--set-upstream </dt>
+<dd>
+<p>If the remote is fetched successfully, add upstream
+(tracking) reference, used by argument-less
+<a href='{{< relurl "docs/git-pull" >}}'>git-pull[1]</a> and other commands. For more information,
+see <code>branch.&lt;name&gt;.merge</code> and <code>branch.&lt;name&gt;.remote</code> in
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---submodule-prefixltpathgt"> <a class="anchor" href="#Documentation/fetch-options.txt---submodule-prefixltpathgt"></a>--submodule-prefix=&lt;path&gt; </dt>
+<dd>
+<p>Prepend &lt;path&gt; to paths printed in informative messages
+such as "Fetching submodule foo".  This option is used
+internally when recursing over submodules.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---recurse-submodules-defaultyeson-demand"> <a class="anchor" href="#Documentation/fetch-options.txt---recurse-submodules-defaultyeson-demand"></a>--recurse-submodules-default=[yes|on-demand] </dt>
+<dd>
+<p>This option is used internally to temporarily provide a
+non-negative default value for the --recurse-submodules
+option.  All other methods of configuring fetch&#8217;s submodule
+recursion (such as settings in <a href='{{< relurl "docs/gitmodules" >}}'>gitmodules[5]</a> and
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>) override this option, as does
+specifying --[no-]recurse-submodules directly.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--u"> <a class="anchor" href="#Documentation/fetch-options.txt--u"></a>-u </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---update-head-ok"> <a class="anchor" href="#Documentation/fetch-options.txt---update-head-ok"></a>--update-head-ok </dt>
+<dd>
+<p>By default <em>git fetch</em> refuses to update the head which
+corresponds to the current branch.  This flag disables the
+check.  This is purely for the internal use for <em>git pull</em>
+to communicate with <em>git fetch</em>, and unless you are
+implementing your own Porcelain you are not supposed to
+use it.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---upload-packltupload-packgt"> <a class="anchor" href="#Documentation/fetch-options.txt---upload-packltupload-packgt"></a>--upload-pack &lt;upload-pack&gt; </dt>
+<dd>
+<p>When given, and the repository to fetch from is handled
+by <em>git fetch-pack</em>, <code>--exec=&lt;upload-pack&gt;</code> is passed to
+the command to specify non-default path for the command
+run on the other end.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--q"> <a class="anchor" href="#Documentation/fetch-options.txt--q"></a>-q </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---quiet"> <a class="anchor" href="#Documentation/fetch-options.txt---quiet"></a>--quiet </dt>
+<dd>
+<p>Pass --quiet to git-fetch-pack and silence any other internally
+used git commands. Progress is not reported to the standard error
+stream.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--v"> <a class="anchor" href="#Documentation/fetch-options.txt--v"></a>-v </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---verbose"> <a class="anchor" href="#Documentation/fetch-options.txt---verbose"></a>--verbose </dt>
+<dd>
+<p>Be verbose.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---progress"> <a class="anchor" href="#Documentation/fetch-options.txt---progress"></a>--progress </dt>
+<dd>
+<p>Progress status is reported on the standard error stream
+by default when it is attached to a terminal, unless -q
+is specified. This flag forces progress status even if the
+standard error stream is not directed to a terminal.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--oltoptiongt"> <a class="anchor" href="#Documentation/fetch-options.txt--oltoptiongt"></a>-o &lt;option&gt; </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---server-optionltoptiongt"> <a class="anchor" href="#Documentation/fetch-options.txt---server-optionltoptiongt"></a>--server-option=&lt;option&gt; </dt>
+<dd>
+<p>Transmit the given string to the server when communicating using
+protocol version 2.  The given string must not contain a NUL or LF
+character.  The server&#8217;s handling of server options, including
+unknown ones, is server-specific.
+When multiple <code>--server-option=&lt;option&gt;</code> are given, they are all
+sent to the other side in the order listed on the command line.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---show-forced-updates"> <a class="anchor" href="#Documentation/fetch-options.txt---show-forced-updates"></a>--show-forced-updates </dt>
+<dd>
+<p>By default, git checks if a branch is force-updated during
+fetch. This can be disabled through fetch.showForcedUpdates, but
+the --show-forced-updates option guarantees this check occurs.
+See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---no-show-forced-updates"> <a class="anchor" href="#Documentation/fetch-options.txt---no-show-forced-updates"></a>--no-show-forced-updates </dt>
+<dd>
+<p>By default, git checks if a branch is force-updated during
+fetch. Pass --no-show-forced-updates or set fetch.showForcedUpdates
+to false to skip this check for performance reasons. If used during
+<em>git-pull</em> the --ff-only option will still check for forced updates
+before attempting a fast-forward update. See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--4"> <a class="anchor" href="#Documentation/fetch-options.txt--4"></a>-4 </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---ipv4"> <a class="anchor" href="#Documentation/fetch-options.txt---ipv4"></a>--ipv4 </dt>
+<dd>
+<p>Use IPv4 addresses only, ignoring IPv6 addresses.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/fetch-options.txt--6"> <a class="anchor" href="#Documentation/fetch-options.txt--6"></a>-6 </dt>
+<dt class="hdlist1" id="Documentation/fetch-options.txt---ipv6"> <a class="anchor" href="#Documentation/fetch-options.txt---ipv6"></a>--ipv6 </dt>
+<dd>
+<p>Use IPv6 addresses only, ignoring IPv4 addresses.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
\ No newline at end of file
diff --git a/external/docs/content/docs/git-add/2.46.0.html b/external/docs/content/docs/git-add/2.46.0.html
index f46fbef2f8..5dc60755d5 100644
--- a/external/docs/content/docs/git-add/2.46.0.html
+++ b/external/docs/content/docs/git-add/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-add/2.46.0/index.html"
 - "/docs/git-add/2.46.1/index.html"
+- "/docs/git-add/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-am/2.46.0.html b/external/docs/content/docs/git-am/2.46.0.html
index e6d6f86086..774e5e8a10 100644
--- a/external/docs/content/docs/git-am/2.46.0.html
+++ b/external/docs/content/docs/git-am/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-am/2.46.0/index.html"
 - "/docs/git-am/2.46.1/index.html"
+- "/docs/git-am/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-annotate/2.41.0.html b/external/docs/content/docs/git-annotate/2.41.0.html
index cc000e0640..a37e3abf93 100644
--- a/external/docs/content/docs/git-annotate/2.41.0.html
+++ b/external/docs/content/docs/git-annotate/2.41.0.html
@@ -29,6 +29,7 @@
 - "/docs/git-annotate/2.45.2/index.html"
 - "/docs/git-annotate/2.46.0/index.html"
 - "/docs/git-annotate/2.46.1/index.html"
+- "/docs/git-annotate/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-apply/2.43.0.html b/external/docs/content/docs/git-apply/2.43.0.html
index 4421f5900f..66c767f3e0 100644
--- a/external/docs/content/docs/git-apply/2.43.0.html
+++ b/external/docs/content/docs/git-apply/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-apply/2.45.2/index.html"
 - "/docs/git-apply/2.46.0/index.html"
 - "/docs/git-apply/2.46.1/index.html"
+- "/docs/git-apply/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-archimport/2.35.0.html b/external/docs/content/docs/git-archimport/2.35.0.html
index 148df2fe8a..34462354f3 100644
--- a/external/docs/content/docs/git-archimport/2.35.0.html
+++ b/external/docs/content/docs/git-archimport/2.35.0.html
@@ -69,6 +69,7 @@
 - "/docs/git-archimport/2.45.2/index.html"
 - "/docs/git-archimport/2.46.0/index.html"
 - "/docs/git-archimport/2.46.1/index.html"
+- "/docs/git-archimport/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-archive/2.46.0.html b/external/docs/content/docs/git-archive/2.46.0.html
index 1d629693b0..cf874aba7d 100644
--- a/external/docs/content/docs/git-archive/2.46.0.html
+++ b/external/docs/content/docs/git-archive/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-archive/2.46.0/index.html"
 - "/docs/git-archive/2.46.1/index.html"
+- "/docs/git-archive/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-bisect-lk2009/2.40.0.html b/external/docs/content/docs/git-bisect-lk2009/2.40.0.html
index 30c2fd8be9..712655bbd8 100644
--- a/external/docs/content/docs/git-bisect-lk2009/2.40.0.html
+++ b/external/docs/content/docs/git-bisect-lk2009/2.40.0.html
@@ -33,6 +33,7 @@
 - "/docs/git-bisect-lk2009/2.45.2/index.html"
 - "/docs/git-bisect-lk2009/2.46.0/index.html"
 - "/docs/git-bisect-lk2009/2.46.1/index.html"
+- "/docs/git-bisect-lk2009/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_abstract"><a class="anchor" href="#_abstract"></a>Abstract</h2>
diff --git a/external/docs/content/docs/git-bisect/2.44.0.html b/external/docs/content/docs/git-bisect/2.44.0.html
index cacf28c5c1..9698799cdd 100644
--- a/external/docs/content/docs/git-bisect/2.44.0.html
+++ b/external/docs/content/docs/git-bisect/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-bisect/2.45.2/index.html"
 - "/docs/git-bisect/2.46.0/index.html"
 - "/docs/git-bisect/2.46.1/index.html"
+- "/docs/git-bisect/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-blame/2.44.0.html b/external/docs/content/docs/git-blame/2.44.0.html
index 9731c2b576..11a7e60417 100644
--- a/external/docs/content/docs/git-blame/2.44.0.html
+++ b/external/docs/content/docs/git-blame/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-blame/2.45.2/index.html"
 - "/docs/git-blame/2.46.0/index.html"
 - "/docs/git-blame/2.46.1/index.html"
+- "/docs/git-blame/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-branch/2.44.0.html b/external/docs/content/docs/git-branch/2.44.0.html
index 9c7af4dec6..4bac14c811 100644
--- a/external/docs/content/docs/git-branch/2.44.0.html
+++ b/external/docs/content/docs/git-branch/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-branch/2.45.2/index.html"
 - "/docs/git-branch/2.46.0/index.html"
 - "/docs/git-branch/2.46.1/index.html"
+- "/docs/git-branch/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-bugreport/2.45.0.html b/external/docs/content/docs/git-bugreport/2.45.0.html
index f5c1a31ef4..98c875e34a 100644
--- a/external/docs/content/docs/git-bugreport/2.45.0.html
+++ b/external/docs/content/docs/git-bugreport/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-bugreport/2.45.2/index.html"
 - "/docs/git-bugreport/2.46.0/index.html"
 - "/docs/git-bugreport/2.46.1/index.html"
+- "/docs/git-bugreport/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-bundle/2.41.0.html b/external/docs/content/docs/git-bundle/2.41.0.html
index 78b0a08822..e6de661676 100644
--- a/external/docs/content/docs/git-bundle/2.41.0.html
+++ b/external/docs/content/docs/git-bundle/2.41.0.html
@@ -29,6 +29,7 @@
 - "/docs/git-bundle/2.45.2/index.html"
 - "/docs/git-bundle/2.46.0/index.html"
 - "/docs/git-bundle/2.46.1/index.html"
+- "/docs/git-bundle/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-cat-file/2.46.1.html b/external/docs/content/docs/git-cat-file/2.46.1.html
index d9fa5b67a9..4511cf72c2 100644
--- a/external/docs/content/docs/git-cat-file/2.46.1.html
+++ b/external/docs/content/docs/git-cat-file/2.46.1.html
@@ -9,6 +9,7 @@
 version: 2.46.1
 aliases:
 - "/docs/git-cat-file/2.46.1/index.html"
+- "/docs/git-cat-file/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-check-attr/2.43.0.html b/external/docs/content/docs/git-check-attr/2.43.0.html
index f8edf246f7..955f9a595d 100644
--- a/external/docs/content/docs/git-check-attr/2.43.0.html
+++ b/external/docs/content/docs/git-check-attr/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-check-attr/2.45.2/index.html"
 - "/docs/git-check-attr/2.46.0/index.html"
 - "/docs/git-check-attr/2.46.1/index.html"
+- "/docs/git-check-attr/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-check-ignore/2.43.0.html b/external/docs/content/docs/git-check-ignore/2.43.0.html
index 8be0fc5bdd..9cfa633e91 100644
--- a/external/docs/content/docs/git-check-ignore/2.43.0.html
+++ b/external/docs/content/docs/git-check-ignore/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-check-ignore/2.45.2/index.html"
 - "/docs/git-check-ignore/2.46.0/index.html"
 - "/docs/git-check-ignore/2.46.1/index.html"
+- "/docs/git-check-ignore/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-check-mailmap/2.31.0.html b/external/docs/content/docs/git-check-mailmap/2.31.0.html
index 12f722fbf2..9fc378f8ce 100644
--- a/external/docs/content/docs/git-check-mailmap/2.31.0.html
+++ b/external/docs/content/docs/git-check-mailmap/2.31.0.html
@@ -104,6 +104,7 @@
 - "/docs/git-check-mailmap/2.45.2/index.html"
 - "/docs/git-check-mailmap/2.46.0/index.html"
 - "/docs/git-check-mailmap/2.46.1/index.html"
+- "/docs/git-check-mailmap/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-check-ref-format/2.43.0.html b/external/docs/content/docs/git-check-ref-format/2.43.0.html
index 1f350dc325..e57d44e67e 100644
--- a/external/docs/content/docs/git-check-ref-format/2.43.0.html
+++ b/external/docs/content/docs/git-check-ref-format/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-check-ref-format/2.45.2/index.html"
 - "/docs/git-check-ref-format/2.46.0/index.html"
 - "/docs/git-check-ref-format/2.46.1/index.html"
+- "/docs/git-check-ref-format/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-checkout-index/2.43.0.html b/external/docs/content/docs/git-checkout-index/2.43.0.html
index 553220bb8a..7a8aaac46f 100644
--- a/external/docs/content/docs/git-checkout-index/2.43.0.html
+++ b/external/docs/content/docs/git-checkout-index/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-checkout-index/2.45.2/index.html"
 - "/docs/git-checkout-index/2.46.0/index.html"
 - "/docs/git-checkout-index/2.46.1/index.html"
+- "/docs/git-checkout-index/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-checkout/2.44.0.html b/external/docs/content/docs/git-checkout/2.44.0.html
index bd8ca871f4..678c28a5f8 100644
--- a/external/docs/content/docs/git-checkout/2.44.0.html
+++ b/external/docs/content/docs/git-checkout/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-checkout/2.45.2/index.html"
 - "/docs/git-checkout/2.46.0/index.html"
 - "/docs/git-checkout/2.46.1/index.html"
+- "/docs/git-checkout/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-cherry-pick/2.45.0.html b/external/docs/content/docs/git-cherry-pick/2.45.0.html
index 228142a685..cc1039c571 100644
--- a/external/docs/content/docs/git-cherry-pick/2.45.0.html
+++ b/external/docs/content/docs/git-cherry-pick/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-cherry-pick/2.45.2/index.html"
 - "/docs/git-cherry-pick/2.46.0/index.html"
 - "/docs/git-cherry-pick/2.46.1/index.html"
+- "/docs/git-cherry-pick/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-cherry/2.0.5.html b/external/docs/content/docs/git-cherry/2.0.5.html
index edf852b9ba..6080680e7a 100644
--- a/external/docs/content/docs/git-cherry/2.0.5.html
+++ b/external/docs/content/docs/git-cherry/2.0.5.html
@@ -196,6 +196,7 @@
 - "/docs/git-cherry/2.45.2/index.html"
 - "/docs/git-cherry/2.46.0/index.html"
 - "/docs/git-cherry/2.46.1/index.html"
+- "/docs/git-cherry/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-citool/2.0.5.html b/external/docs/content/docs/git-citool/2.0.5.html
index 9e084dc4e5..360bbc94e1 100644
--- a/external/docs/content/docs/git-citool/2.0.5.html
+++ b/external/docs/content/docs/git-citool/2.0.5.html
@@ -196,6 +196,7 @@
 - "/docs/git-citool/2.45.2/index.html"
 - "/docs/git-citool/2.46.0/index.html"
 - "/docs/git-citool/2.46.1/index.html"
+- "/docs/git-citool/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-clean/2.45.0.html b/external/docs/content/docs/git-clean/2.45.0.html
index 4ddd2754b7..7ee977e3b6 100644
--- a/external/docs/content/docs/git-clean/2.45.0.html
+++ b/external/docs/content/docs/git-clean/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-clean/2.45.2/index.html"
 - "/docs/git-clean/2.46.0/index.html"
 - "/docs/git-clean/2.46.1/index.html"
+- "/docs/git-clean/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-clone/2.46.0.html b/external/docs/content/docs/git-clone/2.46.0.html
index 72d38e67cc..7d58f27632 100644
--- a/external/docs/content/docs/git-clone/2.46.0.html
+++ b/external/docs/content/docs/git-clone/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-clone/2.46.0/index.html"
 - "/docs/git-clone/2.46.1/index.html"
+- "/docs/git-clone/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-column/2.43.0.html b/external/docs/content/docs/git-column/2.43.0.html
index 9fbccf35ac..fe2048b6da 100644
--- a/external/docs/content/docs/git-column/2.43.0.html
+++ b/external/docs/content/docs/git-column/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-column/2.45.2/index.html"
 - "/docs/git-column/2.46.0/index.html"
 - "/docs/git-column/2.46.1/index.html"
+- "/docs/git-column/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-commit-graph/2.46.0.html b/external/docs/content/docs/git-commit-graph/2.46.0.html
index 638b7653ab..5f6fa44730 100644
--- a/external/docs/content/docs/git-commit-graph/2.46.0.html
+++ b/external/docs/content/docs/git-commit-graph/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-commit-graph/2.46.0/index.html"
 - "/docs/git-commit-graph/2.46.1/index.html"
+- "/docs/git-commit-graph/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-commit-tree/2.45.0.html b/external/docs/content/docs/git-commit-tree/2.45.0.html
index a982a3179a..3912380621 100644
--- a/external/docs/content/docs/git-commit-tree/2.45.0.html
+++ b/external/docs/content/docs/git-commit-tree/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-commit-tree/2.45.2/index.html"
 - "/docs/git-commit-tree/2.46.0/index.html"
 - "/docs/git-commit-tree/2.46.1/index.html"
+- "/docs/git-commit-tree/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-commit/2.46.1.html b/external/docs/content/docs/git-commit/2.46.1.html
index 93ed466730..97a37b6d65 100644
--- a/external/docs/content/docs/git-commit/2.46.1.html
+++ b/external/docs/content/docs/git-commit/2.46.1.html
@@ -9,6 +9,7 @@
 version: 2.46.1
 aliases:
 - "/docs/git-commit/2.46.1/index.html"
+- "/docs/git-commit/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-config.html b/external/docs/content/docs/git-config.html
index cf7448e3c0..820c2c76b8 100644
--- a/external/docs/content/docs/git-config.html
+++ b/external/docs/content/docs/git-config.html
@@ -6,8 +6,8 @@
 subsection: manual
 title: Git - git-config Documentation
 docname: git-config
-version: 2.46.1
-latest-changes: 2.46.1
+version: 2.46.2
+latest-changes: 2.46.2
 aliases:
 - "/docs/git-config/index.html"
 ---
@@ -7390,15 +7390,16 @@ <h3 id="_variables"><a class="anchor" href="#_variables"></a>Variables</h3>
 </dd>
 <dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtskipDefaultUpdate"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtskipDefaultUpdate"></a>remote.&lt;name&gt;.skipDefaultUpdate </dt>
 <dd>
-<p>If true, this remote will be skipped by default when updating
-using <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> or the <code>update</code> subcommand of
-<a href='{{< relurl "docs/git-remote" >}}'>git-remote[1]</a>.</p>
+<p>A deprecated synonym to <code>remote.&lt;name&gt;.skipFetchAll</code> (if
+both are set in the configuration files with different
+values, the value of the last occurrence will be used).</p>
 </dd>
 <dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtskipFetchAll"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtskipFetchAll"></a>remote.&lt;name&gt;.skipFetchAll </dt>
 <dd>
-<p>If true, this remote will be skipped by default when updating
-using <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> or the <code>update</code> subcommand of
-<a href='{{< relurl "docs/git-remote" >}}'>git-remote[1]</a>.</p>
+<p>If true, this remote will be skipped when updating
+using <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>, the <code>update</code> subcommand of
+<a href='{{< relurl "docs/git-remote" >}}'>git-remote[1]</a>, and ignored by the prefetch task
+of <code>git maitenance</code>.</p>
 </dd>
 <dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtreceivepack"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtreceivepack"></a>remote.&lt;name&gt;.receivepack </dt>
 <dd>
diff --git a/external/docs/content/docs/git-config/2.46.2.html b/external/docs/content/docs/git-config/2.46.2.html
new file mode 100644
index 0000000000..ed24d5fb98
--- /dev/null
+++ b/external/docs/content/docs/git-config/2.46.2.html
@@ -0,0 +1,8705 @@
+---
+### DO NOT EDIT! Generated by script/update-docs.rb
+
+category: manual
+section: documentation
+subsection: manual
+title: Git - git-config Documentation
+docname: git-config
+version: 2.46.2
+aliases:
+- "/docs/git-config/2.46.2/index.html"
+---
+<div class="sect1">
+<h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>git-config - Get and set repository or global options</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_synopsis"><a class="anchor" href="#_synopsis"></a>SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="verseblock">
+<pre class="content"><em>git config list</em> [&lt;file-option&gt;] [&lt;display-option&gt;] [--includes]
+<em>git config get</em> [&lt;file-option&gt;] [&lt;display-option&gt;] [--includes] [--all] [--regexp] [--value=&lt;value&gt;] [--fixed-value] [--default=&lt;default&gt;] &lt;name&gt;
+<em>git config set</em> [&lt;file-option&gt;] [--type=&lt;type&gt;] [--all] [--value=&lt;value&gt;] [--fixed-value] &lt;name&gt; &lt;value&gt;
+<em>git config unset</em> [&lt;file-option&gt;] [--all] [--value=&lt;value&gt;] [--fixed-value] &lt;name&gt; &lt;value&gt;
+<em>git config rename-section</em> [&lt;file-option&gt;] &lt;old-name&gt; &lt;new-name&gt;
+<em>git config remove-section</em> [&lt;file-option&gt;] &lt;name&gt;
+<em>git config edit</em> [&lt;file-option&gt;]
+<em>git config</em> [&lt;file-option&gt;] --get-colorbool &lt;name&gt; [&lt;stdout-is-tty&gt;]</pre>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description"><a class="anchor" href="#_description"></a>DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>You can query/set/replace/unset options with this command. The name is
+actually the section and the key separated by a dot, and the value will be
+escaped.</p>
+</div>
+<div class="paragraph">
+<p>Multiple lines can be added to an option by using the <code>--append</code> option.
+If you want to update or unset an option which can occur on multiple
+lines, a <code>value-pattern</code> (which is an extended regular expression,
+unless the <code>--fixed-value</code> option is given) needs to be given.  Only the
+existing values that match the pattern are updated or unset.  If
+you want to handle the lines that do <strong>not</strong> match the pattern, just
+prepend a single exclamation mark in front (see also <a href="#EXAMPLES">EXAMPLES</a>),
+but note that this only works when the <code>--fixed-value</code> option is not
+in use.</p>
+</div>
+<div class="paragraph">
+<p>The <code>--type=&lt;type&gt;</code> option instructs <em>git config</em> to ensure that incoming and
+outgoing values are canonicalize-able under the given &lt;type&gt;.  If no
+<code>--type=&lt;type&gt;</code> is given, no canonicalization will be performed. Callers may
+unset an existing <code>--type</code> specifier with <code>--no-type</code>.</p>
+</div>
+<div class="paragraph">
+<p>When reading, the values are read from the system, global and
+repository local configuration files by default, and options
+<code>--system</code>, <code>--global</code>, <code>--local</code>, <code>--worktree</code> and
+<code>--file &lt;filename&gt;</code> can be used to tell the command to read from only
+that location (see <a href="#FILES">FILES</a>).</p>
+</div>
+<div class="paragraph">
+<p>When writing, the new value is written to the repository local
+configuration file by default, and options <code>--system</code>, <code>--global</code>,
+<code>--worktree</code>, <code>--file &lt;filename&gt;</code> can be used to tell the command to
+write to that location (you can say <code>--local</code> but that is the
+default).</p>
+</div>
+<div class="paragraph">
+<p>This command will fail with non-zero status upon error.  Some exit
+codes are:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The section or key is invalid (ret=1),</p>
+</li>
+<li>
+<p>no section or name was provided (ret=2),</p>
+</li>
+<li>
+<p>the config file is invalid (ret=3),</p>
+</li>
+<li>
+<p>the config file cannot be written (ret=4),</p>
+</li>
+<li>
+<p>you try to unset an option which does not exist (ret=5),</p>
+</li>
+<li>
+<p>you try to unset/set an option for which multiple lines match (ret=5), or</p>
+</li>
+<li>
+<p>you try to use an invalid regexp (ret=6).</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>On success, the command returns the exit code 0.</p>
+</div>
+<div class="paragraph">
+<p>A list of all available configuration variables can be obtained using the
+<code>git help --config</code> command.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_commands"><a class="anchor" href="#_commands"></a>COMMANDS</h2>
+<div class="sectionbody">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-list"> <a class="anchor" href="#Documentation/git-config.txt-list"></a>list </dt>
+<dd>
+<p>List all variables set in config file, along with their values.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-get"> <a class="anchor" href="#Documentation/git-config.txt-get"></a>get </dt>
+<dd>
+<p>Emits the value of the specified key. If key is present multiple times
+in the configuration, emits the last value. If <code>--all</code> is specified,
+emits all values associated with key. Returns error code 1 if key is
+not present.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-set"> <a class="anchor" href="#Documentation/git-config.txt-set"></a>set </dt>
+<dd>
+<p>Set value for one or more config options. By default, this command
+refuses to write multi-valued config options. Passing <code>--all</code> will
+replace all multi-valued config options with the new value, whereas
+<code>--value=</code> will replace all config options whose values match the given
+pattern.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-unset"> <a class="anchor" href="#Documentation/git-config.txt-unset"></a>unset </dt>
+<dd>
+<p>Unset value for one or more config options. By default, this command
+refuses to unset multi-valued keys. Passing <code>--all</code> will unset all
+multi-valued config options, whereas <code>--value</code> will unset all config
+options whose values match the given pattern.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rename-section"> <a class="anchor" href="#Documentation/git-config.txt-rename-section"></a>rename-section </dt>
+<dd>
+<p>Rename the given section to a new name.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remove-section"> <a class="anchor" href="#Documentation/git-config.txt-remove-section"></a>remove-section </dt>
+<dd>
+<p>Remove the given section from the configuration file.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-edit"> <a class="anchor" href="#Documentation/git-config.txt-edit"></a>edit </dt>
+<dd>
+<p>Opens an editor to modify the specified config file; either
+<code>--system</code>, <code>--global</code>, <code>--local</code> (default), <code>--worktree</code>, or
+<code>--file &lt;config-file&gt;</code>.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="OPTIONS"><a class="anchor" href="#OPTIONS"></a>OPTIONS</h2>
+<div class="sectionbody">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt---replace-all"> <a class="anchor" href="#Documentation/git-config.txt---replace-all"></a>--replace-all </dt>
+<dd>
+<p>Default behavior is to replace at most one line. This replaces
+all lines matching the key (and optionally the <code>value-pattern</code>).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---append"> <a class="anchor" href="#Documentation/git-config.txt---append"></a>--append </dt>
+<dd>
+<p>Adds a new line to the option without altering any existing
+values. This is the same as providing <em>--value=^$</em> in <code>set</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---commentltmessagegt"> <a class="anchor" href="#Documentation/git-config.txt---commentltmessagegt"></a>--comment &lt;message&gt; </dt>
+<dd>
+<p>Append a comment at the end of new or modified lines.</p>
+<div class="literalblock">
+<div class="content">
+<pre>If _&lt;message&gt;_ begins with one or more whitespaces followed
+by "#", it is used as-is.  If it begins with "#", a space is
+prepended before it is used.  Otherwise, a string " # " (a
+space followed by a hash followed by a space) is prepended
+to it.  And the resulting string is placed immediately after
+the value defined for the variable.  The _&lt;message&gt;_ must
+not contain linefeed characters (no multi-line comments are
+permitted).</pre>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---all"> <a class="anchor" href="#Documentation/git-config.txt---all"></a>--all </dt>
+<dd>
+<p>With <code>get</code>, return all values for a multi-valued key.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---regexp"> <a class="anchor" href="#Documentation/git-config.txt---regexp"></a>--regexp </dt>
+<dd>
+<p>With <code>get</code>, interpret the name as a regular expression. Regular
+expression matching is currently case-sensitive and done against a
+canonicalized version of the key in which section and variable names
+are lowercased, but subsection names are not.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---urlltURLgt"> <a class="anchor" href="#Documentation/git-config.txt---urlltURLgt"></a>--url=&lt;URL&gt; </dt>
+<dd>
+<p>When given a two-part &lt;name&gt; as &lt;section&gt;.&lt;key&gt;, the value for
+&lt;section&gt;.&lt;URL&gt;.&lt;key&gt; whose &lt;URL&gt; part matches the best to the
+given URL is returned (if no such key exists, the value for
+&lt;section&gt;.&lt;key&gt; is used as a fallback).  When given just the
+&lt;section&gt; as name, do so for all the keys in the section and
+list them.  Returns error code 1 if no value is found.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---global"> <a class="anchor" href="#Documentation/git-config.txt---global"></a>--global </dt>
+<dd>
+<p>For writing options: write to global <code>~/.gitconfig</code> file
+rather than the repository <code>.git/config</code>, write to
+<code>$XDG_CONFIG_HOME/git/config</code> file if this file exists and the
+<code>~/.gitconfig</code> file doesn&#8217;t.</p>
+<div class="paragraph">
+<p>For reading options: read only from global <code>~/.gitconfig</code> and from
+<code>$XDG_CONFIG_HOME/git/config</code> rather than from all available files.</p>
+</div>
+<div class="paragraph">
+<p>See also <a href="#FILES">FILES</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---system"> <a class="anchor" href="#Documentation/git-config.txt---system"></a>--system </dt>
+<dd>
+<p>For writing options: write to system-wide
+<code>$(prefix)/etc/gitconfig</code> rather than the repository
+<code>.git/config</code>.</p>
+<div class="paragraph">
+<p>For reading options: read only from system-wide <code>$(prefix)/etc/gitconfig</code>
+rather than from all available files.</p>
+</div>
+<div class="paragraph">
+<p>See also <a href="#FILES">FILES</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---local"> <a class="anchor" href="#Documentation/git-config.txt---local"></a>--local </dt>
+<dd>
+<p>For writing options: write to the repository <code>.git/config</code> file.
+This is the default behavior.</p>
+<div class="paragraph">
+<p>For reading options: read only from the repository <code>.git/config</code> rather than
+from all available files.</p>
+</div>
+<div class="paragraph">
+<p>See also <a href="#FILES">FILES</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---worktree"> <a class="anchor" href="#Documentation/git-config.txt---worktree"></a>--worktree </dt>
+<dd>
+<p>Similar to <code>--local</code> except that <code>$GIT_DIR/config.worktree</code> is
+read from or written to if <code>extensions.worktreeConfig</code> is
+enabled. If not it&#8217;s the same as <code>--local</code>. Note that <code>$GIT_DIR</code>
+is equal to <code>$GIT_COMMON_DIR</code> for the main working tree, but is of
+the form <code>$GIT_DIR/worktrees/&lt;id&gt;/</code> for other working trees. See
+<a href='{{< relurl "docs/git-worktree" >}}'>git-worktree[1]</a> to learn how to enable
+<code>extensions.worktreeConfig</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt--fltconfig-filegt"> <a class="anchor" href="#Documentation/git-config.txt--fltconfig-filegt"></a>-f &lt;config-file&gt; </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt---fileltconfig-filegt"> <a class="anchor" href="#Documentation/git-config.txt---fileltconfig-filegt"></a>--file &lt;config-file&gt; </dt>
+<dd>
+<p>For writing options: write to the specified file rather than the
+repository <code>.git/config</code>.</p>
+<div class="paragraph">
+<p>For reading options: read only from the specified file rather than from all
+available files.</p>
+</div>
+<div class="paragraph">
+<p>See also <a href="#FILES">FILES</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---blobltblobgt"> <a class="anchor" href="#Documentation/git-config.txt---blobltblobgt"></a>--blob &lt;blob&gt; </dt>
+<dd>
+<p>Similar to <code>--file</code> but use the given blob instead of a file. E.g.
+you can use <em>master:.gitmodules</em> to read values from the file
+<em>.gitmodules</em> in the master branch. See "SPECIFYING REVISIONS"
+section in <a href='{{< relurl "docs/gitrevisions" >}}'>gitrevisions[7]</a> for a more complete list of
+ways to spell blob names.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---fixed-value"> <a class="anchor" href="#Documentation/git-config.txt---fixed-value"></a>--fixed-value </dt>
+<dd>
+<p>When used with the <code>value-pattern</code> argument, treat <code>value-pattern</code> as
+an exact string instead of a regular expression. This will restrict
+the name/value pairs that are matched to only those where the value
+is exactly equal to the <code>value-pattern</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---typelttypegt"> <a class="anchor" href="#Documentation/git-config.txt---typelttypegt"></a>--type &lt;type&gt; </dt>
+<dd>
+<p><em>git config</em> will ensure that any input or output is valid under the given
+type constraint(s), and will canonicalize outgoing values in <code>&lt;type&gt;</code>'s
+canonical form.</p>
+<div class="paragraph">
+<p>Valid <code>&lt;type&gt;</code>'s include:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><em>bool</em>: canonicalize values as either "true" or "false".</p>
+</li>
+<li>
+<p><em>int</em>: canonicalize values as simple decimal numbers. An optional suffix of
+<em>k</em>, <em>m</em>, or <em>g</em> will cause the value to be multiplied by 1024, 1048576, or
+1073741824 upon input.</p>
+</li>
+<li>
+<p><em>bool-or-int</em>: canonicalize according to either <em>bool</em> or <em>int</em>, as described
+above.</p>
+</li>
+<li>
+<p><em>path</em>: canonicalize by expanding a leading <code>~</code> to the value of <code>$HOME</code> and
+<code>~user</code> to the home directory for the specified user. This specifier has no
+effect when setting the value (but you can use <code>git config section.variable
+~/</code> from the command line to let your shell do the expansion.)</p>
+</li>
+<li>
+<p><em>expiry-date</em>: canonicalize by converting from a fixed or relative date-string
+to a timestamp. This specifier has no effect when setting the value.</p>
+</li>
+<li>
+<p><em>color</em>: When getting a value, canonicalize by converting to an ANSI color
+escape sequence. When setting a value, a sanity-check is performed to ensure
+that the given value is canonicalize-able as an ANSI color, but it is written
+as-is.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---bool"> <a class="anchor" href="#Documentation/git-config.txt---bool"></a>--bool </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt---int"> <a class="anchor" href="#Documentation/git-config.txt---int"></a>--int </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt---bool-or-int"> <a class="anchor" href="#Documentation/git-config.txt---bool-or-int"></a>--bool-or-int </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt---path"> <a class="anchor" href="#Documentation/git-config.txt---path"></a>--path </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt---expiry-date"> <a class="anchor" href="#Documentation/git-config.txt---expiry-date"></a>--expiry-date </dt>
+<dd>
+<p>Historical options for selecting a type specifier. Prefer instead <code>--type</code>
+(see above).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---no-type"> <a class="anchor" href="#Documentation/git-config.txt---no-type"></a>--no-type </dt>
+<dd>
+<p>Un-sets the previously set type specifier (if one was previously set). This
+option requests that <em>git config</em> not canonicalize the retrieved variable.
+<code>--no-type</code> has no effect without <code>--type=&lt;type&gt;</code> or <code>--&lt;type&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt--z"> <a class="anchor" href="#Documentation/git-config.txt--z"></a>-z </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt---null"> <a class="anchor" href="#Documentation/git-config.txt---null"></a>--null </dt>
+<dd>
+<p>For all options that output values and/or keys, always
+end values with the null character (instead of a
+newline). Use newline instead as a delimiter between
+key and value. This allows for secure parsing of the
+output without getting confused e.g. by values that
+contain line breaks.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---name-only"> <a class="anchor" href="#Documentation/git-config.txt---name-only"></a>--name-only </dt>
+<dd>
+<p>Output only the names of config variables for <code>list</code> or
+<code>get</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---show-origin"> <a class="anchor" href="#Documentation/git-config.txt---show-origin"></a>--show-origin </dt>
+<dd>
+<p>Augment the output of all queried config options with the
+origin type (file, standard input, blob, command line) and
+the actual origin (config file path, ref, or blob id if
+applicable).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---show-scope"> <a class="anchor" href="#Documentation/git-config.txt---show-scope"></a>--show-scope </dt>
+<dd>
+<p>Similar to <code>--show-origin</code> in that it augments the output of
+all queried config options with the scope of that value
+(worktree, local, global, system, command).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---get-colorboolltnamegtltstdout-is-ttygt"> <a class="anchor" href="#Documentation/git-config.txt---get-colorboolltnamegtltstdout-is-ttygt"></a>--get-colorbool &lt;name&gt; [&lt;stdout-is-tty&gt;] </dt>
+<dd>
+<p>Find the color setting for <code>&lt;name&gt;</code> (e.g. <code>color.diff</code>) and output
+"true" or "false".  <code>&lt;stdout-is-tty&gt;</code> should be either "true" or
+"false", and is taken into account when configuration says
+"auto".  If <code>&lt;stdout-is-tty&gt;</code> is missing, then checks the standard
+output of the command itself, and exits with status 0 if color
+is to be used, or exits with status 1 otherwise.
+When the color setting for <code>name</code> is undefined, the command uses
+<code>color.ui</code> as fallback.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---no-includes"> <a class="anchor" href="#Documentation/git-config.txt---no-includes"></a>--[no-]includes </dt>
+<dd>
+<p>Respect <code>include.*</code> directives in config files when looking up
+values. Defaults to <code>off</code> when a specific file is given (e.g.,
+using <code>--file</code>, <code>--global</code>, etc) and <code>on</code> when searching all
+config files.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---defaultltvaluegt"> <a class="anchor" href="#Documentation/git-config.txt---defaultltvaluegt"></a>--default &lt;value&gt; </dt>
+<dd>
+<p>When using <code>get</code>, and the requested variable is not found, behave as if
+&lt;value&gt; were the value assigned to that variable.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_deprecated_modes"><a class="anchor" href="#_deprecated_modes"></a>DEPRECATED MODES</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The following modes have been deprecated in favor of subcommands. It is
+recommended to migrate to the new syntax.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-emgitconfigltnamegtem"> <a class="anchor" href="#Documentation/git-config.txt-emgitconfigltnamegtem"></a><em>git config &lt;name&gt;</em> </dt>
+<dd>
+<p>Replaced by <code>git config get &lt;name&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-emgitconfigltnamegtltvaluegtltvalue-patterngtem"> <a class="anchor" href="#Documentation/git-config.txt-emgitconfigltnamegtltvaluegtltvalue-patterngtem"></a><em>git config &lt;name&gt; &lt;value&gt; [&lt;value-pattern&gt;]</em> </dt>
+<dd>
+<p>Replaced by <code>git config set [--value=&lt;pattern&gt;] &lt;name&gt; &lt;value&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt--l"> <a class="anchor" href="#Documentation/git-config.txt--l"></a>-l </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt---list"> <a class="anchor" href="#Documentation/git-config.txt---list"></a>--list </dt>
+<dd>
+<p>Replaced by <code>git config list</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---getltnamegtltvalue-patterngt"> <a class="anchor" href="#Documentation/git-config.txt---getltnamegtltvalue-patterngt"></a>--get &lt;name&gt; [&lt;value-pattern&gt;] </dt>
+<dd>
+<p>Replaced by <code>git config get [--value=&lt;pattern&gt;] &lt;name&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---get-allltnamegtltvalue-patterngt"> <a class="anchor" href="#Documentation/git-config.txt---get-allltnamegtltvalue-patterngt"></a>--get-all &lt;name&gt; [&lt;value-pattern&gt;] </dt>
+<dd>
+<p>Replaced by <code>git config get [--value=&lt;pattern&gt;] --all &lt;name&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---get-regexpltname-regexpgt"> <a class="anchor" href="#Documentation/git-config.txt---get-regexpltname-regexpgt"></a>--get-regexp &lt;name-regexp&gt; </dt>
+<dd>
+<p>Replaced by <code>git config get --all --show-names --regexp &lt;name-regexp&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---get-urlmatchltnamegtltURLgt"> <a class="anchor" href="#Documentation/git-config.txt---get-urlmatchltnamegtltURLgt"></a>--get-urlmatch &lt;name&gt; &lt;URL&gt; </dt>
+<dd>
+<p>Replaced by <code>git config get --all --show-names --url=&lt;URL&gt; &lt;name&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---get-colorltnamegtltdefaultgt"> <a class="anchor" href="#Documentation/git-config.txt---get-colorltnamegtltdefaultgt"></a>--get-color &lt;name&gt; [&lt;default&gt;] </dt>
+<dd>
+<p>Replaced by <code>git config get --type=color [--default=&lt;default&gt;] &lt;name&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---addltnamegtltvaluegt"> <a class="anchor" href="#Documentation/git-config.txt---addltnamegtltvaluegt"></a>--add &lt;name&gt; &lt;value&gt; </dt>
+<dd>
+<p>Replaced by <code>git config set --append &lt;name&gt; &lt;value&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---unsetltnamegtltvalue-patterngt"> <a class="anchor" href="#Documentation/git-config.txt---unsetltnamegtltvalue-patterngt"></a>--unset &lt;name&gt; [&lt;value-pattern&gt;] </dt>
+<dd>
+<p>Replaced by <code>git config unset [--value=&lt;pattern&gt;] &lt;name&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---unset-allltnamegtltvalue-patterngt"> <a class="anchor" href="#Documentation/git-config.txt---unset-allltnamegtltvalue-patterngt"></a>--unset-all &lt;name&gt; [&lt;value-pattern&gt;] </dt>
+<dd>
+<p>Replaced by <code>git config unset [--value=&lt;pattern&gt;] --all &lt;name&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---rename-sectionltold-namegtltnew-namegt"> <a class="anchor" href="#Documentation/git-config.txt---rename-sectionltold-namegtltnew-namegt"></a>--rename-section &lt;old-name&gt; &lt;new-name&gt; </dt>
+<dd>
+<p>Replaced by <code>git config rename-section &lt;old-name&gt; &lt;new-name&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt---remove-sectionltnamegt"> <a class="anchor" href="#Documentation/git-config.txt---remove-sectionltnamegt"></a>--remove-section &lt;name&gt; </dt>
+<dd>
+<p>Replaced by <code>git config remove-section &lt;name&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt--e"> <a class="anchor" href="#Documentation/git-config.txt--e"></a>-e </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt---edit"> <a class="anchor" href="#Documentation/git-config.txt---edit"></a>--edit </dt>
+<dd>
+<p>Replaced by <code>git config edit</code>.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_configuration"><a class="anchor" href="#_configuration"></a>CONFIGURATION</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><code>pager.config</code> is only respected when listing configuration, i.e., when
+using <code>list</code> or <code>get</code> which may return multiple results. The default is to use
+a pager.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="FILES"><a class="anchor" href="#FILES"></a>FILES</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>By default, <em>git config</em> will read configuration options from multiple
+files:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-prefixetcgitconfig"> <a class="anchor" href="#Documentation/git-config.txt-prefixetcgitconfig"></a>$(prefix)/etc/gitconfig </dt>
+<dd>
+<p>System-wide configuration file.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-XDGCONFIGHOMEgitconfig"> <a class="anchor" href="#Documentation/git-config.txt-XDGCONFIGHOMEgitconfig"></a>$XDG_CONFIG_HOME/git/config </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitconfig"> <a class="anchor" href="#Documentation/git-config.txt-gitconfig"></a>~/.gitconfig </dt>
+<dd>
+<p>User-specific configuration files. When the XDG_CONFIG_HOME environment
+variable is not set or empty, $HOME/.config/ is used as
+$XDG_CONFIG_HOME.</p>
+<div class="paragraph">
+<p>These are also called "global" configuration files. If both files exist, both
+files are read in the order given above.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-GITDIRconfig"> <a class="anchor" href="#Documentation/git-config.txt-GITDIRconfig"></a>$GIT_DIR/config </dt>
+<dd>
+<p>Repository specific configuration file.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-GITDIRconfigworktree"> <a class="anchor" href="#Documentation/git-config.txt-GITDIRconfigworktree"></a>$GIT_DIR/config.worktree </dt>
+<dd>
+<p>This is optional and is only searched when
+<code>extensions.worktreeConfig</code> is present in $GIT_DIR/config.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>You may also provide additional configuration parameters when running any
+git command by using the <code>-c</code> option. See <a href='{{< relurl "docs/git" >}}'>git[1]</a> for details.</p>
+</div>
+<div class="paragraph">
+<p>Options will be read from all of these files that are available. If the
+global or the system-wide configuration files are missing or unreadable they
+will be ignored. If the repository configuration file is missing or unreadable,
+<em>git config</em> will exit with a non-zero error code. An error message is produced
+if the file is unreadable, but not if it is missing.</p>
+</div>
+<div class="paragraph">
+<p>The files are read in the order given above, with last value found taking
+precedence over values read earlier.  When multiple values are taken then all
+values of a key from all files will be used.</p>
+</div>
+<div class="paragraph">
+<p>By default, options are only written to the repository specific
+configuration file. Note that this also affects options like <code>set</code>
+and <code>unset</code>. <strong><em>git config</em> will only ever change one file at a time</strong>.</p>
+</div>
+<div class="paragraph">
+<p>You can limit which configuration sources are read from or written to by
+specifying the path of a file with the <code>--file</code> option, or by specifying a
+configuration scope with <code>--system</code>, <code>--global</code>, <code>--local</code>, or <code>--worktree</code>.
+For more, see <a href="#OPTIONS">OPTIONS</a> above.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="SCOPES"><a class="anchor" href="#SCOPES"></a>SCOPES</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Each configuration source falls within a configuration scope. The scopes
+are:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-system"> <a class="anchor" href="#Documentation/git-config.txt-system"></a>system </dt>
+<dd>
+<p>$(prefix)/etc/gitconfig</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-global"> <a class="anchor" href="#Documentation/git-config.txt-global"></a>global </dt>
+<dd>
+<p>$XDG_CONFIG_HOME/git/config</p>
+<div class="paragraph">
+<p>~/.gitconfig</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-local"> <a class="anchor" href="#Documentation/git-config.txt-local"></a>local </dt>
+<dd>
+<p>$GIT_DIR/config</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-worktree"> <a class="anchor" href="#Documentation/git-config.txt-worktree"></a>worktree </dt>
+<dd>
+<p>$GIT_DIR/config.worktree</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-command"> <a class="anchor" href="#Documentation/git-config.txt-command"></a>command </dt>
+<dd>
+<p>GIT_CONFIG_{COUNT,KEY,VALUE} environment variables (see <a href="#ENVIRONMENT">ENVIRONMENT</a>
+below)</p>
+<div class="paragraph">
+<p>the <code>-c</code> option</p>
+</div>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>With the exception of <em>command</em>, each scope corresponds to a command line
+option: <code>--system</code>, <code>--global</code>, <code>--local</code>, <code>--worktree</code>.</p>
+</div>
+<div class="paragraph">
+<p>When reading options, specifying a scope will only read options from the
+files within that scope. When writing options, specifying a scope will write
+to the files within that scope (instead of the repository specific
+configuration file). See <a href="#OPTIONS">OPTIONS</a> above for a complete description.</p>
+</div>
+<div class="paragraph">
+<p>Most configuration options are respected regardless of the scope it is
+defined in, but some options are only respected in certain scopes. See the
+respective option&#8217;s documentation for the full details.</p>
+</div>
+<div class="sect2">
+<h3 id="_protected_configuration"><a class="anchor" href="#_protected_configuration"></a>Protected configuration</h3>
+<div class="paragraph">
+<p>Protected configuration refers to the <em>system</em>, <em>global</em>, and <em>command</em> scopes.
+For security reasons, certain options are only respected when they are
+specified in protected configuration, and ignored otherwise.</p>
+</div>
+<div class="paragraph">
+<p>Git treats these scopes as if they are controlled by the user or a trusted
+administrator. This is because an attacker who controls these scopes can do
+substantial harm without using Git, so it is assumed that the user&#8217;s environment
+protects these scopes against attackers.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="ENVIRONMENT"><a class="anchor" href="#ENVIRONMENT"></a>ENVIRONMENT</h2>
+<div class="sectionbody">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-GITCONFIGGLOBAL"> <a class="anchor" href="#Documentation/git-config.txt-GITCONFIGGLOBAL"></a>GIT_CONFIG_GLOBAL </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-GITCONFIGSYSTEM"> <a class="anchor" href="#Documentation/git-config.txt-GITCONFIGSYSTEM"></a>GIT_CONFIG_SYSTEM </dt>
+<dd>
+<p>Take the configuration from the given files instead from global or
+system-level configuration. See <a href='{{< relurl "docs/git" >}}'>git[1]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-GITCONFIGNOSYSTEM"> <a class="anchor" href="#Documentation/git-config.txt-GITCONFIGNOSYSTEM"></a>GIT_CONFIG_NOSYSTEM </dt>
+<dd>
+<p>Whether to skip reading settings from the system-wide
+$(prefix)/etc/gitconfig file. See <a href='{{< relurl "docs/git" >}}'>git[1]</a> for details.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>See also <a href="#FILES">FILES</a>.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-GITCONFIGCOUNT"> <a class="anchor" href="#Documentation/git-config.txt-GITCONFIGCOUNT"></a>GIT_CONFIG_COUNT </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-GITCONFIGKEYltngt"> <a class="anchor" href="#Documentation/git-config.txt-GITCONFIGKEYltngt"></a>GIT_CONFIG_KEY_&lt;n&gt; </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-GITCONFIGVALUEltngt"> <a class="anchor" href="#Documentation/git-config.txt-GITCONFIGVALUEltngt"></a>GIT_CONFIG_VALUE_&lt;n&gt; </dt>
+<dd>
+<p>If GIT_CONFIG_COUNT is set to a positive number, all environment pairs
+GIT_CONFIG_KEY_&lt;n&gt; and GIT_CONFIG_VALUE_&lt;n&gt; up to that number will be
+added to the process&#8217;s runtime configuration. The config pairs are
+zero-indexed. Any missing key or value is treated as an error. An empty
+GIT_CONFIG_COUNT is treated the same as GIT_CONFIG_COUNT=0, namely no
+pairs are processed. These environment variables will override values
+in configuration files, but will be overridden by any explicit options
+passed via <code>git -c</code>.</p>
+<div class="paragraph">
+<p>This is useful for cases where you want to spawn multiple git commands
+with a common configuration but cannot depend on a configuration file,
+for example when writing scripts.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-GITCONFIG"> <a class="anchor" href="#Documentation/git-config.txt-GITCONFIG"></a>GIT_CONFIG </dt>
+<dd>
+<p>If no <code>--file</code> option is provided to <code>git config</code>, use the file
+given by <code>GIT_CONFIG</code> as if it were provided via <code>--file</code>. This
+variable has no effect on other Git commands, and is mostly for
+historical compatibility; there is generally no reason to use it
+instead of the <code>--file</code> option.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="EXAMPLES"><a class="anchor" href="#EXAMPLES"></a>EXAMPLES</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Given a .git/config like this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>#
+# This is the config file, and
+# a '#' or ';' character indicates
+# a comment
+#
+
+; core variables
+[core]
+	; Don't trust file modes
+	filemode = false
+
+; Our diff algorithm
+[diff]
+	external = /usr/local/bin/diff-wrapper
+	renames = true
+
+; Proxy settings
+[core]
+	gitproxy=proxy-command for kernel.org
+	gitproxy=default-proxy ; for all the rest
+
+; HTTP
+[http]
+	sslVerify
+[http "https://weak.example.com"]
+	sslVerify = false
+	cookieFile = /tmp/cookie.txt</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>you can set the filemode to true with</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config set core.filemode true</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The hypothetical proxy command entries actually have a postfix to discern
+what URL they apply to. Here is how to change the entry for kernel.org
+to "ssh".</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config set --value='for kernel.org$' core.gitproxy '"ssh" for kernel.org'</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>This makes sure that only the key/value pair for kernel.org is replaced.</p>
+</div>
+<div class="paragraph">
+<p>To delete the entry for renames, do</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config unset diff.renames</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>If you want to delete an entry for a multivar (like core.gitproxy above),
+you have to provide a regex matching the value of exactly one line.</p>
+</div>
+<div class="paragraph">
+<p>To query the value for a given key, do</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config get core.filemode</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>or, to query a multivar:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config get --value="for kernel.org$" core.gitproxy</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>If you want to know all the values for a multivar, do:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config get --all --show-names core.gitproxy</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>If you like to live dangerously, you can replace <strong>all</strong> core.gitproxy by a
+new one with</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config set --all core.gitproxy ssh</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>However, if you really only want to replace the line for the default proxy,
+i.e. the one without a "for &#8230;&#8203;" postfix, do something like this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config set --value='! for ' core.gitproxy ssh</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>To actually match only values with an exclamation mark, you have to</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config set --value='[!]' section.key value</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>To add a new proxy, without altering any of the existing ones, use</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config set --append core.gitproxy '"proxy-command" for example.com'</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>An example to use customized color from the configuration in your
+script:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>#!/bin/sh
+WS=$(git config get --type=color --default="blue reverse" color.diff.whitespace)
+RESET=$(git config get --type=color --default="reset" "")
+echo "${WS}your whitespace color or blue reverse${RESET}"</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>For URLs in <code>https://weak.example.com</code>, <code>http.sslVerify</code> is set to
+false, while it is set to <code>true</code> for all others:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>% git config get --type=bool --url=https://good.example.com http.sslverify
+true
+% git config get --type=bool --url=https://weak.example.com http.sslverify
+false
+% git config get --url=https://weak.example.com http
+http.cookieFile /tmp/cookie.txt
+http.sslverify false</pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_configuration_file"><a class="anchor" href="#_configuration_file"></a>CONFIGURATION FILE</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The Git configuration file contains a number of variables that affect
+the Git commands' behavior. The files <code>.git/config</code> and optionally
+<code>config.worktree</code> (see the "CONFIGURATION FILE" section of
+<a href='{{< relurl "docs/git-worktree" >}}'>git-worktree[1]</a>) in each repository are used to store the
+configuration for that repository, and <code>$HOME/.gitconfig</code> is used to
+store a per-user configuration as fallback values for the <code>.git/config</code>
+file. The file <code>/etc/gitconfig</code> can be used to store a system-wide
+default configuration.</p>
+</div>
+<div class="paragraph">
+<p>The configuration variables are used by both the Git plumbing
+and the porcelain commands. The variables are divided into sections, wherein
+the fully qualified variable name of the variable itself is the last
+dot-separated segment and the section name is everything before the last
+dot. The variable names are case-insensitive, allow only alphanumeric
+characters and <code>-</code>, and must start with an alphabetic character.  Some
+variables may appear multiple times; we say then that the variable is
+multivalued.</p>
+</div>
+<div class="sect2">
+<h3 id="_syntax"><a class="anchor" href="#_syntax"></a>Syntax</h3>
+<div class="paragraph">
+<p>The syntax is fairly flexible and permissive.  Whitespace characters,
+which in this context are the space character (SP) and the horizontal
+tabulation (HT), are mostly ignored.  The <em>#</em> and <em>;</em> characters begin
+comments to the end of line.  Blank lines are ignored.</p>
+</div>
+<div class="paragraph">
+<p>The file consists of sections and variables.  A section begins with
+the name of the section in square brackets and continues until the next
+section begins.  Section names are case-insensitive.  Only alphanumeric
+characters, <code>-</code> and <code>.</code> are allowed in section names.  Each variable
+must belong to some section, which means that there must be a section
+header before the first setting of a variable.</p>
+</div>
+<div class="paragraph">
+<p>Sections can be further divided into subsections.  To begin a subsection
+put its name in double quotes, separated by space from the section name,
+in the section header, like in the example below:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	[section "subsection"]</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Subsection names are case sensitive and can contain any characters except
+newline and the null byte. Doublequote <code>"</code> and backslash can be included
+by escaping them as <code>\"</code> and <code>\\</code>, respectively. Backslashes preceding
+other characters are dropped when reading; for example, <code>\t</code> is read as
+<code>t</code> and <code>\0</code> is read as <code>0</code>. Section headers cannot span multiple lines.
+Variables may belong directly to a section or to a given subsection. You
+can have <code>[section]</code> if you have <code>[section "subsection"]</code>, but you don&#8217;t
+need to.</p>
+</div>
+<div class="paragraph">
+<p>There is also a deprecated <code>[section.subsection]</code> syntax. With this
+syntax, the subsection name is converted to lower-case and is also
+compared case sensitively. These subsection names follow the same
+restrictions as section names.</p>
+</div>
+<div class="paragraph">
+<p>All the other lines (and the remainder of the line after the section
+header) are recognized as setting variables, in the form
+<em>name = value</em> (or just <em>name</em>, which is a short-hand to say that
+the variable is the boolean "true").
+The variable names are case-insensitive, allow only alphanumeric characters
+and <code>-</code>, and must start with an alphabetic character.</p>
+</div>
+<div class="paragraph">
+<p>Whitespace characters surrounding <code>name</code>, <code>=</code> and <code>value</code> are discarded.
+Internal whitespace characters within <em>value</em> are retained verbatim.
+Comments starting with either <code>#</code> or <code>;</code> and extending to the end of line
+are discarded.  A line that defines a value can be continued to the next
+line by ending it with a backslash (<code>\</code>);  the backslash and the end-of-line
+characters are discarded.</p>
+</div>
+<div class="paragraph">
+<p>If <code>value</code> needs to contain leading or trailing whitespace characters,
+it must be enclosed in double quotation marks (<code>"</code>).  Inside double quotation
+marks, double quote (<code>"</code>) and backslash (<code>\</code>) characters must be escaped:
+use <code>\"</code> for <code>"</code> and <code>\\</code> for <code>\</code>.</p>
+</div>
+<div class="paragraph">
+<p>The following escape sequences (beside <code>\"</code> and <code>\\</code>) are recognized:
+<code>\n</code> for newline character (NL), <code>\t</code> for horizontal tabulation (HT, TAB)
+and <code>\b</code> for backspace (BS).  Other char escape sequences (including octal
+escape sequences) are invalid.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_includes"><a class="anchor" href="#_includes"></a>Includes</h3>
+<div class="paragraph">
+<p>The <code>include</code> and <code>includeIf</code> sections allow you to include config
+directives from another source. These sections behave identically to
+each other with the exception that <code>includeIf</code> sections may be ignored
+if their condition does not evaluate to true; see "Conditional includes"
+below.</p>
+</div>
+<div class="paragraph">
+<p>You can include a config file from another by setting the special
+<code>include.path</code> (or <code>includeIf.*.path</code>) variable to the name of the file
+to be included. The variable takes a pathname as its value, and is
+subject to tilde expansion. These variables can be given multiple times.</p>
+</div>
+<div class="paragraph">
+<p>The contents of the included file are inserted immediately, as if they
+had been found at the location of the include directive. If the value of the
+variable is a relative path, the path is considered to
+be relative to the configuration file in which the include directive
+was found.  See below for examples.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_conditional_includes"><a class="anchor" href="#_conditional_includes"></a>Conditional includes</h3>
+<div class="paragraph">
+<p>You can conditionally include a config file from another by setting an
+<code>includeIf.&lt;condition&gt;.path</code> variable to the name of the file to be
+included.</p>
+</div>
+<div class="paragraph">
+<p>The condition starts with a keyword followed by a colon and some data
+whose format and meaning depends on the keyword. Supported keywords
+are:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-codegitdircode"> <a class="anchor" href="#Documentation/git-config.txt-codegitdircode"></a><code>gitdir</code> </dt>
+<dd>
+<p>The data that follows the keyword <code>gitdir:</code> is used as a glob
+pattern. If the location of the .git directory matches the
+pattern, the include condition is met.</p>
+<div class="paragraph">
+<p>The .git location may be auto-discovered, or come from <code>$GIT_DIR</code>
+environment variable. If the repository is auto-discovered via a .git
+file (e.g. from submodules, or a linked worktree), the .git location
+would be the final location where the .git directory is, not where the
+.git file is.</p>
+</div>
+<div class="paragraph">
+<p>The pattern can contain standard globbing wildcards and two additional
+ones, <code>**/</code> and <code>/**</code>, that can match multiple path components. Please
+refer to <a href='{{< relurl "docs/gitignore" >}}'>gitignore[5]</a> for details. For convenience:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>If the pattern starts with <code>~/</code>, <code>~</code> will be substituted with the
+content of the environment variable <code>HOME</code>.</p>
+</li>
+<li>
+<p>If the pattern starts with <code>./</code>, it is replaced with the directory
+containing the current config file.</p>
+</li>
+<li>
+<p>If the pattern does not start with either <code>~/</code>, <code>./</code> or <code>/</code>, <code>**/</code>
+will be automatically prepended. For example, the pattern <code>foo/bar</code>
+becomes <code>**/foo/bar</code> and would match <code>/any/path/to/foo/bar</code>.</p>
+</li>
+<li>
+<p>If the pattern ends with <code>/</code>, <code>**</code> will be automatically added. For
+example, the pattern <code>foo/</code> becomes <code>foo/**</code>. In other words, it
+matches "foo" and everything inside, recursively.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codegitdiricode"> <a class="anchor" href="#Documentation/git-config.txt-codegitdiricode"></a><code>gitdir/i</code> </dt>
+<dd>
+<p>This is the same as <code>gitdir</code> except that matching is done
+case-insensitively (e.g. on case-insensitive file systems)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeonbranchcode"> <a class="anchor" href="#Documentation/git-config.txt-codeonbranchcode"></a><code>onbranch</code> </dt>
+<dd>
+<p>The data that follows the keyword <code>onbranch:</code> is taken to be a
+pattern with standard globbing wildcards and two additional
+ones, <code>**/</code> and <code>/**</code>, that can match multiple path components.
+If we are in a worktree where the name of the branch that is
+currently checked out matches the pattern, the include condition
+is met.</p>
+<div class="paragraph">
+<p>If the pattern ends with <code>/</code>, <code>**</code> will be automatically added. For
+example, the pattern <code>foo/</code> becomes <code>foo/**</code>. In other words, it matches
+all branches that begin with <code>foo/</code>. This is useful if your branches are
+organized hierarchically and you would like to apply a configuration to
+all the branches in that hierarchy.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codehasconfigremoteurlcode"> <a class="anchor" href="#Documentation/git-config.txt-codehasconfigremoteurlcode"></a><code>hasconfig:remote.*.url:</code> </dt>
+<dd>
+<p>The data that follows this keyword is taken to
+be a pattern with standard globbing wildcards and two
+additional ones, <code>**/</code> and <code>/**</code>, that can match multiple
+components. The first time this keyword is seen, the rest of
+the config files will be scanned for remote URLs (without
+applying any values). If there exists at least one remote URL
+that matches this pattern, the include condition is met.</p>
+<div class="paragraph">
+<p>Files included by this option (directly or indirectly) are not allowed
+to contain remote URLs.</p>
+</div>
+<div class="paragraph">
+<p>Note that unlike other includeIf conditions, resolving this condition
+relies on information that is not yet known at the point of reading the
+condition. A typical use case is this option being present as a
+system-level or global-level config, and the remote URL being in a
+local-level config; hence the need to scan ahead when resolving this
+condition. In order to avoid the chicken-and-egg problem in which
+potentially-included files can affect whether such files are potentially
+included, Git breaks the cycle by prohibiting these files from affecting
+the resolution of these conditions (thus, prohibiting them from
+declaring remote URLs).</p>
+</div>
+<div class="paragraph">
+<p>As for the naming of this keyword, it is for forwards compatibility with
+a naming scheme that supports more variable-based include conditions,
+but currently Git only supports the exact keyword described above.</p>
+</div>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>A few more notes on matching via <code>gitdir</code> and <code>gitdir/i</code>:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Symlinks in <code>$GIT_DIR</code> are not resolved before matching.</p>
+</li>
+<li>
+<p>Both the symlink &amp; realpath versions of paths will be matched
+outside of <code>$GIT_DIR</code>. E.g. if ~/git is a symlink to
+/mnt/storage/git, both <code>gitdir:~/git</code> and <code>gitdir:/mnt/storage/git</code>
+will match.</p>
+<div class="paragraph">
+<p>This was not the case in the initial release of this feature in
+v2.13.0, which only matched the realpath version. Configuration that
+wants to be compatible with the initial release of this feature needs
+to either specify only the realpath version, or both versions.</p>
+</div>
+</li>
+<li>
+<p>Note that "../" is not special and will match literally, which is
+unlikely what you want.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_example"><a class="anchor" href="#_example"></a>Example</h3>
+<div class="listingblock">
+<div class="content">
+<pre># Core variables
+[core]
+	; Don't trust file modes
+	filemode = false
+
+# Our diff algorithm
+[diff]
+	external = /usr/local/bin/diff-wrapper
+	renames = true
+
+[branch "devel"]
+	remote = origin
+	merge = refs/heads/devel
+
+# Proxy settings
+[core]
+	gitProxy="ssh" for "kernel.org"
+	gitProxy=default-proxy ; for the rest
+
+[include]
+	path = /path/to/foo.inc ; include by absolute path
+	path = foo.inc ; find "foo.inc" relative to the current file
+	path = ~/foo.inc ; find "foo.inc" in your `$HOME` directory
+
+; include if $GIT_DIR is /path/to/foo/.git
+[includeIf "gitdir:/path/to/foo/.git"]
+	path = /path/to/foo.inc
+
+; include for all repositories inside /path/to/group
+[includeIf "gitdir:/path/to/group/"]
+	path = /path/to/foo.inc
+
+; include for all repositories inside $HOME/to/group
+[includeIf "gitdir:~/to/group/"]
+	path = /path/to/foo.inc
+
+; relative paths are always relative to the including
+; file (if the condition is true); their location is not
+; affected by the condition
+[includeIf "gitdir:/path/to/group/"]
+	path = foo.inc
+
+; include only if we are in a worktree where foo-branch is
+; currently checked out
+[includeIf "onbranch:foo-branch"]
+	path = foo.inc
+
+; include only if a remote with the given URL exists (note
+; that such a URL may be provided later in a file or in a
+; file read after this file is read, as seen in this example)
+[includeIf "hasconfig:remote.*.url:https://example.com/**"]
+	path = foo.inc
+[remote "origin"]
+	url = https://example.com/git</pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_values"><a class="anchor" href="#_values"></a>Values</h3>
+<div class="paragraph">
+<p>Values of many variables are treated as a simple string, but there
+are variables that take values of specific types and there are rules
+as to how to spell them.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-boolean"> <a class="anchor" href="#Documentation/git-config.txt-boolean"></a>boolean </dt>
+<dd>
+<p>When a variable is said to take a boolean value, many
+synonyms are accepted for <em>true</em> and <em>false</em>; these are all
+case-insensitive.</p>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-true"> <a class="anchor" href="#Documentation/git-config.txt-true"></a>true </dt>
+<dd>
+<p>Boolean true literals are <code>yes</code>, <code>on</code>, <code>true</code>,
+and <code>1</code>.  Also, a variable defined without <code>= &lt;value&gt;</code>
+is taken as true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-false"> <a class="anchor" href="#Documentation/git-config.txt-false"></a>false </dt>
+<dd>
+<p>Boolean false literals are <code>no</code>, <code>off</code>, <code>false</code>,
+<code>0</code> and the empty string.</p>
+<div class="paragraph">
+<p>When converting a value to its canonical form using the <code>--type=bool</code> type
+specifier, <em>git config</em> will ensure that the output is "true" or
+"false" (spelled in lowercase).</p>
+</div>
+</dd>
+</dl>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-integer"> <a class="anchor" href="#Documentation/git-config.txt-integer"></a>integer </dt>
+<dd>
+<p>The value for many variables that specify various sizes can
+be suffixed with <code>k</code>, <code>M</code>,&#8230;&#8203; to mean "scale the number by
+1024", "by 1024x1024", etc.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-color"> <a class="anchor" href="#Documentation/git-config.txt-color"></a>color </dt>
+<dd>
+<p>The value for a variable that takes a color is a list of
+colors (at most two, one for foreground and one for background)
+and attributes (as many as you want), separated by spaces.</p>
+<div class="paragraph">
+<p>The basic colors accepted are <code>normal</code>, <code>black</code>, <code>red</code>, <code>green</code>,
+<code>yellow</code>, <code>blue</code>, <code>magenta</code>, <code>cyan</code>, <code>white</code> and <code>default</code>.  The first
+color given is the foreground; the second is the background.  All the
+basic colors except <code>normal</code> and <code>default</code> have a bright variant that can
+be specified by prefixing the color with <code>bright</code>, like <code>brightred</code>.</p>
+</div>
+<div class="paragraph">
+<p>The color <code>normal</code> makes no change to the color. It is the same as an
+empty string, but can be used as the foreground color when specifying a
+background color alone (for example, "normal red").</p>
+</div>
+<div class="paragraph">
+<p>The color <code>default</code> explicitly resets the color to the terminal default,
+for example to specify a cleared background. Although it varies between
+terminals, this is usually not the same as setting to "white black".</p>
+</div>
+<div class="paragraph">
+<p>Colors may also be given as numbers between 0 and 255; these use ANSI
+256-color mode (but note that not all terminals may support this).  If
+your terminal supports it, you may also specify 24-bit RGB values as
+hex, like <code>#ff0ab3</code>, or 12-bit RGB values like <code>#f1b</code>, which is
+equivalent to the 24-bit color <code>#ff11bb</code>.</p>
+</div>
+<div class="paragraph">
+<p>The accepted attributes are <code>bold</code>, <code>dim</code>, <code>ul</code>, <code>blink</code>, <code>reverse</code>,
+<code>italic</code>, and <code>strike</code> (for crossed-out or "strikethrough" letters).
+The position of any attributes with respect to the colors
+(before, after, or in between), doesn&#8217;t matter. Specific attributes may
+be turned off by prefixing them with <code>no</code> or <code>no-</code> (e.g., <code>noreverse</code>,
+<code>no-ul</code>, etc).</p>
+</div>
+<div class="paragraph">
+<p>The pseudo-attribute <code>reset</code> resets all colors and attributes before
+applying the specified coloring. For example, <code>reset green</code> will result
+in a green foreground and default background without any active
+attributes.</p>
+</div>
+<div class="paragraph">
+<p>An empty color string produces no color effect at all. This can be used
+to avoid coloring specific elements without disabling color entirely.</p>
+</div>
+<div class="paragraph">
+<p>For git&#8217;s pre-defined color slots, the attributes are meant to be reset
+at the beginning of each item in the colored output. So setting
+<code>color.decorate.branch</code> to <code>black</code> will paint that branch name in a
+plain <code>black</code>, even if the previous thing on the same output line (e.g.
+opening parenthesis before the list of branch names in <code>log --decorate</code>
+output) is set to be painted with <code>bold</code> or some other attribute.
+However, custom log formats may do more complicated and layered
+coloring, and the negated forms may be useful there.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pathname"> <a class="anchor" href="#Documentation/git-config.txt-pathname"></a>pathname </dt>
+<dd>
+<p>A variable that takes a pathname value can be given a
+string that begins with "<code>~/</code>" or "<code>~user/</code>", and the usual
+tilde expansion happens to such a string: <code>~/</code>
+is expanded to the value of <code>$HOME</code>, and <code>~user/</code> to the
+specified user&#8217;s home directory.</p>
+<div class="paragraph">
+<p>If a path starts with <code>%(prefix)/</code>, the remainder is interpreted as a
+path relative to Git&#8217;s "runtime prefix", i.e. relative to the location
+where Git itself was installed. For example, <code>%(prefix)/bin/</code> refers to
+the directory in which the Git executable itself lives. If Git was
+compiled without runtime prefix support, the compiled-in prefix will be
+substituted instead. In the unlikely event that a literal path needs to
+be specified that should <em>not</em> be expanded, it needs to be prefixed by
+<code>./</code>, like so: <code>./%(prefix)/bin</code>.</p>
+</div>
+</dd>
+</dl>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_variables"><a class="anchor" href="#_variables"></a>Variables</h3>
+<div class="paragraph">
+<p>Note that this list is non-comprehensive and not necessarily complete.
+For command-specific variables, you will find a more detailed description
+in the appropriate manual page.</p>
+</div>
+<div class="paragraph">
+<p>Other git-related tools may and do use their own variables.  When
+inventing new variables for use in your own tool, make sure their
+names do not conflict with those that are used by Git itself and
+other popular tools, and describe them in your documentation.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-addignoreErrors"> <a class="anchor" href="#Documentation/git-config.txt-addignoreErrors"></a>add.ignoreErrors </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-addignore-errorsdeprecated"> <a class="anchor" href="#Documentation/git-config.txt-addignore-errorsdeprecated"></a>add.ignore-errors (deprecated) </dt>
+<dd>
+<p>Tells <em>git add</em> to continue adding files when some files cannot be
+added due to indexing errors. Equivalent to the <code>--ignore-errors</code>
+option of <a href='{{< relurl "docs/git-add" >}}'>git-add[1]</a>.  <code>add.ignore-errors</code> is deprecated,
+as it does not follow the usual naming convention for configuration
+variables.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-advice"> <a class="anchor" href="#Documentation/git-config.txt-advice"></a>advice.* </dt>
+<dd>
+<p>These variables control various optional help messages designed to
+aid new users.  When left unconfigured, Git will give the message
+alongside instructions on how to squelch it.  You can tell Git
+that you do not need the help message by setting these to <code>false</code>:</p>
+<div class="openblock">
+<div class="content">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-addEmbeddedRepo"> <a class="anchor" href="#Documentation/git-config.txt-addEmbeddedRepo"></a>addEmbeddedRepo </dt>
+<dd>
+<p>Shown when the user accidentally adds one
+git repo inside of another.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-addEmptyPathspec"> <a class="anchor" href="#Documentation/git-config.txt-addEmptyPathspec"></a>addEmptyPathspec </dt>
+<dd>
+<p>Shown when the user runs <code>git add</code> without providing
+the pathspec parameter.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-addIgnoredFile"> <a class="anchor" href="#Documentation/git-config.txt-addIgnoredFile"></a>addIgnoredFile </dt>
+<dd>
+<p>Shown when the user attempts to add an ignored file to
+the index.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-amWorkDir"> <a class="anchor" href="#Documentation/git-config.txt-amWorkDir"></a>amWorkDir </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-am" >}}'>git-am[1]</a> fails to apply a patch
+file, to tell the user the location of the file.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-ambiguousFetchRefspec"> <a class="anchor" href="#Documentation/git-config.txt-ambiguousFetchRefspec"></a>ambiguousFetchRefspec </dt>
+<dd>
+<p>Shown when a fetch refspec for multiple remotes maps to
+the same remote-tracking branch namespace and causes branch
+tracking set-up to fail.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-checkoutAmbiguousRemoteBranchName"> <a class="anchor" href="#Documentation/git-config.txt-checkoutAmbiguousRemoteBranchName"></a>checkoutAmbiguousRemoteBranchName </dt>
+<dd>
+<p>Shown when the argument to
+<a href='{{< relurl "docs/git-checkout" >}}'>git-checkout[1]</a> and <a href='{{< relurl "docs/git-switch" >}}'>git-switch[1]</a>
+ambiguously resolves to a
+remote tracking branch on more than one remote in
+situations where an unambiguous argument would have
+otherwise caused a remote-tracking branch to be
+checked out. See the <code>checkout.defaultRemote</code>
+configuration variable for how to set a given remote
+to be used by default in some situations where this
+advice would be printed.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-commitBeforeMerge"> <a class="anchor" href="#Documentation/git-config.txt-commitBeforeMerge"></a>commitBeforeMerge </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-merge" >}}'>git-merge[1]</a> refuses to
+merge to avoid overwriting local changes.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-detachedHead"> <a class="anchor" href="#Documentation/git-config.txt-detachedHead"></a>detachedHead </dt>
+<dd>
+<p>Shown when the user uses
+<a href='{{< relurl "docs/git-switch" >}}'>git-switch[1]</a> or <a href='{{< relurl "docs/git-checkout" >}}'>git-checkout[1]</a>
+to move to the detached HEAD state, to tell the user how
+to create a local branch after the fact.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diverging"> <a class="anchor" href="#Documentation/git-config.txt-diverging"></a>diverging </dt>
+<dd>
+<p>Shown when a fast-forward is not possible.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchShowForcedUpdates"> <a class="anchor" href="#Documentation/git-config.txt-fetchShowForcedUpdates"></a>fetchShowForcedUpdates </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> takes a long time
+to calculate forced updates after ref updates, or to warn
+that the check is disabled.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-forceDeleteBranch"> <a class="anchor" href="#Documentation/git-config.txt-forceDeleteBranch"></a>forceDeleteBranch </dt>
+<dd>
+<p>Shown when the user tries to delete a not fully merged
+branch without the force option set.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-ignoredHook"> <a class="anchor" href="#Documentation/git-config.txt-ignoredHook"></a>ignoredHook </dt>
+<dd>
+<p>Shown when a hook is ignored because the hook is not
+set as executable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-implicitIdentity"> <a class="anchor" href="#Documentation/git-config.txt-implicitIdentity"></a>implicitIdentity </dt>
+<dd>
+<p>Shown when the user&#8217;s information is guessed from the
+system username and domain name, to tell the user how to
+set their identity configuration.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergeConflict"> <a class="anchor" href="#Documentation/git-config.txt-mergeConflict"></a>mergeConflict </dt>
+<dd>
+<p>Shown when various commands stop because of conflicts.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-nestedTag"> <a class="anchor" href="#Documentation/git-config.txt-nestedTag"></a>nestedTag </dt>
+<dd>
+<p>Shown when a user attempts to recursively tag a tag object.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushAlreadyExists"> <a class="anchor" href="#Documentation/git-config.txt-pushAlreadyExists"></a>pushAlreadyExists </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a> rejects an update that
+does not qualify for fast-forwarding (e.g., a tag.)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushFetchFirst"> <a class="anchor" href="#Documentation/git-config.txt-pushFetchFirst"></a>pushFetchFirst </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a> rejects an update that
+tries to overwrite a remote ref that points at an
+object we do not have.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushNeedsForce"> <a class="anchor" href="#Documentation/git-config.txt-pushNeedsForce"></a>pushNeedsForce </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a> rejects an update that
+tries to overwrite a remote ref that points at an
+object that is not a commit-ish, or make the remote
+ref point at an object that is not a commit-ish.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushNonFFCurrent"> <a class="anchor" href="#Documentation/git-config.txt-pushNonFFCurrent"></a>pushNonFFCurrent </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a> fails due to a
+non-fast-forward update to the current branch.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushNonFFMatching"> <a class="anchor" href="#Documentation/git-config.txt-pushNonFFMatching"></a>pushNonFFMatching </dt>
+<dd>
+<p>Shown when the user ran <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a> and pushed
+"matching refs" explicitly (i.e. used <code>:</code>, or
+specified a refspec that isn&#8217;t the current branch) and
+it resulted in a non-fast-forward error.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushRefNeedsUpdate"> <a class="anchor" href="#Documentation/git-config.txt-pushRefNeedsUpdate"></a>pushRefNeedsUpdate </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a> rejects a forced update of
+a branch when its remote-tracking ref has updates that we
+do not have locally.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushUnqualifiedRefname"> <a class="anchor" href="#Documentation/git-config.txt-pushUnqualifiedRefname"></a>pushUnqualifiedRefname </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a> gives up trying to
+guess based on the source and destination refs what
+remote ref namespace the source belongs in, but where
+we can still suggest that the user push to either
+<code>refs/heads/*</code> or <code>refs/tags/*</code> based on the type of the
+source object.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushUpdateRejected"> <a class="anchor" href="#Documentation/git-config.txt-pushUpdateRejected"></a>pushUpdateRejected </dt>
+<dd>
+<p>Set this variable to <code>false</code> if you want to disable
+<code>pushNonFFCurrent</code>, <code>pushNonFFMatching</code>, <code>pushAlreadyExists</code>,
+<code>pushFetchFirst</code>, <code>pushNeedsForce</code>, and <code>pushRefNeedsUpdate</code>
+simultaneously.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebaseTodoError"> <a class="anchor" href="#Documentation/git-config.txt-rebaseTodoError"></a>rebaseTodoError </dt>
+<dd>
+<p>Shown when there is an error after editing the rebase todo list.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-refSyntax"> <a class="anchor" href="#Documentation/git-config.txt-refSyntax"></a>refSyntax </dt>
+<dd>
+<p>Shown when the user provides an illegal ref name, to
+tell the user about the ref syntax documentation.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-resetNoRefresh"> <a class="anchor" href="#Documentation/git-config.txt-resetNoRefresh"></a>resetNoRefresh </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-reset" >}}'>git-reset[1]</a> takes more than 2
+seconds to refresh the index after reset, to tell the user
+that they can use the <code>--no-refresh</code> option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-resolveConflict"> <a class="anchor" href="#Documentation/git-config.txt-resolveConflict"></a>resolveConflict </dt>
+<dd>
+<p>Shown by various commands when conflicts
+prevent the operation from being performed.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rmHints"> <a class="anchor" href="#Documentation/git-config.txt-rmHints"></a>rmHints </dt>
+<dd>
+<p>Shown on failure in the output of <a href='{{< relurl "docs/git-rm" >}}'>git-rm[1]</a>, to
+give directions on how to proceed from the current state.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sequencerInUse"> <a class="anchor" href="#Documentation/git-config.txt-sequencerInUse"></a>sequencerInUse </dt>
+<dd>
+<p>Shown when a sequencer command is already in progress.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-skippedCherryPicks"> <a class="anchor" href="#Documentation/git-config.txt-skippedCherryPicks"></a>skippedCherryPicks </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-rebase" >}}'>git-rebase[1]</a> skips a commit that has already
+been cherry-picked onto the upstream branch.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sparseIndexExpanded"> <a class="anchor" href="#Documentation/git-config.txt-sparseIndexExpanded"></a>sparseIndexExpanded </dt>
+<dd>
+<p>Shown when a sparse index is expanded to a full index, which is likely
+due to an unexpected set of files existing outside of the
+sparse-checkout.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusAheadBehind"> <a class="anchor" href="#Documentation/git-config.txt-statusAheadBehind"></a>statusAheadBehind </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> computes the ahead/behind
+counts for a local ref compared to its remote tracking ref,
+and that calculation takes longer than expected. Will not
+appear if <code>status.aheadBehind</code> is false or the option
+<code>--no-ahead-behind</code> is given.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusHints"> <a class="anchor" href="#Documentation/git-config.txt-statusHints"></a>statusHints </dt>
+<dd>
+<p>Show directions on how to proceed from the current
+state in the output of <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a>, in
+the template shown when writing commit messages in
+<a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a>, and in the help message shown
+by <a href='{{< relurl "docs/git-switch" >}}'>git-switch[1]</a> or
+<a href='{{< relurl "docs/git-checkout" >}}'>git-checkout[1]</a> when switching branches.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusUoption"> <a class="anchor" href="#Documentation/git-config.txt-statusUoption"></a>statusUoption </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> takes more than 2
+seconds to enumerate untracked files, to tell the user that
+they can use the <code>-u</code> option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submoduleAlternateErrorStrategyDie"> <a class="anchor" href="#Documentation/git-config.txt-submoduleAlternateErrorStrategyDie"></a>submoduleAlternateErrorStrategyDie </dt>
+<dd>
+<p>Shown when a submodule.alternateErrorStrategy option
+configured to "die" causes a fatal error.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submoduleMergeConflict"> <a class="anchor" href="#Documentation/git-config.txt-submoduleMergeConflict"></a>submoduleMergeConflict </dt>
+<dd>
+<p>Advice shown when a non-trivial submodule merge conflict is
+encountered.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submodulesNotUpdated"> <a class="anchor" href="#Documentation/git-config.txt-submodulesNotUpdated"></a>submodulesNotUpdated </dt>
+<dd>
+<p>Shown when a user runs a submodule command that fails
+because <code>git submodule update --init</code> was not run.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-suggestDetachingHead"> <a class="anchor" href="#Documentation/git-config.txt-suggestDetachingHead"></a>suggestDetachingHead </dt>
+<dd>
+<p>Shown when <a href='{{< relurl "docs/git-switch" >}}'>git-switch[1]</a> refuses to detach HEAD
+without the explicit <code>--detach</code> option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-updateSparsePath"> <a class="anchor" href="#Documentation/git-config.txt-updateSparsePath"></a>updateSparsePath </dt>
+<dd>
+<p>Shown when either <a href='{{< relurl "docs/git-add" >}}'>git-add[1]</a> or <a href='{{< relurl "docs/git-rm" >}}'>git-rm[1]</a>
+is asked to update index entries outside the current sparse
+checkout.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-waitingForEditor"> <a class="anchor" href="#Documentation/git-config.txt-waitingForEditor"></a>waitingForEditor </dt>
+<dd>
+<p>Shown when Git is waiting for editor input. Relevant
+when e.g. the editor is not launched inside the terminal.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-worktreeAddOrphan"> <a class="anchor" href="#Documentation/git-config.txt-worktreeAddOrphan"></a>worktreeAddOrphan </dt>
+<dd>
+<p>Shown when the user tries to create a worktree from an
+invalid reference, to tell the user how to create a new unborn
+branch instead.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-alias"> <a class="anchor" href="#Documentation/git-config.txt-alias"></a>alias.* </dt>
+<dd>
+<p>Command aliases for the <a href='{{< relurl "docs/git" >}}'>git[1]</a> command wrapper - e.g.
+after defining <code>alias.last = cat-file commit HEAD</code>, the invocation
+<code>git last</code> is equivalent to <code>git cat-file commit HEAD</code>. To avoid
+confusion and troubles with script usage, aliases that
+hide existing Git commands are ignored. Arguments are split by
+spaces, the usual shell quoting and escaping are supported.
+A quote pair or a backslash can be used to quote them.</p>
+<div class="paragraph">
+<p>Note that the first word of an alias does not necessarily have to be a
+command. It can be a command-line option that will be passed into the
+invocation of <code>git</code>. In particular, this is useful when used with <code>-c</code>
+to pass in one-time configurations or <code>-p</code> to force pagination. For example,
+<code>loud-rebase = -c commit.verbose=true rebase</code> can be defined such that
+running <code>git loud-rebase</code> would be equivalent to
+<code>git -c commit.verbose=true rebase</code>. Also, <code>ps = -p status</code> would be a
+helpful alias since <code>git ps</code> would paginate the output of <code>git status</code>
+where the original command does not.</p>
+</div>
+<div class="paragraph">
+<p>If the alias expansion is prefixed with an exclamation point,
+it will be treated as a shell command.  For example, defining
+<code>alias.new = !gitk --all --not ORIG_HEAD</code>, the invocation
+<code>git new</code> is equivalent to running the shell command
+<code>gitk --all --not ORIG_HEAD</code>.  Note:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Shell commands will be executed from the top-level directory of a
+repository, which may not necessarily be the current directory.</p>
+</li>
+<li>
+<p><code>GIT_PREFIX</code> is set as returned by running <code>git rev-parse --show-prefix</code>
+from the original current directory. See <a href='{{< relurl "docs/git-rev-parse" >}}'>git-rev-parse[1]</a>.</p>
+</li>
+<li>
+<p>Shell command aliases always receive any extra arguments provided to
+the Git command-line as positional arguments.</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Care should be taken if your shell alias is a "one-liner" script
+with multiple commands (e.g. in a pipeline), references multiple
+arguments, or is otherwise not able to handle positional arguments
+added at the end.  For example: <code>alias.cmd = "!echo $1 | grep $2"</code>
+called as <code>git cmd 1 2</code> will be executed as <em>echo $1 | grep $2
+1 2</em>, which is not what you want.</p>
+</li>
+<li>
+<p>A convenient way to deal with this is to write your script
+operations in an inline function that is then called with any
+arguments from the command-line.  For example `alias.cmd = "!c() {
+echo $1 | grep $2 ; }; c" will correctly execute the prior example.</p>
+</li>
+<li>
+<p>Setting <code>GIT_TRACE=1</code> can help you debug the command being run for
+your alias.</p>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-amkeepcr"> <a class="anchor" href="#Documentation/git-config.txt-amkeepcr"></a>am.keepcr </dt>
+<dd>
+<p>If true, git-am will call git-mailsplit for patches in mbox format
+with parameter <code>--keep-cr</code>. In this case git-mailsplit will
+not remove <code>\r</code> from lines ending with <code>\r\n</code>. Can be overridden
+by giving <code>--no-keep-cr</code> from the command line.
+See <a href='{{< relurl "docs/git-am" >}}'>git-am[1]</a>, <a href='{{< relurl "docs/git-mailsplit" >}}'>git-mailsplit[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-amthreeWay"> <a class="anchor" href="#Documentation/git-config.txt-amthreeWay"></a>am.threeWay </dt>
+<dd>
+<p>By default, <code>git am</code> will fail if the patch does not apply cleanly. When
+set to true, this setting tells <code>git am</code> to fall back on 3-way merge if
+the patch records the identity of blobs it is supposed to apply to and
+we have those blobs available locally (equivalent to giving the <code>--3way</code>
+option from the command line). Defaults to <code>false</code>.
+See <a href='{{< relurl "docs/git-am" >}}'>git-am[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-applyignoreWhitespace"> <a class="anchor" href="#Documentation/git-config.txt-applyignoreWhitespace"></a>apply.ignoreWhitespace </dt>
+<dd>
+<p>When set to <em>change</em>, tells <em>git apply</em> to ignore changes in
+whitespace, in the same way as the <code>--ignore-space-change</code>
+option.
+When set to one of: no, none, never, false, it tells <em>git apply</em> to
+respect all whitespace differences.
+See <a href='{{< relurl "docs/git-apply" >}}'>git-apply[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-applywhitespace"> <a class="anchor" href="#Documentation/git-config.txt-applywhitespace"></a>apply.whitespace </dt>
+<dd>
+<p>Tells <em>git apply</em> how to handle whitespace, in the same way
+as the <code>--whitespace</code> option. See <a href='{{< relurl "docs/git-apply" >}}'>git-apply[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-attrtree"> <a class="anchor" href="#Documentation/git-config.txt-attrtree"></a>attr.tree </dt>
+<dd>
+<p>A reference to a tree in the repository from which to read attributes,
+instead of the <code>.gitattributes</code> file in the working tree. If the value
+does not resolve to a valid tree object, an empty tree is used instead.
+When the <code>GIT_ATTR_SOURCE</code> environment variable or <code>--attr-source</code>
+command line option are used, this configuration variable has no effect.</p>
+</dd>
+</dl>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+The configuration options in <code>bitmapPseudoMerge.*</code> are considered
+EXPERIMENTAL and may be subject to change or be removed entirely in the
+future. For more information about the pseudo-merge bitmap feature, see
+the "Pseudo-merge bitmaps" section of <a href='{{< relurl "docs/gitpacking" >}}'>gitpacking[7]</a>.
+</td>
+</tr>
+</table>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-bitmapPseudoMergeltnamegtpattern"> <a class="anchor" href="#Documentation/git-config.txt-bitmapPseudoMergeltnamegtpattern"></a>bitmapPseudoMerge.&lt;name&gt;.pattern </dt>
+<dd>
+<p>Regular expression used to match reference names. Commits
+pointed to by references matching this pattern (and meeting
+the below criteria, like <code>bitmapPseudoMerge.&lt;name&gt;.sampleRate</code>
+and <code>bitmapPseudoMerge.&lt;name&gt;.threshold</code>) will be considered
+for inclusion in a pseudo-merge bitmap.</p>
+<div class="paragraph">
+<p>Commits are grouped into pseudo-merge groups based on whether or not
+any reference(s) that point at a given commit match the pattern, which
+is an extended regular expression.</p>
+</div>
+<div class="paragraph">
+<p>Within a pseudo-merge group, commits may be further grouped into
+sub-groups based on the capture groups in the pattern. These
+sub-groupings are formed from the regular expressions by concatenating
+any capture groups from the regular expression, with a <em>-</em> dash in
+between.</p>
+</div>
+<div class="paragraph">
+<p>For example, if the pattern is <code>refs/tags/</code>, then all tags (provided
+they meet the below criteria) will be considered candidates for the
+same pseudo-merge group. However, if the pattern is instead
+<code>refs/remotes/([0-9])+/tags/</code>, then tags from different remotes will
+be grouped into separate pseudo-merge groups, based on the remote
+number.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bitmapPseudoMergeltnamegtdecay"> <a class="anchor" href="#Documentation/git-config.txt-bitmapPseudoMergeltnamegtdecay"></a>bitmapPseudoMerge.&lt;name&gt;.decay </dt>
+<dd>
+<p>Determines the rate at which consecutive pseudo-merge bitmap
+groups decrease in size. Must be non-negative. This parameter
+can be thought of as <code>k</code> in the function <code>f(n) = C * n^-k</code>,
+where <code>f(n)</code> is the size of the `n`th group.</p>
+<div class="paragraph">
+<p>Setting the decay rate equal to <code>0</code> will cause all groups to be the
+same size. Setting the decay rate equal to <code>1</code> will cause the <code>n`th
+group to be `1/n</code> the size of the initial group.  Higher values of the
+decay rate cause consecutive groups to shrink at an increasing rate.
+The default is <code>1</code>.</p>
+</div>
+<div class="paragraph">
+<p>If all groups are the same size, it is possible that groups containing
+newer commits will be able to be used less often than earlier groups,
+since it is more likely that the references pointing at newer commits
+will be updated more often than a reference pointing at an old commit.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bitmapPseudoMergeltnamegtsampleRate"> <a class="anchor" href="#Documentation/git-config.txt-bitmapPseudoMergeltnamegtsampleRate"></a>bitmapPseudoMerge.&lt;name&gt;.sampleRate </dt>
+<dd>
+<p>Determines the proportion of non-bitmapped commits (among
+reference tips) which are selected for inclusion in an
+unstable pseudo-merge bitmap. Must be between <code>0</code> and <code>1</code>
+(inclusive). The default is <code>1</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bitmapPseudoMergeltnamegtthreshold"> <a class="anchor" href="#Documentation/git-config.txt-bitmapPseudoMergeltnamegtthreshold"></a>bitmapPseudoMerge.&lt;name&gt;.threshold </dt>
+<dd>
+<p>Determines the minimum age of non-bitmapped commits (among
+reference tips, as above) which are candidates for inclusion
+in an unstable pseudo-merge bitmap. The default is
+<code>1.week.ago</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bitmapPseudoMergeltnamegtmaxMerges"> <a class="anchor" href="#Documentation/git-config.txt-bitmapPseudoMergeltnamegtmaxMerges"></a>bitmapPseudoMerge.&lt;name&gt;.maxMerges </dt>
+<dd>
+<p>Determines the maximum number of pseudo-merge commits among
+which commits may be distributed.</p>
+<div class="paragraph">
+<p>For pseudo-merge groups whose pattern does not contain any capture
+groups, this setting is applied for all commits matching the regular
+expression. For patterns that have one or more capture groups, this
+setting is applied for each distinct capture group.</p>
+</div>
+<div class="paragraph">
+<p>For example, if your capture group is <code>refs/tags/</code>, then this setting
+will distribute all tags into a maximum of <code>maxMerges</code> pseudo-merge
+commits. However, if your capture group is, say,
+<code>refs/remotes/([0-9]+)/tags/</code>, then this setting will be applied to
+each remote&#8217;s set of tags individually.</p>
+</div>
+<div class="paragraph">
+<p>Must be non-negative. The default value is 64.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bitmapPseudoMergeltnamegtstableThreshold"> <a class="anchor" href="#Documentation/git-config.txt-bitmapPseudoMergeltnamegtstableThreshold"></a>bitmapPseudoMerge.&lt;name&gt;.stableThreshold </dt>
+<dd>
+<p>Determines the minimum age of commits (among reference tips,
+as above, however stable commits are still considered
+candidates even when they have been covered by a bitmap) which
+are candidates for a stable a pseudo-merge bitmap. The default
+is <code>1.month.ago</code>.</p>
+<div class="paragraph">
+<p>Setting this threshold to a smaller value (e.g., 1.week.ago) will cause
+more stable groups to be generated (which impose a one-time generation
+cost) but those groups will likely become stale over time. Using a
+larger value incurs the opposite penalty (fewer stable groups which are
+more useful).</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bitmapPseudoMergeltnamegtstableSize"> <a class="anchor" href="#Documentation/git-config.txt-bitmapPseudoMergeltnamegtstableSize"></a>bitmapPseudoMerge.&lt;name&gt;.stableSize </dt>
+<dd>
+<p>Determines the size (in number of commits) of a stable
+psuedo-merge bitmap. The default is <code>512</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-blameblankBoundary"> <a class="anchor" href="#Documentation/git-config.txt-blameblankBoundary"></a>blame.blankBoundary </dt>
+<dd>
+<p>Show blank commit object name for boundary commits in
+<a href='{{< relurl "docs/git-blame" >}}'>git-blame[1]</a>. This option defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-blamecoloring"> <a class="anchor" href="#Documentation/git-config.txt-blamecoloring"></a>blame.coloring </dt>
+<dd>
+<p>This determines the coloring scheme to be applied to blame
+output. It can be <em>repeatedLines</em>, <em>highlightRecent</em>,
+or <em>none</em> which is the default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-blamedate"> <a class="anchor" href="#Documentation/git-config.txt-blamedate"></a>blame.date </dt>
+<dd>
+<p>Specifies the format used to output dates in <a href='{{< relurl "docs/git-blame" >}}'>git-blame[1]</a>.
+If unset the iso format is used. For supported values,
+see the discussion of the <code>--date</code> option at <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-blameshowEmail"> <a class="anchor" href="#Documentation/git-config.txt-blameshowEmail"></a>blame.showEmail </dt>
+<dd>
+<p>Show the author email instead of author name in <a href='{{< relurl "docs/git-blame" >}}'>git-blame[1]</a>.
+This option defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-blameshowRoot"> <a class="anchor" href="#Documentation/git-config.txt-blameshowRoot"></a>blame.showRoot </dt>
+<dd>
+<p>Do not treat root commits as boundaries in <a href='{{< relurl "docs/git-blame" >}}'>git-blame[1]</a>.
+This option defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-blameignoreRevsFile"> <a class="anchor" href="#Documentation/git-config.txt-blameignoreRevsFile"></a>blame.ignoreRevsFile </dt>
+<dd>
+<p>Ignore revisions listed in the file, one unabbreviated object name per
+line, in <a href='{{< relurl "docs/git-blame" >}}'>git-blame[1]</a>.  Whitespace and comments beginning with
+<code>#</code> are ignored.  This option may be repeated multiple times.  Empty
+file names will reset the list of ignored revisions.  This option will
+be handled before the command line option <code>--ignore-revs-file</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-blamemarkUnblamableLines"> <a class="anchor" href="#Documentation/git-config.txt-blamemarkUnblamableLines"></a>blame.markUnblamableLines </dt>
+<dd>
+<p>Mark lines that were changed by an ignored revision that we could not
+attribute to another commit with a <em>*</em> in the output of
+<a href='{{< relurl "docs/git-blame" >}}'>git-blame[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-blamemarkIgnoredLines"> <a class="anchor" href="#Documentation/git-config.txt-blamemarkIgnoredLines"></a>blame.markIgnoredLines </dt>
+<dd>
+<p>Mark lines that were changed by an ignored revision that we attributed to
+another commit with a <em>?</em> in the output of <a href='{{< relurl "docs/git-blame" >}}'>git-blame[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-branchautoSetupMerge"> <a class="anchor" href="#Documentation/git-config.txt-branchautoSetupMerge"></a>branch.autoSetupMerge </dt>
+<dd>
+<p>Tells <em>git branch</em>, <em>git switch</em> and <em>git checkout</em> to set up new branches
+so that <a href='{{< relurl "docs/git-pull" >}}'>git-pull[1]</a> will appropriately merge from the
+starting point branch. Note that even if this option is not set,
+this behavior can be chosen per-branch using the <code>--track</code>
+and <code>--no-track</code> options. The valid settings are: <code>false</code>&#8201;&#8212;&#8201;no
+automatic setup is done; <code>true</code>&#8201;&#8212;&#8201;automatic setup is done when the
+starting point is a remote-tracking branch; <code>always</code>&#8201;&#8212;&#8201;automatic setup is done when the starting point is either a
+local branch or remote-tracking branch; <code>inherit</code>&#8201;&#8212;&#8201;if the starting point
+has a tracking configuration, it is copied to the new
+branch; <code>simple</code>&#8201;&#8212;&#8201;automatic setup is done only when the starting point
+is a remote-tracking branch and the new branch has the same name as the
+remote branch. This option defaults to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-branchautoSetupRebase"> <a class="anchor" href="#Documentation/git-config.txt-branchautoSetupRebase"></a>branch.autoSetupRebase </dt>
+<dd>
+<p>When a new branch is created with <em>git branch</em>, <em>git switch</em> or <em>git checkout</em>
+that tracks another branch, this variable tells Git to set
+up pull to rebase instead of merge (see "branch.&lt;name&gt;.rebase").
+When <code>never</code>, rebase is never automatically set to true.
+When <code>local</code>, rebase is set to true for tracked branches of
+other local branches.
+When <code>remote</code>, rebase is set to true for tracked branches of
+remote-tracking branches.
+When <code>always</code>, rebase will be set to true for all tracking
+branches.
+See "branch.autoSetupMerge" for details on how to set up a
+branch to track another branch.
+This option defaults to never.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-branchsort"> <a class="anchor" href="#Documentation/git-config.txt-branchsort"></a>branch.sort </dt>
+<dd>
+<p>This variable controls the sort ordering of branches when displayed by
+<a href='{{< relurl "docs/git-branch" >}}'>git-branch[1]</a>. Without the "--sort=&lt;value&gt;" option provided, the
+value of this variable will be used as the default.
+See <a href='{{< relurl "docs/git-for-each-ref" >}}'>git-for-each-ref[1]</a> field names for valid values.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-branchltnamegtremote"> <a class="anchor" href="#Documentation/git-config.txt-branchltnamegtremote"></a>branch.&lt;name&gt;.remote </dt>
+<dd>
+<p>When on branch &lt;name&gt;, it tells <em>git fetch</em> and <em>git push</em>
+which remote to fetch from or push to.  The remote to push to
+may be overridden with <code>remote.pushDefault</code> (for all branches).
+The remote to push to, for the current branch, may be further
+overridden by <code>branch.&lt;name&gt;.pushRemote</code>.  If no remote is
+configured, or if you are not on any branch and there is more than
+one remote defined in the repository, it defaults to <code>origin</code> for
+fetching and <code>remote.pushDefault</code> for pushing.
+Additionally, <code>.</code> (a period) is the current local repository
+(a dot-repository), see <code>branch.&lt;name&gt;.merge</code>'s final note below.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-branchltnamegtpushRemote"> <a class="anchor" href="#Documentation/git-config.txt-branchltnamegtpushRemote"></a>branch.&lt;name&gt;.pushRemote </dt>
+<dd>
+<p>When on branch &lt;name&gt;, it overrides <code>branch.&lt;name&gt;.remote</code> for
+pushing.  It also overrides <code>remote.pushDefault</code> for pushing
+from branch &lt;name&gt;.  When you pull from one place (e.g. your
+upstream) and push to another place (e.g. your own publishing
+repository), you would want to set <code>remote.pushDefault</code> to
+specify the remote to push to for all branches, and use this
+option to override it for a specific branch.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-branchltnamegtmerge"> <a class="anchor" href="#Documentation/git-config.txt-branchltnamegtmerge"></a>branch.&lt;name&gt;.merge </dt>
+<dd>
+<p>Defines, together with branch.&lt;name&gt;.remote, the upstream branch
+for the given branch. It tells <em>git fetch</em>/<em>git pull</em>/<em>git rebase</em> which
+branch to merge and can also affect <em>git push</em> (see push.default).
+When in branch &lt;name&gt;, it tells <em>git fetch</em> the default
+refspec to be marked for merging in FETCH_HEAD. The value is
+handled like the remote part of a refspec, and must match a
+ref which is fetched from the remote given by
+"branch.&lt;name&gt;.remote".
+The merge information is used by <em>git pull</em> (which first calls
+<em>git fetch</em>) to lookup the default branch for merging. Without
+this option, <em>git pull</em> defaults to merge the first refspec fetched.
+Specify multiple values to get an octopus merge.
+If you wish to setup <em>git pull</em> so that it merges into &lt;name&gt; from
+another branch in the local repository, you can point
+branch.&lt;name&gt;.merge to the desired branch, and use the relative path
+setting <code>.</code> (a period) for branch.&lt;name&gt;.remote.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-branchltnamegtmergeOptions"> <a class="anchor" href="#Documentation/git-config.txt-branchltnamegtmergeOptions"></a>branch.&lt;name&gt;.mergeOptions </dt>
+<dd>
+<p>Sets default options for merging into branch &lt;name&gt;. The syntax and
+supported options are the same as those of <a href='{{< relurl "docs/git-merge" >}}'>git-merge[1]</a>, but
+option values containing whitespace characters are currently not
+supported.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-branchltnamegtrebase"> <a class="anchor" href="#Documentation/git-config.txt-branchltnamegtrebase"></a>branch.&lt;name&gt;.rebase </dt>
+<dd>
+<p>When true, rebase the branch &lt;name&gt; on top of the fetched branch,
+instead of merging the default branch from the default remote when
+"git pull" is run. See "pull.rebase" for doing this in a non
+branch-specific manner.</p>
+<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>
+so that the local merge commits are included in the rebase (see
+<a href='{{< relurl "docs/git-rebase" >}}'>git-rebase[1]</a> for details).</p>
+</div>
+<div class="paragraph">
+<p>When the value is <code>interactive</code> (or just <em>i</em>), the rebase is run in interactive
+mode.</p>
+</div>
+<div class="paragraph">
+<p><strong>NOTE</strong>: this is a possibly dangerous operation; do <strong>not</strong> use
+it unless you understand the implications (see <a href='{{< relurl "docs/git-rebase" >}}'>git-rebase[1]</a>
+for details).</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-branchltnamegtdescription"> <a class="anchor" href="#Documentation/git-config.txt-branchltnamegtdescription"></a>branch.&lt;name&gt;.description </dt>
+<dd>
+<p>Branch description, can be edited with
+<code>git branch --edit-description</code>. Branch description is
+automatically added to the format-patch cover letter or
+request-pull summary.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-browserlttoolgtcmd"> <a class="anchor" href="#Documentation/git-config.txt-browserlttoolgtcmd"></a>browser.&lt;tool&gt;.cmd </dt>
+<dd>
+<p>Specify the command to invoke the specified browser. The
+specified command is evaluated in shell with the URLs passed
+as arguments. (See <a href='{{< relurl "docs/git-web--browse" >}}'>git-web&#x2d;&#x2d;browse[1]</a>.)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-browserlttoolgtpath"> <a class="anchor" href="#Documentation/git-config.txt-browserlttoolgtpath"></a>browser.&lt;tool&gt;.path </dt>
+<dd>
+<p>Override the path for the given tool that may be used to
+browse HTML help (see <code>-w</code> option in <a href='{{< relurl "docs/git-help" >}}'>git-help[1]</a>) or a
+working repository in gitweb (see <a href='{{< relurl "docs/git-instaweb" >}}'>git-instaweb[1]</a>).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bundle"> <a class="anchor" href="#Documentation/git-config.txt-bundle"></a>bundle.* </dt>
+<dd>
+<p>The <code>bundle.*</code> keys may appear in a bundle list file found via the
+<code>git clone --bundle-uri</code> option. These keys currently have no effect
+if placed in a repository config file, though this will change in the
+future. See <a href="{{< relurl "docs/bundle-uri" >}}">the bundle URI design
+document</a> for more details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bundleversion"> <a class="anchor" href="#Documentation/git-config.txt-bundleversion"></a>bundle.version </dt>
+<dd>
+<p>This integer value advertises the version of the bundle list format
+used by the bundle list. Currently, the only accepted value is <code>1</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bundlemode"> <a class="anchor" href="#Documentation/git-config.txt-bundlemode"></a>bundle.mode </dt>
+<dd>
+<p>This string value should be either <code>all</code> or <code>any</code>. This value describes
+whether all of the advertised bundles are required to unbundle a
+complete understanding of the bundled information (<code>all</code>) or if any one
+of the listed bundle URIs is sufficient (<code>any</code>).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bundleheuristic"> <a class="anchor" href="#Documentation/git-config.txt-bundleheuristic"></a>bundle.heuristic </dt>
+<dd>
+<p>If this string-valued key exists, then the bundle list is designed to
+work well with incremental <code>git fetch</code> commands. The heuristic signals
+that there are additional keys available for each bundle that help
+determine which subset of bundles the client should download. The
+only value currently understood is <code>creationToken</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bundleltidgt"> <a class="anchor" href="#Documentation/git-config.txt-bundleltidgt"></a>bundle.&lt;id&gt;.* </dt>
+<dd>
+<p>The <code>bundle.&lt;id&gt;.*</code> keys are used to describe a single item in the
+bundle list, grouped under <code>&lt;id&gt;</code> for identification purposes.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-bundleltidgturi"> <a class="anchor" href="#Documentation/git-config.txt-bundleltidgturi"></a>bundle.&lt;id&gt;.uri </dt>
+<dd>
+<p>This string value defines the URI by which Git can reach the contents
+of this <code>&lt;id&gt;</code>. This URI may be a bundle file or another bundle list.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-checkoutdefaultRemote"> <a class="anchor" href="#Documentation/git-config.txt-checkoutdefaultRemote"></a>checkout.defaultRemote </dt>
+<dd>
+<p>When you run <code>git checkout &lt;something&gt;</code>
+or <code>git switch &lt;something&gt;</code> and only have one
+remote, it may implicitly fall back on checking out and
+tracking e.g. <code>origin/&lt;something&gt;</code>. This stops working as soon
+as you have more than one remote with a <code>&lt;something&gt;</code>
+reference. This setting allows for setting the name of a
+preferred remote that should always win when it comes to
+disambiguation. The typical use-case is to set this to
+<code>origin</code>.</p>
+<div class="paragraph">
+<p>Currently this is used by <a href='{{< relurl "docs/git-switch" >}}'>git-switch[1]</a> and
+<a href='{{< relurl "docs/git-checkout" >}}'>git-checkout[1]</a> when <code>git checkout &lt;something&gt;</code>
+or <code>git switch &lt;something&gt;</code>
+will checkout the <code>&lt;something&gt;</code> branch on another remote,
+and by <a href='{{< relurl "docs/git-worktree" >}}'>git-worktree[1]</a> when <code>git worktree add</code> refers to a
+remote branch. This setting might be used for other checkout-like
+commands or functionality in the future.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-checkoutguess"> <a class="anchor" href="#Documentation/git-config.txt-checkoutguess"></a>checkout.guess </dt>
+<dd>
+<p>Provides the default value for the <code>--guess</code> or <code>--no-guess</code>
+option in <code>git checkout</code> and <code>git switch</code>. See
+<a href='{{< relurl "docs/git-switch" >}}'>git-switch[1]</a> and <a href='{{< relurl "docs/git-checkout" >}}'>git-checkout[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-checkoutworkers"> <a class="anchor" href="#Documentation/git-config.txt-checkoutworkers"></a>checkout.workers </dt>
+<dd>
+<p>The number of parallel workers to use when updating the working tree.
+The default is one, i.e. sequential execution. If set to a value less
+than one, Git will use as many workers as the number of logical cores
+available. This setting and <code>checkout.thresholdForParallelism</code> affect
+all commands that perform checkout. E.g. checkout, clone, reset,
+sparse-checkout, etc.</p>
+<div class="paragraph">
+<p>Note: Parallel checkout usually delivers better performance for repositories
+located on SSDs or over NFS. For repositories on spinning disks and/or machines
+with a small number of cores, the default sequential checkout often performs
+better. The size and compression level of a repository might also influence how
+well the parallel version performs.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-checkoutthresholdForParallelism"> <a class="anchor" href="#Documentation/git-config.txt-checkoutthresholdForParallelism"></a>checkout.thresholdForParallelism </dt>
+<dd>
+<p>When running parallel checkout with a small number of files, the cost
+of subprocess spawning and inter-process communication might outweigh
+the parallelization gains. This setting allows you to define the minimum
+number of files for which parallel checkout should be attempted. The
+default is 100.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-cleanrequireForce"> <a class="anchor" href="#Documentation/git-config.txt-cleanrequireForce"></a>clean.requireForce </dt>
+<dd>
+<p>A boolean to make git-clean refuse to delete files unless -f
+is given. Defaults to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeclonedefaultRemoteNamecode"> <a class="anchor" href="#Documentation/git-config.txt-codeclonedefaultRemoteNamecode"></a><code>clone.defaultRemoteName</code> </dt>
+<dd>
+<p>The name of the remote to create when cloning a repository.  Defaults to
+<code>origin</code>.
+It can be overridden by passing the <code>--origin</code> command-line
+option to <a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeclonerejectShallowcode"> <a class="anchor" href="#Documentation/git-config.txt-codeclonerejectShallowcode"></a><code>clone.rejectShallow</code> </dt>
+<dd>
+<p>Reject cloning a repository if it is a shallow one; this can be overridden by
+passing the <code>--reject-shallow</code> option on the command line.
+See <a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeclonefilterSubmodulescode"> <a class="anchor" href="#Documentation/git-config.txt-codeclonefilterSubmodulescode"></a><code>clone.filterSubmodules</code> </dt>
+<dd>
+<p>If a partial clone filter is provided (see <code>--filter</code> in
+<a href='{{< relurl "docs/git-rev-list" >}}'>git-rev-list[1]</a>) and <code>--recurse-submodules</code> is used, also apply
+the filter to submodules.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coloradvice"> <a class="anchor" href="#Documentation/git-config.txt-coloradvice"></a>color.advice </dt>
+<dd>
+<p>A boolean to enable/disable color in hints (e.g. when a push
+failed, see <code>advice.*</code> for a list).  May be set to <code>always</code>,
+<code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which case colors
+are used only when the error output goes to a terminal. If
+unset, then the value of <code>color.ui</code> is used (<code>auto</code> by default).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coloradvicehint"> <a class="anchor" href="#Documentation/git-config.txt-coloradvicehint"></a>color.advice.hint </dt>
+<dd>
+<p>Use customized color for hints.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorblamehighlightRecent"> <a class="anchor" href="#Documentation/git-config.txt-colorblamehighlightRecent"></a>color.blame.highlightRecent </dt>
+<dd>
+<p>Specify the line annotation color for <code>git blame --color-by-age</code>
+depending upon the age of the line.</p>
+<div class="paragraph">
+<p>This setting should be set to a comma-separated list of color and
+date settings, starting and ending with a color, the dates should be
+set from oldest to newest. The metadata will be colored with the
+specified colors if the line was introduced before the given
+timestamp, overwriting older timestamped colors.</p>
+</div>
+<div class="paragraph">
+<p>Instead of an absolute timestamp relative timestamps work as well,
+e.g. <code>2.weeks.ago</code> is valid to address anything older than 2 weeks.</p>
+</div>
+<div class="paragraph">
+<p>It defaults to <code>blue,12 month ago,white,1 month ago,red</code>, which
+colors everything older than one year blue, recent changes between
+one month and one year old are kept white, and lines introduced
+within the last month are colored red.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorblamerepeatedLines"> <a class="anchor" href="#Documentation/git-config.txt-colorblamerepeatedLines"></a>color.blame.repeatedLines </dt>
+<dd>
+<p>Use the specified color to colorize line annotations for
+<code>git blame --color-lines</code>, if they come from the same commit as the
+preceding line. Defaults to cyan.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorbranch"> <a class="anchor" href="#Documentation/git-config.txt-colorbranch"></a>color.branch </dt>
+<dd>
+<p>A boolean to enable/disable color in the output of
+<a href='{{< relurl "docs/git-branch" >}}'>git-branch[1]</a>. May be set to <code>always</code>,
+<code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which case colors are used
+only when the output is to a terminal. If unset, then the
+value of <code>color.ui</code> is used (<code>auto</code> by default).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorbranchltslotgt"> <a class="anchor" href="#Documentation/git-config.txt-colorbranchltslotgt"></a>color.branch.&lt;slot&gt; </dt>
+<dd>
+<p>Use customized color for branch coloration. <code>&lt;slot&gt;</code> is one of
+<code>current</code> (the current branch), <code>local</code> (a local branch),
+<code>remote</code> (a remote-tracking branch in refs/remotes/),
+<code>upstream</code> (upstream tracking branch), <code>plain</code> (other
+refs).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colordiff"> <a class="anchor" href="#Documentation/git-config.txt-colordiff"></a>color.diff </dt>
+<dd>
+<p>Whether to use ANSI escape sequences to add color to patches.
+If this is set to <code>always</code>, <a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a>,
+<a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a>, and <a href='{{< relurl "docs/git-show" >}}'>git-show[1]</a> will use color
+for all patches.  If it is set to <code>true</code> or <code>auto</code>, those
+commands will only use color when output is to the terminal.
+If unset, then the value of <code>color.ui</code> is used (<code>auto</code> by
+default).</p>
+<div class="paragraph">
+<p>This does not affect <a href='{{< relurl "docs/git-format-patch" >}}'>git-format-patch[1]</a> or the
+<em>git-diff-*</em> plumbing commands.  Can be overridden on the
+command line with the <code>--color[=&lt;when&gt;]</code> option.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colordiffltslotgt"> <a class="anchor" href="#Documentation/git-config.txt-colordiffltslotgt"></a>color.diff.&lt;slot&gt; </dt>
+<dd>
+<p>Use customized color for diff colorization.  <code>&lt;slot&gt;</code> specifies
+which part of the patch to use the specified color, and is one
+of <code>context</code> (context text - <code>plain</code> is a historical synonym),
+<code>meta</code> (metainformation), <code>frag</code>
+(hunk header), <em>func</em> (function in hunk header), <code>old</code> (removed lines),
+<code>new</code> (added lines), <code>commit</code> (commit headers), <code>whitespace</code>
+(highlighting whitespace errors), <code>oldMoved</code> (deleted lines),
+<code>newMoved</code> (added lines), <code>oldMovedDimmed</code>, <code>oldMovedAlternative</code>,
+<code>oldMovedAlternativeDimmed</code>, <code>newMovedDimmed</code>, <code>newMovedAlternative</code>
+<code>newMovedAlternativeDimmed</code> (See the <em>&lt;mode&gt;</em>
+setting of <em>--color-moved</em> in <a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a> for details),
+<code>contextDimmed</code>, <code>oldDimmed</code>, <code>newDimmed</code>, <code>contextBold</code>,
+<code>oldBold</code>, and <code>newBold</code> (see <a href='{{< relurl "docs/git-range-diff" >}}'>git-range-diff[1]</a> for details).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colordecorateltslotgt"> <a class="anchor" href="#Documentation/git-config.txt-colordecorateltslotgt"></a>color.decorate.&lt;slot&gt; </dt>
+<dd>
+<p>Use customized color for <em>git log --decorate</em> output.  <code>&lt;slot&gt;</code> is one
+of <code>branch</code>, <code>remoteBranch</code>, <code>tag</code>, <code>stash</code> or <code>HEAD</code> for local
+branches, remote-tracking branches, tags, stash and HEAD, respectively
+and <code>grafted</code> for grafted commits.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorgrep"> <a class="anchor" href="#Documentation/git-config.txt-colorgrep"></a>color.grep </dt>
+<dd>
+<p>When set to <code>always</code>, always highlight matches.  When <code>false</code> (or
+<code>never</code>), never.  When set to <code>true</code> or <code>auto</code>, use color only
+when the output is written to the terminal.  If unset, then the
+value of <code>color.ui</code> is used (<code>auto</code> by default).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorgrepltslotgt"> <a class="anchor" href="#Documentation/git-config.txt-colorgrepltslotgt"></a>color.grep.&lt;slot&gt; </dt>
+<dd>
+<p>Use customized color for grep colorization.  <code>&lt;slot&gt;</code> specifies which
+part of the line to use the specified color, and is one of</p>
+<div class="openblock">
+<div class="content">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-codecontextcode"> <a class="anchor" href="#Documentation/git-config.txt-codecontextcode"></a><code>context</code> </dt>
+<dd>
+<p>non-matching text in context lines (when using <code>-A</code>, <code>-B</code>, or <code>-C</code>)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codefilenamecode"> <a class="anchor" href="#Documentation/git-config.txt-codefilenamecode"></a><code>filename</code> </dt>
+<dd>
+<p>filename prefix (when not using <code>-h</code>)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codefunctioncode"> <a class="anchor" href="#Documentation/git-config.txt-codefunctioncode"></a><code>function</code> </dt>
+<dd>
+<p>function name lines (when using <code>-p</code>)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codelineNumbercode"> <a class="anchor" href="#Documentation/git-config.txt-codelineNumbercode"></a><code>lineNumber</code> </dt>
+<dd>
+<p>line number prefix (when using <code>-n</code>)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codecolumncode"> <a class="anchor" href="#Documentation/git-config.txt-codecolumncode"></a><code>column</code> </dt>
+<dd>
+<p>column number prefix (when using <code>--column</code>)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codematchcode"> <a class="anchor" href="#Documentation/git-config.txt-codematchcode"></a><code>match</code> </dt>
+<dd>
+<p>matching text (same as setting <code>matchContext</code> and <code>matchSelected</code>)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codematchContextcode"> <a class="anchor" href="#Documentation/git-config.txt-codematchContextcode"></a><code>matchContext</code> </dt>
+<dd>
+<p>matching text in context lines</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codematchSelectedcode"> <a class="anchor" href="#Documentation/git-config.txt-codematchSelectedcode"></a><code>matchSelected</code> </dt>
+<dd>
+<p>matching text in selected lines. Also, used to customize the following
+<a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a> subcommands: <code>--grep</code>, <code>--author</code>, and <code>--committer</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeselectedcode"> <a class="anchor" href="#Documentation/git-config.txt-codeselectedcode"></a><code>selected</code> </dt>
+<dd>
+<p>non-matching text in selected lines. Also, used to customize the
+following <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a> subcommands: <code>--grep</code>, <code>--author</code> and
+<code>--committer</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeseparatorcode"> <a class="anchor" href="#Documentation/git-config.txt-codeseparatorcode"></a><code>separator</code> </dt>
+<dd>
+<p>separators between fields on a line (<code>:</code>, <code>-</code>, and <code>=</code>)
+and between hunks (<code>--</code>)</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorinteractive"> <a class="anchor" href="#Documentation/git-config.txt-colorinteractive"></a>color.interactive </dt>
+<dd>
+<p>When set to <code>always</code>, always use colors for interactive prompts
+and displays (such as those used by "git-add --interactive" and
+"git-clean --interactive"). When false (or <code>never</code>), never.
+When set to <code>true</code> or <code>auto</code>, use colors only when the output is
+to the terminal. If unset, then the value of <code>color.ui</code> is
+used (<code>auto</code> by default).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorinteractiveltslotgt"> <a class="anchor" href="#Documentation/git-config.txt-colorinteractiveltslotgt"></a>color.interactive.&lt;slot&gt; </dt>
+<dd>
+<p>Use customized color for <em>git add --interactive</em> and <em>git clean
+--interactive</em> output. <code>&lt;slot&gt;</code> may be <code>prompt</code>, <code>header</code>, <code>help</code>
+or <code>error</code>, for four distinct types of normal output from
+interactive commands.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorpager"> <a class="anchor" href="#Documentation/git-config.txt-colorpager"></a>color.pager </dt>
+<dd>
+<p>A boolean to specify whether <code>auto</code> color modes should colorize
+output going to the pager. Defaults to true; set this to false
+if your pager does not understand ANSI color codes.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorpush"> <a class="anchor" href="#Documentation/git-config.txt-colorpush"></a>color.push </dt>
+<dd>
+<p>A boolean to enable/disable color in push errors. May be set to
+<code>always</code>, <code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which
+case colors are used only when the error output goes to a terminal.
+If unset, then the value of <code>color.ui</code> is used (<code>auto</code> by default).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorpusherror"> <a class="anchor" href="#Documentation/git-config.txt-colorpusherror"></a>color.push.error </dt>
+<dd>
+<p>Use customized color for push errors.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorremote"> <a class="anchor" href="#Documentation/git-config.txt-colorremote"></a>color.remote </dt>
+<dd>
+<p>If set, keywords at the start of the line are highlighted. The
+keywords are "error", "warning", "hint" and "success", and are
+matched case-insensitively. May be set to <code>always</code>, <code>false</code> (or
+<code>never</code>) or <code>auto</code> (or <code>true</code>). If unset, then the value of
+<code>color.ui</code> is used (<code>auto</code> by default).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorremoteltslotgt"> <a class="anchor" href="#Documentation/git-config.txt-colorremoteltslotgt"></a>color.remote.&lt;slot&gt; </dt>
+<dd>
+<p>Use customized color for each remote keyword. <code>&lt;slot&gt;</code> may be
+<code>hint</code>, <code>warning</code>, <code>success</code> or <code>error</code> which match the
+corresponding keyword.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorshowBranch"> <a class="anchor" href="#Documentation/git-config.txt-colorshowBranch"></a>color.showBranch </dt>
+<dd>
+<p>A boolean to enable/disable color in the output of
+<a href='{{< relurl "docs/git-show-branch" >}}'>git-show-branch[1]</a>. May be set to <code>always</code>,
+<code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which case colors are used
+only when the output is to a terminal. If unset, then the
+value of <code>color.ui</code> is used (<code>auto</code> by default).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorstatus"> <a class="anchor" href="#Documentation/git-config.txt-colorstatus"></a>color.status </dt>
+<dd>
+<p>A boolean to enable/disable color in the output of
+<a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a>. May be set to <code>always</code>,
+<code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which case colors are used
+only when the output is to a terminal. If unset, then the
+value of <code>color.ui</code> is used (<code>auto</code> by default).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorstatusltslotgt"> <a class="anchor" href="#Documentation/git-config.txt-colorstatusltslotgt"></a>color.status.&lt;slot&gt; </dt>
+<dd>
+<p>Use customized color for status colorization. <code>&lt;slot&gt;</code> is
+one of <code>header</code> (the header text of the status message),
+<code>added</code> or <code>updated</code> (files which are added but not committed),
+<code>changed</code> (files which are changed but not added in the index),
+<code>untracked</code> (files which are not tracked by Git),
+<code>branch</code> (the current branch),
+<code>nobranch</code> (the color the <em>no branch</em> warning is shown in, defaulting
+to red),
+<code>localBranch</code> or <code>remoteBranch</code> (the local and remote branch names,
+respectively, when branch and tracking information is displayed in the
+status short-format), or
+<code>unmerged</code> (files which have unmerged changes).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colortransport"> <a class="anchor" href="#Documentation/git-config.txt-colortransport"></a>color.transport </dt>
+<dd>
+<p>A boolean to enable/disable color when pushes are rejected. May be
+set to <code>always</code>, <code>false</code> (or <code>never</code>) or <code>auto</code> (or <code>true</code>), in which
+case colors are used only when the error output goes to a terminal.
+If unset, then the value of <code>color.ui</code> is used (<code>auto</code> by default).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colortransportrejected"> <a class="anchor" href="#Documentation/git-config.txt-colortransportrejected"></a>color.transport.rejected </dt>
+<dd>
+<p>Use customized color when a push was rejected.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-colorui"> <a class="anchor" href="#Documentation/git-config.txt-colorui"></a>color.ui </dt>
+<dd>
+<p>This variable determines the default value for variables such
+as <code>color.diff</code> and <code>color.grep</code> that control the use of color
+per command family. Its scope will expand as more commands learn
+configuration to set a default for the <code>--color</code> option.  Set it
+to <code>false</code> or <code>never</code> if you prefer Git commands not to use
+color unless enabled explicitly with some other configuration
+or the <code>--color</code> option. Set it to <code>always</code> if you want all
+output not intended for machine consumption to use color, to
+<code>true</code> or <code>auto</code> (this is the default since Git 1.8.4) if you
+want such output to use color when written to the terminal.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-columnui"> <a class="anchor" href="#Documentation/git-config.txt-columnui"></a>column.ui </dt>
+<dd>
+<p>Specify whether supported commands should output in columns.
+This variable consists of a list of tokens separated by spaces
+or commas:</p>
+<div class="paragraph">
+<p>These options control when the feature should be enabled
+(defaults to <em>never</em>):</p>
+</div>
+<div class="openblock">
+<div class="content">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-codealwayscode"> <a class="anchor" href="#Documentation/git-config.txt-codealwayscode"></a><code>always</code> </dt>
+<dd>
+<p>always show in columns</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codenevercode"> <a class="anchor" href="#Documentation/git-config.txt-codenevercode"></a><code>never</code> </dt>
+<dd>
+<p>never show in columns</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeautocode"> <a class="anchor" href="#Documentation/git-config.txt-codeautocode"></a><code>auto</code> </dt>
+<dd>
+<p>show in columns if the output is to the terminal</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>These options control layout (defaults to <em>column</em>).  Setting any
+of these implies <em>always</em> if none of <em>always</em>, <em>never</em>, or <em>auto</em> are
+specified.</p>
+</div>
+<div class="openblock">
+<div class="content">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-codecolumncode-1"> <a class="anchor" href="#Documentation/git-config.txt-codecolumncode-1"></a><code>column</code> </dt>
+<dd>
+<p>fill columns before rows</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coderowcode"> <a class="anchor" href="#Documentation/git-config.txt-coderowcode"></a><code>row</code> </dt>
+<dd>
+<p>fill rows before columns</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeplaincode"> <a class="anchor" href="#Documentation/git-config.txt-codeplaincode"></a><code>plain</code> </dt>
+<dd>
+<p>show in one column</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Finally, these options can be combined with a layout option (defaults
+to <em>nodense</em>):</p>
+</div>
+<div class="openblock">
+<div class="content">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-codedensecode"> <a class="anchor" href="#Documentation/git-config.txt-codedensecode"></a><code>dense</code> </dt>
+<dd>
+<p>make unequal size columns to utilize more space</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codenodensecode"> <a class="anchor" href="#Documentation/git-config.txt-codenodensecode"></a><code>nodense</code> </dt>
+<dd>
+<p>make equal size columns</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-columnbranch"> <a class="anchor" href="#Documentation/git-config.txt-columnbranch"></a>column.branch </dt>
+<dd>
+<p>Specify whether to output branch listing in <code>git branch</code> in columns.
+See <code>column.ui</code> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-columnclean"> <a class="anchor" href="#Documentation/git-config.txt-columnclean"></a>column.clean </dt>
+<dd>
+<p>Specify the layout when listing items in <code>git clean -i</code>, which always
+shows files and directories in columns. See <code>column.ui</code> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-columnstatus"> <a class="anchor" href="#Documentation/git-config.txt-columnstatus"></a>column.status </dt>
+<dd>
+<p>Specify whether to output untracked files in <code>git status</code> in columns.
+See <code>column.ui</code> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-columntag"> <a class="anchor" href="#Documentation/git-config.txt-columntag"></a>column.tag </dt>
+<dd>
+<p>Specify whether to output tag listings in <code>git tag</code> in columns.
+See <code>column.ui</code> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-commitcleanup"> <a class="anchor" href="#Documentation/git-config.txt-commitcleanup"></a>commit.cleanup </dt>
+<dd>
+<p>This setting overrides the default of the <code>--cleanup</code> option in
+<code>git commit</code>. See <a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a> for details. Changing the
+default can be useful when you always want to keep lines that begin
+with the comment character <code>#</code> in your log message, in which case you
+would do <code>git config commit.cleanup whitespace</code> (note that you will
+have to remove the help lines that begin with <code>#</code> in the commit log
+template yourself, if you do this).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-commitgpgSign"> <a class="anchor" href="#Documentation/git-config.txt-commitgpgSign"></a>commit.gpgSign </dt>
+<dd>
+<p>A boolean to specify whether all commits should be GPG signed.
+Use of this option when doing operations such as rebase can
+result in a large number of commits being signed. It may be
+convenient to use an agent to avoid typing your GPG passphrase
+several times.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-commitstatus"> <a class="anchor" href="#Documentation/git-config.txt-commitstatus"></a>commit.status </dt>
+<dd>
+<p>A boolean to enable/disable inclusion of status information in the
+commit message template when using an editor to prepare the commit
+message.  Defaults to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-committemplate"> <a class="anchor" href="#Documentation/git-config.txt-committemplate"></a>commit.template </dt>
+<dd>
+<p>Specify the pathname of a file to use as the template for
+new commit messages.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-commitverbose"> <a class="anchor" href="#Documentation/git-config.txt-commitverbose"></a>commit.verbose </dt>
+<dd>
+<p>A boolean or int to specify the level of verbosity with <code>git commit</code>.
+See <a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-commitGraphgenerationVersion"> <a class="anchor" href="#Documentation/git-config.txt-commitGraphgenerationVersion"></a>commitGraph.generationVersion </dt>
+<dd>
+<p>Specifies the type of generation number version to use when writing
+or reading the commit-graph file. If version 1 is specified, then
+the corrected commit dates will not be written or read. Defaults to
+2.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-commitGraphmaxNewFilters"> <a class="anchor" href="#Documentation/git-config.txt-commitGraphmaxNewFilters"></a>commitGraph.maxNewFilters </dt>
+<dd>
+<p>Specifies the default value for the <code>--max-new-filters</code> option of <code>git
+commit-graph write</code> (c.f., <a href='{{< relurl "docs/git-commit-graph" >}}'>git-commit-graph[1]</a>).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-commitGraphreadChangedPaths"> <a class="anchor" href="#Documentation/git-config.txt-commitGraphreadChangedPaths"></a>commitGraph.readChangedPaths </dt>
+<dd>
+<p>Deprecated. Equivalent to commitGraph.changedPathsVersion=-1 if true, and
+commitGraph.changedPathsVersion=0 if false. (If commitGraph.changedPathVersion
+is also set, commitGraph.changedPathsVersion takes precedence.)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-commitGraphchangedPathsVersion"> <a class="anchor" href="#Documentation/git-config.txt-commitGraphchangedPathsVersion"></a>commitGraph.changedPathsVersion </dt>
+<dd>
+<p>Specifies the version of the changed-path Bloom filters that Git will read and
+write. May be -1, 0, 1, or 2. Note that values greater than 1 may be
+incompatible with older versions of Git which do not yet understand
+those versions. Use caution when operating in a mixed-version
+environment.</p>
+<div class="paragraph">
+<p>Defaults to -1.</p>
+</div>
+<div class="paragraph">
+<p>If -1, Git will use the version of the changed-path Bloom filters in the
+repository, defaulting to 1 if there are none.</p>
+</div>
+<div class="paragraph">
+<p>If 0, Git will not read any Bloom filters, and will write version 1 Bloom
+filters when instructed to write.</p>
+</div>
+<div class="paragraph">
+<p>If 1, Git will only read version 1 Bloom filters, and will write version 1
+Bloom filters.</p>
+</div>
+<div class="paragraph">
+<p>If 2, Git will only read version 2 Bloom filters, and will write version 2
+Bloom filters.</p>
+</div>
+<div class="paragraph">
+<p>See <a href='{{< relurl "docs/git-commit-graph" >}}'>git-commit-graph[1]</a> for more information.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-completioncommands"> <a class="anchor" href="#Documentation/git-config.txt-completioncommands"></a>completion.commands </dt>
+<dd>
+<p>This is only used by git-completion.bash to add or remove
+commands from the list of completed commands. Normally only
+porcelain commands and a few select others are completed. You
+can add more commands, separated by space, in this
+variable. Prefixing the command with <em>-</em> will remove it from
+the existing list.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corefileMode"> <a class="anchor" href="#Documentation/git-config.txt-corefileMode"></a>core.fileMode </dt>
+<dd>
+<p>Tells Git if the executable bit of files in the working tree
+is to be honored.</p>
+<div class="paragraph">
+<p>Some filesystems lose the executable bit when a file that is
+marked as executable is checked out, or checks out a
+non-executable file with executable bit on.
+<a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a> or <a href='{{< relurl "docs/git-init" >}}'>git-init[1]</a> probe the filesystem
+to see if it handles the executable bit correctly
+and this variable is automatically set as necessary.</p>
+</div>
+<div class="paragraph">
+<p>A repository, however, may be on a filesystem that handles
+the filemode correctly, and this variable is set to <em>true</em>
+when created, but later may be made accessible from another
+environment that loses the filemode (e.g. exporting ext4 via
+CIFS mount, visiting a Cygwin created repository with
+Git for Windows or Eclipse).
+In such a case it may be necessary to set this variable to <em>false</em>.
+See <a href='{{< relurl "docs/git-update-index" >}}'>git-update-index[1]</a>.</p>
+</div>
+<div class="paragraph">
+<p>The default is true (when core.filemode is not specified in the config file).</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corehideDotFiles"> <a class="anchor" href="#Documentation/git-config.txt-corehideDotFiles"></a>core.hideDotFiles </dt>
+<dd>
+<p>(Windows-only) If true, mark newly-created directories and files whose
+name starts with a dot as hidden.  If <em>dotGitOnly</em>, only the <code>.git/</code>
+directory is hidden, but no other files starting with a dot.  The
+default mode is <em>dotGitOnly</em>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreignoreCase"> <a class="anchor" href="#Documentation/git-config.txt-coreignoreCase"></a>core.ignoreCase </dt>
+<dd>
+<p>Internal variable which enables various workarounds to enable
+Git to work better on filesystems that are not case sensitive,
+like APFS, HFS+, FAT, NTFS, etc. For example, if a directory listing
+finds "makefile" when Git expects "Makefile", Git will assume
+it is really the same file, and continue to remember it as
+"Makefile".</p>
+<div class="paragraph">
+<p>The default is false, except <a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a> or <a href='{{< relurl "docs/git-init" >}}'>git-init[1]</a>
+will probe and set core.ignoreCase true if appropriate when the repository
+is created.</p>
+</div>
+<div class="paragraph">
+<p>Git relies on the proper configuration of this variable for your operating
+and file system. Modifying this value may result in unexpected behavior.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreprecomposeUnicode"> <a class="anchor" href="#Documentation/git-config.txt-coreprecomposeUnicode"></a>core.precomposeUnicode </dt>
+<dd>
+<p>This option is only used by Mac OS implementation of Git.
+When core.precomposeUnicode=true, Git reverts the unicode decomposition
+of filenames done by Mac OS. This is useful when sharing a repository
+between Mac OS and Linux or Windows.
+(Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7).
+When false, file names are handled fully transparent by Git,
+which is backward compatible with older versions of Git.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreprotectHFS"> <a class="anchor" href="#Documentation/git-config.txt-coreprotectHFS"></a>core.protectHFS </dt>
+<dd>
+<p>If set to true, do not allow checkout of paths that would
+be considered equivalent to <code>.git</code> on an HFS+ filesystem.
+Defaults to <code>true</code> on Mac OS, and <code>false</code> elsewhere.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreprotectNTFS"> <a class="anchor" href="#Documentation/git-config.txt-coreprotectNTFS"></a>core.protectNTFS </dt>
+<dd>
+<p>If set to true, do not allow checkout of paths that would
+cause problems with the NTFS filesystem, e.g. conflict with
+8.3 "short" names.
+Defaults to <code>true</code> on Windows, and <code>false</code> elsewhere.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corefsmonitor"> <a class="anchor" href="#Documentation/git-config.txt-corefsmonitor"></a>core.fsmonitor </dt>
+<dd>
+<p>If set to true, enable the built-in file system monitor
+daemon for this working directory (<a href='{{< relurl "docs/git-fsmonitor--daemon" >}}'>git-fsmonitor&#x2d;&#x2d;daemon[1]</a>).</p>
+<div class="paragraph">
+<p>Like hook-based file system monitors, the built-in file system monitor
+can speed up Git commands that need to refresh the Git index
+(e.g. <code>git status</code>) in a working directory with many files.  The
+built-in monitor eliminates the need to install and maintain an
+external third-party tool.</p>
+</div>
+<div class="paragraph">
+<p>The built-in file system monitor is currently available only on a
+limited set of supported platforms.  Currently, this includes Windows
+and MacOS.</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>Otherwise, this variable contains the pathname of the "fsmonitor"
+hook command.</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>This hook command is used to identify all files that may have changed
+since the requested date/time. This information is used to speed up
+git by avoiding unnecessary scanning of files that have not changed.</p>
+</div>
+<div class="paragraph">
+<p>See the "fsmonitor-watchman" section of <a href='{{< relurl "docs/githooks" >}}'>githooks[5]</a>.</p>
+</div>
+<div class="paragraph">
+<p>Note that if you concurrently use multiple versions of Git, such
+as one version on the command line and another version in an IDE
+tool, that the definition of <code>core.fsmonitor</code> was extended to
+allow boolean values in addition to hook pathnames.  Git versions
+2.35.1 and prior will not understand the boolean values and will
+consider the "true" or "false" values as hook pathnames to be
+invoked.  Git versions 2.26 thru 2.35.1 default to hook protocol
+V2 and will fall back to no fsmonitor (full scan).  Git versions
+prior to 2.26 default to hook protocol V1 and will silently
+assume there were no changes to report (no scan), so status
+commands may report incomplete results.  For this reason, it is
+best to upgrade all of your Git versions before using the built-in
+file system monitor.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corefsmonitorHookVersion"> <a class="anchor" href="#Documentation/git-config.txt-corefsmonitorHookVersion"></a>core.fsmonitorHookVersion </dt>
+<dd>
+<p>Sets the protocol version to be used when invoking the
+"fsmonitor" hook.</p>
+<div class="paragraph">
+<p>There are currently versions 1 and 2. When this is not set,
+version 2 will be tried first and if it fails then version 1
+will be tried. Version 1 uses a timestamp as input to determine
+which files have changes since that time but some monitors
+like Watchman have race conditions when used with a timestamp.
+Version 2 uses an opaque string so that the monitor can return
+something that can be used to determine what files have changed
+without race conditions.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coretrustctime"> <a class="anchor" href="#Documentation/git-config.txt-coretrustctime"></a>core.trustctime </dt>
+<dd>
+<p>If false, the ctime differences between the index and the
+working tree are ignored; useful when the inode change time
+is regularly modified by something outside Git (file system
+crawlers and some backup systems).
+See <a href='{{< relurl "docs/git-update-index" >}}'>git-update-index[1]</a>. True by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coresplitIndex"> <a class="anchor" href="#Documentation/git-config.txt-coresplitIndex"></a>core.splitIndex </dt>
+<dd>
+<p>If true, the split-index feature of the index will be used.
+See <a href='{{< relurl "docs/git-update-index" >}}'>git-update-index[1]</a>. False by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreuntrackedCache"> <a class="anchor" href="#Documentation/git-config.txt-coreuntrackedCache"></a>core.untrackedCache </dt>
+<dd>
+<p>Determines what to do about the untracked cache feature of the
+index. It will be kept, if this variable is unset or set to
+<code>keep</code>. It will automatically be added if set to <code>true</code>. And
+it will automatically be removed, if set to <code>false</code>. Before
+setting it to <code>true</code>, you should check that mtime is working
+properly on your system.
+See <a href='{{< relurl "docs/git-update-index" >}}'>git-update-index[1]</a>. <code>keep</code> by default, unless
+<code>feature.manyFiles</code> is enabled which sets this setting to
+<code>true</code> by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corecheckStat"> <a class="anchor" href="#Documentation/git-config.txt-corecheckStat"></a>core.checkStat </dt>
+<dd>
+<p>When missing or is set to <code>default</code>, many fields in the stat
+structure are checked to detect if a file has been modified
+since Git looked at it.  When this configuration variable is
+set to <code>minimal</code>, sub-second part of mtime and ctime, the
+uid and gid of the owner of the file, the inode number (and
+the device number, if Git was compiled to use it), are
+excluded from the check among these fields, leaving only the
+whole-second part of mtime (and ctime, if <code>core.trustCtime</code>
+is set) and the filesize to be checked.</p>
+<div class="paragraph">
+<p>There are implementations of Git that do not leave usable values in
+some fields (e.g. JGit); by excluding these fields from the
+comparison, the <code>minimal</code> mode may help interoperability when the
+same repository is used by these other systems at the same time.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corequotePath"> <a class="anchor" href="#Documentation/git-config.txt-corequotePath"></a>core.quotePath </dt>
+<dd>
+<p>Commands that output paths (e.g. <em>ls-files</em>, <em>diff</em>), will
+quote "unusual" characters in the pathname by enclosing the
+pathname in double-quotes and escaping those characters with
+backslashes in the same way C escapes control characters (e.g.
+<code>\t</code> for TAB, <code>\n</code> for LF, <code>\\</code> for backslash) or bytes with
+values larger than 0x80 (e.g. octal <code>\302\265</code> for "micro" in
+UTF-8).  If this variable is set to false, bytes higher than
+0x80 are not considered "unusual" any more. Double-quotes,
+backslash and control characters are always escaped regardless
+of the setting of this variable.  A simple space character is
+not considered "unusual".  Many commands can output pathnames
+completely verbatim using the <code>-z</code> option. The default value
+is true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreeol"> <a class="anchor" href="#Documentation/git-config.txt-coreeol"></a>core.eol </dt>
+<dd>
+<p>Sets the line ending type to use in the working directory for
+files that are marked as text (either by having the <code>text</code>
+attribute set, or by having <code>text=auto</code> and Git auto-detecting
+the contents as text).
+Alternatives are <em>lf</em>, <em>crlf</em> and <em>native</em>, which uses the platform&#8217;s
+native line ending.  The default value is <code>native</code>.  See
+<a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for more information on end-of-line
+conversion. Note that this value is ignored if <code>core.autocrlf</code>
+is set to <code>true</code> or <code>input</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coresafecrlf"> <a class="anchor" href="#Documentation/git-config.txt-coresafecrlf"></a>core.safecrlf </dt>
+<dd>
+<p>If true, makes Git check if converting <code>CRLF</code> is reversible when
+end-of-line conversion is active.  Git will verify if a command
+modifies a file in the work tree either directly or indirectly.
+For example, committing a file followed by checking out the
+same file should yield the original file in the work tree.  If
+this is not the case for the current setting of
+<code>core.autocrlf</code>, Git will reject the file.  The variable can
+be set to "warn", in which case Git will only warn about an
+irreversible conversion but continue the operation.</p>
+<div class="paragraph">
+<p>CRLF conversion bears a slight chance of corrupting data.
+When it is enabled, Git will convert CRLF to LF during commit and LF to
+CRLF during checkout.  A file that contains a mixture of LF and
+CRLF before the commit cannot be recreated by Git.  For text
+files this is the right thing to do: it corrects line endings
+such that we have only LF line endings in the repository.
+But for binary files that are accidentally classified as text the
+conversion can corrupt data.</p>
+</div>
+<div class="paragraph">
+<p>If you recognize such corruption early you can easily fix it by
+setting the conversion type explicitly in .gitattributes.  Right
+after committing you still have the original file in your work
+tree and this file is not yet corrupted.  You can explicitly tell
+Git that this file is binary and Git will handle the file
+appropriately.</p>
+</div>
+<div class="paragraph">
+<p>Unfortunately, the desired effect of cleaning up text files with
+mixed line endings and the undesired effect of corrupting binary
+files cannot be distinguished.  In both cases CRLFs are removed
+in an irreversible way.  For text files this is the right thing
+to do because CRLFs are line endings, while for binary files
+converting CRLFs corrupts data.</p>
+</div>
+<div class="paragraph">
+<p>Note, this safety check does not mean that a checkout will generate a
+file identical to the original file for a different setting of
+<code>core.eol</code> and <code>core.autocrlf</code>, but only for the current one.  For
+example, a text file with <code>LF</code> would be accepted with <code>core.eol=lf</code>
+and could later be checked out with <code>core.eol=crlf</code>, in which case the
+resulting file would contain <code>CRLF</code>, although the original file
+contained <code>LF</code>.  However, in both work trees the line endings would be
+consistent, that is either all <code>LF</code> or all <code>CRLF</code>, but never mixed.  A
+file with mixed line endings would be reported by the <code>core.safecrlf</code>
+mechanism.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreautocrlf"> <a class="anchor" href="#Documentation/git-config.txt-coreautocrlf"></a>core.autocrlf </dt>
+<dd>
+<p>Setting this variable to "true" is the same as setting
+the <code>text</code> attribute to "auto" on all files and core.eol to "crlf".
+Set to true if you want to have <code>CRLF</code> line endings in your
+working directory and the repository has LF line endings.
+This variable can be set to <em>input</em>,
+in which case no output conversion is performed.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corecheckRoundtripEncoding"> <a class="anchor" href="#Documentation/git-config.txt-corecheckRoundtripEncoding"></a>core.checkRoundtripEncoding </dt>
+<dd>
+<p>A comma and/or whitespace separated list of encodings that Git
+performs UTF-8 round trip checks on if they are used in an
+<code>working-tree-encoding</code> attribute (see <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a>).
+The default value is <code>SHIFT-JIS</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coresymlinks"> <a class="anchor" href="#Documentation/git-config.txt-coresymlinks"></a>core.symlinks </dt>
+<dd>
+<p>If false, symbolic links are checked out as small plain files that
+contain the link text. <a href='{{< relurl "docs/git-update-index" >}}'>git-update-index[1]</a> and
+<a href='{{< relurl "docs/git-add" >}}'>git-add[1]</a> will not change the recorded type to regular
+file. Useful on filesystems like FAT that do not support
+symbolic links.</p>
+<div class="paragraph">
+<p>The default is true, except <a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a> or <a href='{{< relurl "docs/git-init" >}}'>git-init[1]</a>
+will probe and set core.symlinks false if appropriate when the repository
+is created.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coregitProxy"> <a class="anchor" href="#Documentation/git-config.txt-coregitProxy"></a>core.gitProxy </dt>
+<dd>
+<p>A "proxy command" to execute (as <em>command host port</em>) instead
+of establishing direct connection to the remote server when
+using the Git protocol for fetching. If the variable value is
+in the "COMMAND for DOMAIN" format, the command is applied only
+on hostnames ending with the specified domain string. This variable
+may be set multiple times and is matched in the given order;
+the first match wins.</p>
+<div class="paragraph">
+<p>Can be overridden by the <code>GIT_PROXY_COMMAND</code> environment variable
+(which always applies universally, without the special "for"
+handling).</p>
+</div>
+<div class="paragraph">
+<p>The special string <code>none</code> can be used as the proxy command to
+specify that no proxy be used for a given domain pattern.
+This is useful for excluding servers inside a firewall from
+proxy use, while defaulting to a common proxy for external domains.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coresshCommand"> <a class="anchor" href="#Documentation/git-config.txt-coresshCommand"></a>core.sshCommand </dt>
+<dd>
+<p>If this variable is set, <code>git fetch</code> and <code>git push</code> will
+use the specified command instead of <code>ssh</code> when they need to
+connect to a remote system. The command is in the same form as
+the <code>GIT_SSH_COMMAND</code> environment variable and is overridden
+when the environment variable is set.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreignoreStat"> <a class="anchor" href="#Documentation/git-config.txt-coreignoreStat"></a>core.ignoreStat </dt>
+<dd>
+<p>If true, Git will avoid using lstat() calls to detect if files have
+changed by setting the "assume-unchanged" bit for those tracked files
+which it has updated identically in both the index and working tree.</p>
+<div class="paragraph">
+<p>When files are modified outside of Git, the user will need to stage
+the modified files explicitly (e.g. see <em>Examples</em> section in
+<a href='{{< relurl "docs/git-update-index" >}}'>git-update-index[1]</a>).
+Git will not normally detect changes to those files.</p>
+</div>
+<div class="paragraph">
+<p>This is useful on systems where lstat() calls are very slow, such as
+CIFS/Microsoft Windows.</p>
+</div>
+<div class="paragraph">
+<p>False by default.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corepreferSymlinkRefs"> <a class="anchor" href="#Documentation/git-config.txt-corepreferSymlinkRefs"></a>core.preferSymlinkRefs </dt>
+<dd>
+<p>Instead of the default "symref" format for HEAD
+and other symbolic reference files, use symbolic links.
+This is sometimes needed to work with old scripts that
+expect HEAD to be a symbolic link.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corealternateRefsCommand"> <a class="anchor" href="#Documentation/git-config.txt-corealternateRefsCommand"></a>core.alternateRefsCommand </dt>
+<dd>
+<p>When advertising tips of available history from an alternate, use the shell to
+execute the specified command instead of <a href='{{< relurl "docs/git-for-each-ref" >}}'>git-for-each-ref[1]</a>. The
+first argument is the absolute path of the alternate. Output must contain one
+hex object id per line (i.e., the same as produced by <code>git for-each-ref
+--format='%(objectname)'</code>).</p>
+<div class="paragraph">
+<p>Note that you cannot generally put <code>git for-each-ref</code> directly into the config
+value, as it does not take a repository path as an argument (but you can wrap
+the command above in a shell script).</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corealternateRefsPrefixes"> <a class="anchor" href="#Documentation/git-config.txt-corealternateRefsPrefixes"></a>core.alternateRefsPrefixes </dt>
+<dd>
+<p>When listing references from an alternate, list only references that begin
+with the given prefix. Prefixes match as if they were given as arguments to
+<a href='{{< relurl "docs/git-for-each-ref" >}}'>git-for-each-ref[1]</a>. To list multiple prefixes, separate them with
+whitespace. If <code>core.alternateRefsCommand</code> is set, setting
+<code>core.alternateRefsPrefixes</code> has no effect.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corebare"> <a class="anchor" href="#Documentation/git-config.txt-corebare"></a>core.bare </dt>
+<dd>
+<p>If true this repository is assumed to be <em>bare</em> and has no
+working directory associated with it.  If this is the case a
+number of commands that require a working directory will be
+disabled, such as <a href='{{< relurl "docs/git-add" >}}'>git-add[1]</a> or <a href='{{< relurl "docs/git-merge" >}}'>git-merge[1]</a>.</p>
+<div class="paragraph">
+<p>This setting is automatically guessed by <a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a> or
+<a href='{{< relurl "docs/git-init" >}}'>git-init[1]</a> when the repository was created.  By default a
+repository that ends in "/.git" is assumed to be not bare (bare =
+false), while all other repositories are assumed to be bare (bare
+= true).</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreworktree"> <a class="anchor" href="#Documentation/git-config.txt-coreworktree"></a>core.worktree </dt>
+<dd>
+<p>Set the path to the root of the working tree.
+If <code>GIT_COMMON_DIR</code> environment variable is set, core.worktree
+is ignored and not used for determining the root of working tree.
+This can be overridden by the <code>GIT_WORK_TREE</code> environment
+variable and the <code>--work-tree</code> command-line option.
+The value can be an absolute path or relative to the path to
+the .git directory, which is either specified by --git-dir
+or GIT_DIR, or automatically discovered.
+If --git-dir or GIT_DIR is specified but none of
+--work-tree, GIT_WORK_TREE and core.worktree is specified,
+the current working directory is regarded as the top level
+of your working tree.</p>
+<div class="paragraph">
+<p>Note that this variable is honored even when set in a configuration
+file in a ".git" subdirectory of a directory and its value differs
+from the latter directory (e.g. "/path/to/.git/config" has
+core.worktree set to "/different/path"), which is most likely a
+misconfiguration.  Running Git commands in the "/path/to" directory will
+still use "/different/path" as the root of the work tree and can cause
+confusion unless you know what you are doing (e.g. you are creating a
+read-only snapshot of the same index to a location different from the
+repository&#8217;s usual working tree).</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corelogAllRefUpdates"> <a class="anchor" href="#Documentation/git-config.txt-corelogAllRefUpdates"></a>core.logAllRefUpdates </dt>
+<dd>
+<p>Enable the reflog. Updates to a ref &lt;ref&gt; is logged to the file
+"<code>$GIT_DIR/logs/&lt;ref&gt;</code>", by appending the new and old
+SHA-1, the date/time and the reason of the update, but
+only when the file exists.  If this configuration
+variable is set to <code>true</code>, missing "<code>$GIT_DIR/logs/&lt;ref&gt;</code>"
+file is automatically created for branch heads (i.e. under
+<code>refs/heads/</code>), remote refs (i.e. under <code>refs/remotes/</code>),
+note refs (i.e. under <code>refs/notes/</code>), and the symbolic ref <code>HEAD</code>.
+If it is set to <code>always</code>, then a missing reflog is automatically
+created for any ref under <code>refs/</code>.</p>
+<div class="paragraph">
+<p>This information can be used to determine what commit
+was the tip of a branch "2 days ago".</p>
+</div>
+<div class="paragraph">
+<p>This value is true by default in a repository that has
+a working directory associated with it, and false by
+default in a bare repository.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corerepositoryFormatVersion"> <a class="anchor" href="#Documentation/git-config.txt-corerepositoryFormatVersion"></a>core.repositoryFormatVersion </dt>
+<dd>
+<p>Internal variable identifying the repository format and layout
+version.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coresharedRepository"> <a class="anchor" href="#Documentation/git-config.txt-coresharedRepository"></a>core.sharedRepository </dt>
+<dd>
+<p>When <em>group</em> (or <em>true</em>), the repository is made shareable between
+several users in a group (making sure all the files and objects are
+group-writable). When <em>all</em> (or <em>world</em> or <em>everybody</em>), the
+repository will be readable by all users, additionally to being
+group-shareable. When <em>umask</em> (or <em>false</em>), Git will use permissions
+reported by umask(2). When <em>0xxx</em>, where <em>0xxx</em> is an octal number,
+files in the repository will have this mode value. <em>0xxx</em> will override
+user&#8217;s umask value (whereas the other options will only override
+requested parts of the user&#8217;s umask value). Examples: <em>0660</em> will make
+the repo read/write-able for the owner and group, but inaccessible to
+others (equivalent to <em>group</em> unless umask is e.g. <em>0022</em>). <em>0640</em> is a
+repository that is group-readable but not group-writable.
+See <a href='{{< relurl "docs/git-init" >}}'>git-init[1]</a>. False by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corewarnAmbiguousRefs"> <a class="anchor" href="#Documentation/git-config.txt-corewarnAmbiguousRefs"></a>core.warnAmbiguousRefs </dt>
+<dd>
+<p>If true, Git will warn you if the ref name you passed it is ambiguous
+and might match multiple refs in the repository. True by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corecompression"> <a class="anchor" href="#Documentation/git-config.txt-corecompression"></a>core.compression </dt>
+<dd>
+<p>An integer -1..9, indicating a default compression level.
+-1 is the zlib default. 0 means no compression,
+and 1..9 are various speed/size tradeoffs, 9 being slowest.
+If set, this provides a default to other compression variables,
+such as <code>core.looseCompression</code> and <code>pack.compression</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corelooseCompression"> <a class="anchor" href="#Documentation/git-config.txt-corelooseCompression"></a>core.looseCompression </dt>
+<dd>
+<p>An integer -1..9, indicating the compression level for objects that
+are not in a pack file. -1 is the zlib default. 0 means no
+compression, and 1..9 are various speed/size tradeoffs, 9 being
+slowest.  If not set,  defaults to core.compression.  If that is
+not set,  defaults to 1 (best speed).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corepackedGitWindowSize"> <a class="anchor" href="#Documentation/git-config.txt-corepackedGitWindowSize"></a>core.packedGitWindowSize </dt>
+<dd>
+<p>Number of bytes of a pack file to map into memory in a
+single mapping operation.  Larger window sizes may allow
+your system to process a smaller number of large pack files
+more quickly.  Smaller window sizes will negatively affect
+performance due to increased calls to the operating system&#8217;s
+memory manager, but may improve performance when accessing
+a large number of large pack files.</p>
+<div class="paragraph">
+<p>Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
+MiB on 32 bit platforms and 1 GiB on 64 bit platforms.  This should
+be reasonable for all users/operating systems.  You probably do
+not need to adjust this value.</p>
+</div>
+<div class="paragraph">
+<p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corepackedGitLimit"> <a class="anchor" href="#Documentation/git-config.txt-corepackedGitLimit"></a>core.packedGitLimit </dt>
+<dd>
+<p>Maximum number of bytes to map simultaneously into memory
+from pack files.  If Git needs to access more than this many
+bytes at once to complete an operation it will unmap existing
+regions to reclaim virtual address space within the process.</p>
+<div class="paragraph">
+<p>Default is 256 MiB on 32 bit platforms and 32 TiB (effectively
+unlimited) on 64 bit platforms.
+This should be reasonable for all users/operating systems, except on
+the largest projects.  You probably do not need to adjust this value.</p>
+</div>
+<div class="paragraph">
+<p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coredeltaBaseCacheLimit"> <a class="anchor" href="#Documentation/git-config.txt-coredeltaBaseCacheLimit"></a>core.deltaBaseCacheLimit </dt>
+<dd>
+<p>Maximum number of bytes per thread to reserve for caching base objects
+that may be referenced by multiple deltified objects.  By storing the
+entire decompressed base objects in a cache Git is able
+to avoid unpacking and decompressing frequently used base
+objects multiple times.</p>
+<div class="paragraph">
+<p>Default is 96 MiB on all platforms.  This should be reasonable
+for all users/operating systems, except on the largest projects.
+You probably do not need to adjust this value.</p>
+</div>
+<div class="paragraph">
+<p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corebigFileThreshold"> <a class="anchor" href="#Documentation/git-config.txt-corebigFileThreshold"></a>core.bigFileThreshold </dt>
+<dd>
+<p>The size of files considered "big", which as discussed below
+changes the behavior of numerous git commands, as well as how
+such files are stored within the repository. The default is
+512 MiB. Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are
+supported.</p>
+<div class="paragraph">
+<p>Files above the configured limit will be:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Stored deflated in packfiles, without attempting delta compression.</p>
+<div class="paragraph">
+<p>The default limit is primarily set with this use-case in mind. With it,
+most projects will have their source code and other text files delta
+compressed, but not larger binary media files.</p>
+</div>
+<div class="paragraph">
+<p>Storing large files without delta compression avoids excessive memory
+usage, at the slight expense of increased disk usage.</p>
+</div>
+</li>
+<li>
+<p>Will be treated as if they were labeled "binary" (see
+<a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a>). e.g. <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a> and
+<a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a> will not compute diffs for files above this limit.</p>
+</li>
+<li>
+<p>Will generally be streamed when written, which avoids excessive
+memory usage, at the cost of some fixed overhead. Commands that make
+use of this include <a href='{{< relurl "docs/git-archive" >}}'>git-archive[1]</a>,
+<a href='{{< relurl "docs/git-fast-import" >}}'>git-fast-import[1]</a>, <a href='{{< relurl "docs/git-index-pack" >}}'>git-index-pack[1]</a>,
+<a href='{{< relurl "docs/git-unpack-objects" >}}'>git-unpack-objects[1]</a> and <a href='{{< relurl "docs/git-fsck" >}}'>git-fsck[1]</a>.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreexcludesFile"> <a class="anchor" href="#Documentation/git-config.txt-coreexcludesFile"></a>core.excludesFile </dt>
+<dd>
+<p>Specifies the pathname to the file that contains patterns to
+describe paths that are not meant to be tracked, in addition
+to <code>.gitignore</code> (per-directory) and <code>.git/info/exclude</code>.
+Defaults to <code>$XDG_CONFIG_HOME/git/ignore</code>.
+If <code>$XDG_CONFIG_HOME</code> is either not set or empty, <code>$HOME/.config/git/ignore</code>
+is used instead. See <a href='{{< relurl "docs/gitignore" >}}'>gitignore[5]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreaskPass"> <a class="anchor" href="#Documentation/git-config.txt-coreaskPass"></a>core.askPass </dt>
+<dd>
+<p>Some commands (e.g. svn and http interfaces) that interactively
+ask for a password can be told to use an external program given
+via the value of this variable. Can be overridden by the <code>GIT_ASKPASS</code>
+environment variable. If not set, fall back to the value of the
+<code>SSH_ASKPASS</code> environment variable or, failing that, a simple password
+prompt. The external program shall be given a suitable prompt as
+command-line argument and write the password on its STDOUT.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreattributesFile"> <a class="anchor" href="#Documentation/git-config.txt-coreattributesFile"></a>core.attributesFile </dt>
+<dd>
+<p>In addition to <code>.gitattributes</code> (per-directory) and
+<code>.git/info/attributes</code>, Git looks into this file for attributes
+(see <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a>). Path expansions are made the same
+way as for <code>core.excludesFile</code>. Its default value is
+<code>$XDG_CONFIG_HOME/git/attributes</code>. If <code>$XDG_CONFIG_HOME</code> is either not
+set or empty, <code>$HOME/.config/git/attributes</code> is used instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corehooksPath"> <a class="anchor" href="#Documentation/git-config.txt-corehooksPath"></a>core.hooksPath </dt>
+<dd>
+<p>By default Git will look for your hooks in the
+<code>$GIT_DIR/hooks</code> directory. Set this to different path,
+e.g. <code>/etc/git/hooks</code>, and Git will try to find your hooks in
+that directory, e.g. <code>/etc/git/hooks/pre-receive</code> instead of
+in <code>$GIT_DIR/hooks/pre-receive</code>.</p>
+<div class="paragraph">
+<p>The path can be either absolute or relative. A relative path is
+taken as relative to the directory where the hooks are run (see
+the "DESCRIPTION" section of <a href='{{< relurl "docs/githooks" >}}'>githooks[5]</a>).</p>
+</div>
+<div class="paragraph">
+<p>This configuration variable is useful in cases where you&#8217;d like to
+centrally configure your Git hooks instead of configuring them on a
+per-repository basis, or as a more flexible and centralized
+alternative to having an <code>init.templateDir</code> where you&#8217;ve changed
+default hooks.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreeditor"> <a class="anchor" href="#Documentation/git-config.txt-coreeditor"></a>core.editor </dt>
+<dd>
+<p>Commands such as <code>commit</code> and <code>tag</code> that let you edit
+messages by launching an editor use the value of this
+variable when it is set, and the environment variable
+<code>GIT_EDITOR</code> is not set.  See <a href='{{< relurl "docs/git-var" >}}'>git-var[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corecommentChar"> <a class="anchor" href="#Documentation/git-config.txt-corecommentChar"></a>core.commentChar </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-corecommentString"> <a class="anchor" href="#Documentation/git-config.txt-corecommentString"></a>core.commentString </dt>
+<dd>
+<p>Commands such as <code>commit</code> and <code>tag</code> that let you edit
+messages consider a line that begins with this character
+commented, and removes them after the editor returns
+(default <em>#</em>).</p>
+<div class="paragraph">
+<p>If set to "auto", <code>git-commit</code> would select a character that is not
+the beginning character of any line in existing commit messages.</p>
+</div>
+<div class="paragraph">
+<p>Note that these two variables are aliases of each other, and in modern
+versions of Git you are free to use a string (e.g., <code>//</code> or <code>⁑⁕⁑</code>) with
+<code>commentChar</code>. Versions of Git prior to v2.45.0 will ignore
+<code>commentString</code> but will reject a value of <code>commentChar</code> that consists
+of more than a single ASCII byte. If you plan to use your config with
+older and newer versions of Git, you may want to specify both:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>[core]
+# single character for older versions
+commentChar = "#"
+# string for newer versions (which will override commentChar
+# because it comes later in the file)
+commentString = "//"</pre>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corefilesRefLockTimeout"> <a class="anchor" href="#Documentation/git-config.txt-corefilesRefLockTimeout"></a>core.filesRefLockTimeout </dt>
+<dd>
+<p>The length of time, in milliseconds, to retry when trying to
+lock an individual reference. Value 0 means not to retry at
+all; -1 means to try indefinitely. Default is 100 (i.e.,
+retry for 100ms).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corepackedRefsTimeout"> <a class="anchor" href="#Documentation/git-config.txt-corepackedRefsTimeout"></a>core.packedRefsTimeout </dt>
+<dd>
+<p>The length of time, in milliseconds, to retry when trying to
+lock the <code>packed-refs</code> file. Value 0 means not to retry at
+all; -1 means to try indefinitely. Default is 1000 (i.e.,
+retry for 1 second).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corepager"> <a class="anchor" href="#Documentation/git-config.txt-corepager"></a>core.pager </dt>
+<dd>
+<p>Text viewer for use by Git commands (e.g., <em>less</em>).  The value
+is meant to be interpreted by the shell.  The order of preference
+is the <code>$GIT_PAGER</code> environment variable, then <code>core.pager</code>
+configuration, then <code>$PAGER</code>, and then the default chosen at
+compile time (usually <em>less</em>).</p>
+<div class="paragraph">
+<p>When the <code>LESS</code> environment variable is unset, Git sets it to <code>FRX</code>
+(if <code>LESS</code> environment variable is set, Git does not change it at
+all).  If you want to selectively override Git&#8217;s default setting
+for <code>LESS</code>, you can set <code>core.pager</code> to e.g. <code>less -S</code>.  This will
+be passed to the shell by Git, which will translate the final
+command to <code>LESS=FRX less -S</code>. The environment does not set the
+<code>S</code> option but the command line does, instructing less to truncate
+long lines. Similarly, setting <code>core.pager</code> to <code>less -+F</code> will
+deactivate the <code>F</code> option specified by the environment from the
+command-line, deactivating the "quit if one screen" behavior of
+<code>less</code>.  One can specifically activate some flags for particular
+commands: for example, setting <code>pager.blame</code> to <code>less -S</code> enables
+line truncation only for <code>git blame</code>.</p>
+</div>
+<div class="paragraph">
+<p>Likewise, when the <code>LV</code> environment variable is unset, Git sets it
+to <code>-c</code>.  You can override this setting by exporting <code>LV</code> with
+another value or setting <code>core.pager</code> to <code>lv +c</code>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corewhitespace"> <a class="anchor" href="#Documentation/git-config.txt-corewhitespace"></a>core.whitespace </dt>
+<dd>
+<p>A comma separated list of common whitespace problems to
+notice.  <em>git diff</em> will use <code>color.diff.whitespace</code> to
+highlight them, and <em>git apply --whitespace=error</em> will
+consider them as errors.  You can prefix <code>-</code> to disable
+any of them (e.g. <code>-trailing-space</code>):</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>blank-at-eol</code> treats trailing whitespaces at the end of the line
+as an error (enabled by default).</p>
+</li>
+<li>
+<p><code>space-before-tab</code> treats a space character that appears immediately
+before a tab character in the initial indent part of the line as an
+error (enabled by default).</p>
+</li>
+<li>
+<p><code>indent-with-non-tab</code> treats a line that is indented with space
+characters instead of the equivalent tabs as an error (not enabled by
+default).</p>
+</li>
+<li>
+<p><code>tab-in-indent</code> treats a tab character in the initial indent part of
+the line as an error (not enabled by default).</p>
+</li>
+<li>
+<p><code>blank-at-eof</code> treats blank lines added at the end of file as an error
+(enabled by default).</p>
+</li>
+<li>
+<p><code>trailing-space</code> is a short-hand to cover both <code>blank-at-eol</code> and
+<code>blank-at-eof</code>.</p>
+</li>
+<li>
+<p><code>cr-at-eol</code> treats a carriage-return at the end of line as
+part of the line terminator, i.e. with it, <code>trailing-space</code>
+does not trigger if the character before such a carriage-return
+is not a whitespace (not enabled by default).</p>
+</li>
+<li>
+<p><code>tabwidth=&lt;n&gt;</code> tells how many character positions a tab occupies; this
+is relevant for <code>indent-with-non-tab</code> and when Git fixes <code>tab-in-indent</code>
+errors. The default tab width is 8. Allowed values are 1 to 63.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corefsync"> <a class="anchor" href="#Documentation/git-config.txt-corefsync"></a>core.fsync </dt>
+<dd>
+<p>A comma-separated list of components of the repository that
+should be hardened via the core.fsyncMethod when created or
+modified.  You can disable hardening of any component by
+prefixing it with a <em>-</em>.  Items that are not hardened may be
+lost in the event of an unclean	system shutdown. Unless you
+have special requirements, it is recommended that you leave
+this option empty or pick one of <code>committed</code>, <code>added</code>,
+or <code>all</code>.</p>
+<div class="paragraph">
+<p>When this configuration is encountered, the set of components starts with
+the platform default value, disabled components are removed, and additional
+components are added. <code>none</code> resets the state so that the platform default
+is ignored.</p>
+</div>
+<div class="paragraph">
+<p>The empty string resets the fsync configuration to the platform
+default. The default on most platforms is equivalent to
+<code>core.fsync=committed,-loose-object</code>, which has good performance,
+but risks losing recent work in the event of an unclean system shutdown.</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>none</code> clears the set of fsynced components.</p>
+</li>
+<li>
+<p><code>loose-object</code> hardens objects added to the repo in loose-object form.</p>
+</li>
+<li>
+<p><code>pack</code> hardens objects added to the repo in packfile form.</p>
+</li>
+<li>
+<p><code>pack-metadata</code> hardens packfile bitmaps and indexes.</p>
+</li>
+<li>
+<p><code>commit-graph</code> hardens the commit-graph file.</p>
+</li>
+<li>
+<p><code>index</code> hardens the index when it is modified.</p>
+</li>
+<li>
+<p><code>objects</code> is an aggregate option that is equivalent to
+<code>loose-object,pack</code>.</p>
+</li>
+<li>
+<p><code>reference</code> hardens references modified in the repo.</p>
+</li>
+<li>
+<p><code>derived-metadata</code> is an aggregate option that is equivalent to
+<code>pack-metadata,commit-graph</code>.</p>
+</li>
+<li>
+<p><code>committed</code> is an aggregate option that is currently equivalent to
+<code>objects</code>. This mode sacrifices some performance to ensure that work
+that is committed to the repository with <code>git commit</code> or similar commands
+is hardened.</p>
+</li>
+<li>
+<p><code>added</code> is an aggregate option that is currently equivalent to
+<code>committed,index</code>. This mode sacrifices additional performance to
+ensure that the results of commands like <code>git add</code> and similar operations
+are hardened.</p>
+</li>
+<li>
+<p><code>all</code> is an aggregate option that syncs all individual components above.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corefsyncMethod"> <a class="anchor" href="#Documentation/git-config.txt-corefsyncMethod"></a>core.fsyncMethod </dt>
+<dd>
+<p>A value indicating the strategy Git will use to harden repository data
+using fsync and related primitives.</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>fsync</code> uses the fsync() system call or platform equivalents.</p>
+</li>
+<li>
+<p><code>writeout-only</code> issues pagecache writeback requests, but depending on the
+filesystem and storage hardware, data added to the repository may not be
+durable in the event of a system crash. This is the default mode on macOS.</p>
+</li>
+<li>
+<p><code>batch</code> enables a mode that uses writeout-only flushes to stage multiple
+updates in the disk writeback cache and then does a single full fsync of
+a dummy file to trigger the disk cache flush at the end of the operation.</p>
+<div class="paragraph">
+<p>Currently <code>batch</code> mode only applies to loose-object files. Other repository
+data is made durable as if <code>fsync</code> was specified. This mode is expected to
+be as safe as <code>fsync</code> on macOS for repos stored on HFS+ or APFS filesystems
+and on Windows for repos stored on NTFS or ReFS filesystems.</p>
+</div>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corefsyncObjectFiles"> <a class="anchor" href="#Documentation/git-config.txt-corefsyncObjectFiles"></a>core.fsyncObjectFiles </dt>
+<dd>
+<p>This boolean will enable <em>fsync()</em> when writing object files.
+This setting is deprecated. Use core.fsync instead.</p>
+<div class="paragraph">
+<p>This setting affects data added to the Git repository in loose-object
+form. When set to true, Git will issue an fsync or similar system call
+to flush caches so that loose-objects remain consistent in the face
+of a unclean system shutdown.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corepreloadIndex"> <a class="anchor" href="#Documentation/git-config.txt-corepreloadIndex"></a>core.preloadIndex </dt>
+<dd>
+<p>Enable parallel index preload for operations like <em>git diff</em></p>
+<div class="paragraph">
+<p>This can speed up operations like <em>git diff</em> and <em>git status</em> especially
+on filesystems like NFS that have weak caching semantics and thus
+relatively high IO latencies.  When enabled, Git will do the
+index comparison to the filesystem data in parallel, allowing
+overlapping IO&#8217;s.  Defaults to true.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreunsetenvvars"> <a class="anchor" href="#Documentation/git-config.txt-coreunsetenvvars"></a>core.unsetenvvars </dt>
+<dd>
+<p>Windows-only: comma-separated list of environment variables'
+names that need to be unset before spawning any other process.
+Defaults to <code>PERL5LIB</code> to account for the fact that Git for
+Windows insists on using its own Perl interpreter.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corerestrictinheritedhandles"> <a class="anchor" href="#Documentation/git-config.txt-corerestrictinheritedhandles"></a>core.restrictinheritedhandles </dt>
+<dd>
+<p>Windows-only: override whether spawned processes inherit only standard
+file handles (<code>stdin</code>, <code>stdout</code> and <code>stderr</code>) or all handles. Can be
+<code>auto</code>, <code>true</code> or <code>false</code>. Defaults to <code>auto</code>, which means <code>true</code> on
+Windows 7 and later, and <code>false</code> on older Windows versions.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corecreateObject"> <a class="anchor" href="#Documentation/git-config.txt-corecreateObject"></a>core.createObject </dt>
+<dd>
+<p>You can set this to <em>link</em>, in which case a hardlink followed by
+a delete of the source are used to make sure that object creation
+will not overwrite existing objects.</p>
+<div class="paragraph">
+<p>On some file system/operating system combinations, this is unreliable.
+Set this config setting to <em>rename</em> there; however, this will remove the
+check that makes sure that existing object files will not get overwritten.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corenotesRef"> <a class="anchor" href="#Documentation/git-config.txt-corenotesRef"></a>core.notesRef </dt>
+<dd>
+<p>When showing commit messages, also show notes which are stored in
+the given ref.  The ref must be fully qualified.  If the given
+ref does not exist, it is not an error but means that no
+notes should be printed.</p>
+<div class="paragraph">
+<p>This setting defaults to "refs/notes/commits", and it can be overridden by
+the <code>GIT_NOTES_REF</code> environment variable.  See <a href='{{< relurl "docs/git-notes" >}}'>git-notes[1]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-corecommitGraph"> <a class="anchor" href="#Documentation/git-config.txt-corecommitGraph"></a>core.commitGraph </dt>
+<dd>
+<p>If true, then git will read the commit-graph file (if it exists)
+to parse the graph structure of commits. Defaults to true. See
+<a href='{{< relurl "docs/git-commit-graph" >}}'>git-commit-graph[1]</a> for more information.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreuseReplaceRefs"> <a class="anchor" href="#Documentation/git-config.txt-coreuseReplaceRefs"></a>core.useReplaceRefs </dt>
+<dd>
+<p>If set to <code>false</code>, behave as if the <code>--no-replace-objects</code>
+option was given on the command line. See <a href='{{< relurl "docs/git" >}}'>git[1]</a> and
+<a href='{{< relurl "docs/git-replace" >}}'>git-replace[1]</a> for more information.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coremultiPackIndex"> <a class="anchor" href="#Documentation/git-config.txt-coremultiPackIndex"></a>core.multiPackIndex </dt>
+<dd>
+<p>Use the multi-pack-index file to track multiple packfiles using a
+single index. See <a href='{{< relurl "docs/git-multi-pack-index" >}}'>git-multi-pack-index[1]</a> for more
+information. Defaults to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coresparseCheckout"> <a class="anchor" href="#Documentation/git-config.txt-coresparseCheckout"></a>core.sparseCheckout </dt>
+<dd>
+<p>Enable "sparse checkout" feature. See <a href='{{< relurl "docs/git-sparse-checkout" >}}'>git-sparse-checkout[1]</a>
+for more information.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coresparseCheckoutCone"> <a class="anchor" href="#Documentation/git-config.txt-coresparseCheckoutCone"></a>core.sparseCheckoutCone </dt>
+<dd>
+<p>Enables the "cone mode" of the sparse checkout feature. When the
+sparse-checkout file contains a limited set of patterns, this
+mode provides significant performance advantages. The "non-cone
+mode" can be requested to allow specifying more flexible
+patterns by setting this variable to <em>false</em>. See
+<a href='{{< relurl "docs/git-sparse-checkout" >}}'>git-sparse-checkout[1]</a> for more information.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coreabbrev"> <a class="anchor" href="#Documentation/git-config.txt-coreabbrev"></a>core.abbrev </dt>
+<dd>
+<p>Set the length object names are abbreviated to.  If
+unspecified or set to "auto", an appropriate value is
+computed based on the approximate number of packed objects
+in your repository, which hopefully is enough for
+abbreviated object names to stay unique for some time.
+If set to "no", no abbreviation is made and the object names
+are shown in their full length.
+The minimum length is 4.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-coremaxTreeDepth"> <a class="anchor" href="#Documentation/git-config.txt-coremaxTreeDepth"></a>core.maxTreeDepth </dt>
+<dd>
+<p>The maximum depth Git is willing to recurse while traversing a
+tree (e.g., "a/b/cde/f" has a depth of 4). This is a fail-safe
+to allow Git to abort cleanly, and should not generally need to
+be adjusted. When Git is compiled with MSVC, the default is 512.
+Otherwise, the default is 2048.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-credentialhelper"> <a class="anchor" href="#Documentation/git-config.txt-credentialhelper"></a>credential.helper </dt>
+<dd>
+<p>Specify an external helper to be called when a username or
+password credential is needed; the helper may consult external
+storage to avoid prompting the user for the credentials. This is
+normally the name of a credential helper with possible
+arguments, but may also be an absolute path with arguments or, if
+preceded by <code>!</code>, shell commands.</p>
+<div class="paragraph">
+<p>Note that multiple helpers may be defined. See <a href='{{< relurl "docs/gitcredentials" >}}'>gitcredentials[7]</a>
+for details and examples.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-credentialuseHttpPath"> <a class="anchor" href="#Documentation/git-config.txt-credentialuseHttpPath"></a>credential.useHttpPath </dt>
+<dd>
+<p>When acquiring credentials, consider the "path" component of an http
+or https URL to be important. Defaults to false. See
+<a href='{{< relurl "docs/gitcredentials" >}}'>gitcredentials[7]</a> for more information.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-credentialusername"> <a class="anchor" href="#Documentation/git-config.txt-credentialusername"></a>credential.username </dt>
+<dd>
+<p>If no username is set for a network authentication, use this username
+by default. See credential.&lt;context&gt;.* below, and
+<a href='{{< relurl "docs/gitcredentials" >}}'>gitcredentials[7]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-credentiallturlgt"> <a class="anchor" href="#Documentation/git-config.txt-credentiallturlgt"></a>credential.&lt;url&gt;.* </dt>
+<dd>
+<p>Any of the credential.* options above can be applied selectively to
+some credentials. For example, "credential.https://example.com.username"
+would set the default username only for https connections to
+example.com. See <a href='{{< relurl "docs/gitcredentials" >}}'>gitcredentials[7]</a> for details on how URLs are
+matched.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-credentialCacheignoreSIGHUP"> <a class="anchor" href="#Documentation/git-config.txt-credentialCacheignoreSIGHUP"></a>credentialCache.ignoreSIGHUP </dt>
+<dd>
+<p>Tell git-credential-cache&#8212;&#8203;daemon to ignore SIGHUP, instead of quitting.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-credentialStorelockTimeoutMS"> <a class="anchor" href="#Documentation/git-config.txt-credentialStorelockTimeoutMS"></a>credentialStore.lockTimeoutMS </dt>
+<dd>
+<p>The length of time, in milliseconds, for git-credential-store to retry
+when trying to lock the credentials file. A value of 0 means not to retry at
+all; -1 means to try indefinitely. Default is 1000 (i.e., retry for
+1s).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffautoRefreshIndex"> <a class="anchor" href="#Documentation/git-config.txt-diffautoRefreshIndex"></a>diff.autoRefreshIndex </dt>
+<dd>
+<p>When using <em>git diff</em> to compare with work tree
+files, do not consider stat-only changes as changed.
+Instead, silently run <code>git update-index --refresh</code> to
+update the cached stat information for paths whose
+contents in the work tree match the contents in the
+index.  This option defaults to true.  Note that this
+affects only <em>git diff</em> Porcelain, and not lower level
+<em>diff</em> commands such as <em>git diff-files</em>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffdirstat"> <a class="anchor" href="#Documentation/git-config.txt-diffdirstat"></a>diff.dirstat </dt>
+<dd>
+<p>A comma separated list of <code>--dirstat</code> parameters specifying the
+default behavior of the <code>--dirstat</code> option to <a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a>
+and friends. The defaults can be overridden on the command line
+(using <code>--dirstat=&lt;param1,param2,...&gt;</code>). The fallback defaults
+(when not changed by <code>diff.dirstat</code>) are <code>changes,noncumulative,3</code>.
+The following parameters are available:</p>
+<div class="openblock">
+<div class="content">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-codechangescode"> <a class="anchor" href="#Documentation/git-config.txt-codechangescode"></a><code>changes</code> </dt>
+<dd>
+<p>Compute the dirstat numbers by counting the lines that have been
+removed from the source, or added to the destination. This ignores
+the amount of pure code movements within a file.  In other words,
+rearranging lines in a file is not counted as much as other changes.
+This is the default behavior when no parameter is given.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codelinescode"> <a class="anchor" href="#Documentation/git-config.txt-codelinescode"></a><code>lines</code> </dt>
+<dd>
+<p>Compute the dirstat numbers by doing the regular line-based diff
+analysis, and summing the removed/added line counts. (For binary
+files, count 64-byte chunks instead, since binary files have no
+natural concept of lines). This is a more expensive <code>--dirstat</code>
+behavior than the <code>changes</code> behavior, but it does count rearranged
+lines within a file as much as other changes. The resulting output
+is consistent with what you get from the other <code>--*stat</code> options.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codefilescode"> <a class="anchor" href="#Documentation/git-config.txt-codefilescode"></a><code>files</code> </dt>
+<dd>
+<p>Compute the dirstat numbers by counting the number of files changed.
+Each changed file counts equally in the dirstat analysis. This is
+the computationally cheapest <code>--dirstat</code> behavior, since it does
+not have to look at the file contents at all.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codecumulativecode"> <a class="anchor" href="#Documentation/git-config.txt-codecumulativecode"></a><code>cumulative</code> </dt>
+<dd>
+<p>Count changes in a child directory for the parent directory as well.
+Note that when using <code>cumulative</code>, the sum of the percentages
+reported may exceed 100%. The default (non-cumulative) behavior can
+be specified with the <code>noncumulative</code> parameter.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-ltlimitgt"> <a class="anchor" href="#Documentation/git-config.txt-ltlimitgt"></a>&lt;limit&gt; </dt>
+<dd>
+<p>An integer parameter specifies a cut-off percent (3% by default).
+Directories contributing less than this percentage of the changes
+are not shown in the output.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Example: The following will count changed files, while ignoring
+directories with less than 10% of the total amount of changed files,
+and accumulating child directory counts in the parent directories:
+<code>files,10,cumulative</code>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffstatNameWidth"> <a class="anchor" href="#Documentation/git-config.txt-diffstatNameWidth"></a>diff.statNameWidth </dt>
+<dd>
+<p>Limit the width of the filename part in --stat output. If set, applies
+to all commands generating --stat output except format-patch.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffstatGraphWidth"> <a class="anchor" href="#Documentation/git-config.txt-diffstatGraphWidth"></a>diff.statGraphWidth </dt>
+<dd>
+<p>Limit the width of the graph part in --stat output. If set, applies
+to all commands generating --stat output except format-patch.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffcontext"> <a class="anchor" href="#Documentation/git-config.txt-diffcontext"></a>diff.context </dt>
+<dd>
+<p>Generate diffs with &lt;n&gt; lines of context instead of the default
+of 3. This value is overridden by the -U option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffinterHunkContext"> <a class="anchor" href="#Documentation/git-config.txt-diffinterHunkContext"></a>diff.interHunkContext </dt>
+<dd>
+<p>Show the context between diff hunks, up to the specified number
+of lines, thereby fusing the hunks that are close to each other.
+This value serves as the default for the <code>--inter-hunk-context</code>
+command line option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffexternal"> <a class="anchor" href="#Documentation/git-config.txt-diffexternal"></a>diff.external </dt>
+<dd>
+<p>If this config variable is set, diff generation is not
+performed using the internal diff machinery, but using the
+given command.  Can be overridden with the &#8216;GIT_EXTERNAL_DIFF&#8217;
+environment variable.  The command is called with parameters
+as described under "git Diffs" in <a href='{{< relurl "docs/git" >}}'>git[1]</a>.  Note: if
+you want to use an external diff program only on a subset of
+your files, you might want to use <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-difftrustExitCode"> <a class="anchor" href="#Documentation/git-config.txt-difftrustExitCode"></a>diff.trustExitCode </dt>
+<dd>
+<p>If this boolean value is set to true then the
+<code>diff.external</code> command is expected to return exit code
+0 if it considers the input files to be equal or 1 if it
+considers them to be different, like <code>diff(1)</code>.
+If it is set to false, which is the default, then the command
+is expected to return exit code 0 regardless of equality.
+Any other exit code causes Git to report a fatal error.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffignoreSubmodules"> <a class="anchor" href="#Documentation/git-config.txt-diffignoreSubmodules"></a>diff.ignoreSubmodules </dt>
+<dd>
+<p>Sets the default value of --ignore-submodules. Note that this
+affects only <em>git diff</em> Porcelain, and not lower level <em>diff</em>
+commands such as <em>git diff-files</em>. <em>git checkout</em>
+and <em>git switch</em> also honor
+this setting when reporting uncommitted changes. Setting it to
+<em>all</em> disables the submodule summary normally shown by <em>git commit</em>
+and <em>git status</em> when <code>status.submoduleSummary</code> is set unless it is
+overridden by using the --ignore-submodules command-line option.
+The <em>git submodule</em> commands are not affected by this setting.
+By default this is set to untracked so that any untracked
+submodules are ignored.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffmnemonicPrefix"> <a class="anchor" href="#Documentation/git-config.txt-diffmnemonicPrefix"></a>diff.mnemonicPrefix </dt>
+<dd>
+<p>If set, <em>git diff</em> uses a prefix pair that is different from the
+standard "a/" and "b/" depending on what is being compared.  When
+this configuration is in effect, reverse diff output also swaps
+the order of the prefixes:</p>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-codegitdiffcode"> <a class="anchor" href="#Documentation/git-config.txt-codegitdiffcode"></a><code>git diff</code> </dt>
+<dd>
+<p>compares the (i)ndex and the (w)ork tree;</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codegitdiffHEADcode"> <a class="anchor" href="#Documentation/git-config.txt-codegitdiffHEADcode"></a><code>git diff HEAD</code> </dt>
+<dd>
+<p>compares a (c)ommit and the (w)ork tree;</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codegitdiff--cachedcode"> <a class="anchor" href="#Documentation/git-config.txt-codegitdiff--cachedcode"></a><code>git diff --cached</code> </dt>
+<dd>
+<p>compares a (c)ommit and the (i)ndex;</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codegitdiffHEADfile1file2code"> <a class="anchor" href="#Documentation/git-config.txt-codegitdiffHEADfile1file2code"></a><code>git diff HEAD:file1 file2</code> </dt>
+<dd>
+<p>compares an (o)bject and a (w)ork tree entity;</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codegitdiff--no-indexabcode"> <a class="anchor" href="#Documentation/git-config.txt-codegitdiff--no-indexabcode"></a><code>git diff --no-index a b</code> </dt>
+<dd>
+<p>compares two non-git things (1) and (2).</p>
+</dd>
+</dl>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffnoPrefix"> <a class="anchor" href="#Documentation/git-config.txt-diffnoPrefix"></a>diff.noPrefix </dt>
+<dd>
+<p>If set, <em>git diff</em> does not show any source or destination prefix.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffsrcPrefix"> <a class="anchor" href="#Documentation/git-config.txt-diffsrcPrefix"></a>diff.srcPrefix </dt>
+<dd>
+<p>If set, <em>git diff</em> uses this source prefix. Defaults to "a/".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffdstPrefix"> <a class="anchor" href="#Documentation/git-config.txt-diffdstPrefix"></a>diff.dstPrefix </dt>
+<dd>
+<p>If set, <em>git diff</em> uses this destination prefix. Defaults to "b/".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffrelative"> <a class="anchor" href="#Documentation/git-config.txt-diffrelative"></a>diff.relative </dt>
+<dd>
+<p>If set to <em>true</em>, <em>git diff</em> does not show changes outside of the directory
+and show pathnames relative to the current directory.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-difforderFile"> <a class="anchor" href="#Documentation/git-config.txt-difforderFile"></a>diff.orderFile </dt>
+<dd>
+<p>File indicating how to order files within a diff.
+See the <em>-O</em> option to <a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a> for details.
+If <code>diff.orderFile</code> is a relative pathname, it is treated as
+relative to the top of the working tree.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffrenameLimit"> <a class="anchor" href="#Documentation/git-config.txt-diffrenameLimit"></a>diff.renameLimit </dt>
+<dd>
+<p>The number of files to consider in the exhaustive portion of
+copy/rename detection; equivalent to the <em>git diff</em> option
+<code>-l</code>.  If not set, the default value is currently 1000.  This
+setting has no effect if rename detection is turned off.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffrenames"> <a class="anchor" href="#Documentation/git-config.txt-diffrenames"></a>diff.renames </dt>
+<dd>
+<p>Whether and how Git detects renames.  If set to "false",
+rename detection is disabled. If set to "true", basic rename
+detection is enabled.  If set to "copies" or "copy", Git will
+detect copies, as well.  Defaults to true.  Note that this
+affects only <em>git diff</em> Porcelain like <a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a> and
+<a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a>, and not lower level commands such as
+<a href='{{< relurl "docs/git-diff-files" >}}'>git-diff-files[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffsuppressBlankEmpty"> <a class="anchor" href="#Documentation/git-config.txt-diffsuppressBlankEmpty"></a>diff.suppressBlankEmpty </dt>
+<dd>
+<p>A boolean to inhibit the standard behavior of printing a space
+before each empty output line. Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffsubmodule"> <a class="anchor" href="#Documentation/git-config.txt-diffsubmodule"></a>diff.submodule </dt>
+<dd>
+<p>Specify the format in which differences in submodules are
+shown.  The "short" format just shows the names of the commits
+at the beginning and end of the range. The "log" format lists
+the commits in the range like <a href='{{< relurl "docs/git-submodule" >}}'>git-submodule[1]</a> <code>summary</code>
+does. The "diff" format shows an inline diff of the changed
+contents of the submodule. Defaults to "short".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffwordRegex"> <a class="anchor" href="#Documentation/git-config.txt-diffwordRegex"></a>diff.wordRegex </dt>
+<dd>
+<p>A POSIX Extended Regular Expression used to determine what is a "word"
+when performing word-by-word difference calculations.  Character
+sequences that match the regular expression are "words", all other
+characters are <strong>ignorable</strong> whitespace.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffltdrivergtcommand"> <a class="anchor" href="#Documentation/git-config.txt-diffltdrivergtcommand"></a>diff.&lt;driver&gt;.command </dt>
+<dd>
+<p>The custom diff driver command.  See <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a>
+for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffltdrivergttrustExitCode"> <a class="anchor" href="#Documentation/git-config.txt-diffltdrivergttrustExitCode"></a>diff.&lt;driver&gt;.trustExitCode </dt>
+<dd>
+<p>If this boolean value is set to true then the
+<code>diff.&lt;driver&gt;.command</code> command is expected to return exit code
+0 if it considers the input files to be equal or 1 if it
+considers them to be different, like <code>diff(1)</code>.
+If it is set to false, which is the default, then the command
+is expected to return exit code 0 regardless of equality.
+Any other exit code causes Git to report a fatal error.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffltdrivergtxfuncname"> <a class="anchor" href="#Documentation/git-config.txt-diffltdrivergtxfuncname"></a>diff.&lt;driver&gt;.xfuncname </dt>
+<dd>
+<p>The regular expression that the diff driver should use to
+recognize the hunk header.  A built-in pattern may also be used.
+See <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffltdrivergtbinary"> <a class="anchor" href="#Documentation/git-config.txt-diffltdrivergtbinary"></a>diff.&lt;driver&gt;.binary </dt>
+<dd>
+<p>Set this option to true to make the diff driver treat files as
+binary.  See <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffltdrivergttextconv"> <a class="anchor" href="#Documentation/git-config.txt-diffltdrivergttextconv"></a>diff.&lt;driver&gt;.textconv </dt>
+<dd>
+<p>The command that the diff driver should call to generate the
+text-converted version of a file.  The result of the
+conversion is used to generate a human-readable diff.  See
+<a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffltdrivergtwordRegex"> <a class="anchor" href="#Documentation/git-config.txt-diffltdrivergtwordRegex"></a>diff.&lt;driver&gt;.wordRegex </dt>
+<dd>
+<p>The regular expression that the diff driver should use to
+split words in a line.  See <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for
+details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffltdrivergtcachetextconv"> <a class="anchor" href="#Documentation/git-config.txt-diffltdrivergtcachetextconv"></a>diff.&lt;driver&gt;.cachetextconv </dt>
+<dd>
+<p>Set this option to true to make the diff driver cache the text
+conversion outputs.  See <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for details.</p>
+<div class="ulist">
+<ul>
+<li>
+<p>araxis</p>
+</li>
+<li>
+<p>bc</p>
+</li>
+<li>
+<p>codecompare</p>
+</li>
+<li>
+<p>deltawalker</p>
+</li>
+<li>
+<p>diffmerge</p>
+</li>
+<li>
+<p>diffuse</p>
+</li>
+<li>
+<p>ecmerge</p>
+</li>
+<li>
+<p>emerge</p>
+</li>
+<li>
+<p>examdiff</p>
+</li>
+<li>
+<p>guiffy</p>
+</li>
+<li>
+<p>gvimdiff</p>
+</li>
+<li>
+<p>kdiff3</p>
+</li>
+<li>
+<p>kompare</p>
+</li>
+<li>
+<p>meld</p>
+</li>
+<li>
+<p>nvimdiff</p>
+</li>
+<li>
+<p>opendiff</p>
+</li>
+<li>
+<p>p4merge</p>
+</li>
+<li>
+<p>smerge</p>
+</li>
+<li>
+<p>tkdiff</p>
+</li>
+<li>
+<p>vimdiff</p>
+</li>
+<li>
+<p>winmerge</p>
+</li>
+<li>
+<p>xxdiff</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffindentHeuristic"> <a class="anchor" href="#Documentation/git-config.txt-diffindentHeuristic"></a>diff.indentHeuristic </dt>
+<dd>
+<p>Set this option to <code>false</code> to disable the default heuristics
+that shift diff hunk boundaries to make patches easier to read.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffalgorithm"> <a class="anchor" href="#Documentation/git-config.txt-diffalgorithm"></a>diff.algorithm </dt>
+<dd>
+<p>Choose a diff algorithm.  The variants are as follows:</p>
+<div class="openblock">
+<div class="content">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-codedefaultcodecodemyerscode"> <a class="anchor" href="#Documentation/git-config.txt-codedefaultcodecodemyerscode"></a><code>default</code>, <code>myers</code> </dt>
+<dd>
+<p>The basic greedy diff algorithm. Currently, this is the default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeminimalcode"> <a class="anchor" href="#Documentation/git-config.txt-codeminimalcode"></a><code>minimal</code> </dt>
+<dd>
+<p>Spend extra time to make sure the smallest possible diff is
+produced.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codepatiencecode"> <a class="anchor" href="#Documentation/git-config.txt-codepatiencecode"></a><code>patience</code> </dt>
+<dd>
+<p>Use "patience diff" algorithm when generating patches.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codehistogramcode"> <a class="anchor" href="#Documentation/git-config.txt-codehistogramcode"></a><code>histogram</code> </dt>
+<dd>
+<p>This algorithm extends the patience algorithm to "support
+low-occurrence common elements".</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffwsErrorHighlight"> <a class="anchor" href="#Documentation/git-config.txt-diffwsErrorHighlight"></a>diff.wsErrorHighlight </dt>
+<dd>
+<p>Highlight whitespace errors in the <code>context</code>, <code>old</code> or <code>new</code>
+lines of the diff.  Multiple values are separated by comma,
+<code>none</code> resets previous values, <code>default</code> reset the list to
+<code>new</code> and <code>all</code> is a shorthand for <code>old,new,context</code>.  The
+whitespace errors are colored with <code>color.diff.whitespace</code>.
+The command line option <code>--ws-error-highlight=&lt;kind&gt;</code>
+overrides this setting.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffcolorMoved"> <a class="anchor" href="#Documentation/git-config.txt-diffcolorMoved"></a>diff.colorMoved </dt>
+<dd>
+<p>If set to either a valid <code>&lt;mode&gt;</code> or a true value, moved lines
+in a diff are colored differently, for details of valid modes
+see <em>--color-moved</em> in <a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a>. If simply set to
+true the default color mode will be used. When set to false,
+moved lines are not colored.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffcolorMovedWS"> <a class="anchor" href="#Documentation/git-config.txt-diffcolorMovedWS"></a>diff.colorMovedWS </dt>
+<dd>
+<p>When moved lines are colored using e.g. the <code>diff.colorMoved</code> setting,
+this option controls the <code>&lt;mode&gt;</code> how spaces are treated.
+For details of valid modes see <em>--color-moved-ws</em> in <a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-difftool"> <a class="anchor" href="#Documentation/git-config.txt-difftool"></a>diff.tool </dt>
+<dd>
+<p>Controls which diff tool is used by <a href='{{< relurl "docs/git-difftool" >}}'>git-difftool[1]</a>.
+This variable overrides the value configured in <code>merge.tool</code>.
+The list below shows the valid built-in values.
+Any other value is treated as a custom diff tool and requires
+that a corresponding difftool.&lt;tool&gt;.cmd variable is defined.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-diffguitool"> <a class="anchor" href="#Documentation/git-config.txt-diffguitool"></a>diff.guitool </dt>
+<dd>
+<p>Controls which diff tool is used by <a href='{{< relurl "docs/git-difftool" >}}'>git-difftool[1]</a> when
+the -g/--gui flag is specified. This variable overrides the value
+configured in <code>merge.guitool</code>. The list below shows the valid
+built-in values. Any other value is treated as a custom diff tool
+and requires that a corresponding difftool.&lt;guitool&gt;.cmd variable
+is defined.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-difftoollttoolgtcmd"> <a class="anchor" href="#Documentation/git-config.txt-difftoollttoolgtcmd"></a>difftool.&lt;tool&gt;.cmd </dt>
+<dd>
+<p>Specify the command to invoke the specified diff tool.
+The specified command is evaluated in shell with the following
+variables available:  <em>LOCAL</em> is set to the name of the temporary
+file containing the contents of the diff pre-image and <em>REMOTE</em>
+is set to the name of the temporary file containing the contents
+of the diff post-image.</p>
+<div class="paragraph">
+<p>See the <code>--tool=&lt;tool&gt;</code> option in <a href='{{< relurl "docs/git-difftool" >}}'>git-difftool[1]</a> for more details.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-difftoollttoolgtpath"> <a class="anchor" href="#Documentation/git-config.txt-difftoollttoolgtpath"></a>difftool.&lt;tool&gt;.path </dt>
+<dd>
+<p>Override the path for the given tool.  This is useful in case
+your tool is not in the PATH.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-difftooltrustExitCode"> <a class="anchor" href="#Documentation/git-config.txt-difftooltrustExitCode"></a>difftool.trustExitCode </dt>
+<dd>
+<p>Exit difftool if the invoked diff tool returns a non-zero exit status.</p>
+<div class="paragraph">
+<p>See the <code>--trust-exit-code</code> option in <a href='{{< relurl "docs/git-difftool" >}}'>git-difftool[1]</a> for more details.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-difftoolprompt"> <a class="anchor" href="#Documentation/git-config.txt-difftoolprompt"></a>difftool.prompt </dt>
+<dd>
+<p>Prompt before each invocation of the diff tool.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-difftoolguiDefault"> <a class="anchor" href="#Documentation/git-config.txt-difftoolguiDefault"></a>difftool.guiDefault </dt>
+<dd>
+<p>Set <code>true</code> to use the <code>diff.guitool</code> by default (equivalent to specifying
+the <code>--gui</code> argument), or <code>auto</code> to select <code>diff.guitool</code> or <code>diff.tool</code>
+depending on the presence of a <code>DISPLAY</code> environment variable value. The
+default is <code>false</code>, where the <code>--gui</code> argument must be provided
+explicitly for the <code>diff.guitool</code> to be used.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-extensionsobjectFormat"> <a class="anchor" href="#Documentation/git-config.txt-extensionsobjectFormat"></a>extensions.objectFormat </dt>
+<dd>
+<p>Specify the hash algorithm to use.  The acceptable values are <code>sha1</code> and
+<code>sha256</code>.  If not specified, <code>sha1</code> is assumed.  It is an error to specify
+this key unless <code>core.repositoryFormatVersion</code> is 1.</p>
+<div class="paragraph">
+<p>Note that this setting should only be set by <a href='{{< relurl "docs/git-init" >}}'>git-init[1]</a> or
+<a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a>.  Trying to change it after initialization will not
+work and will produce hard-to-diagnose issues.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-extensionscompatObjectFormat"> <a class="anchor" href="#Documentation/git-config.txt-extensionscompatObjectFormat"></a>extensions.compatObjectFormat </dt>
+<dd>
+<p>Specify a compatitbility hash algorithm to use.  The acceptable values
+are <code>sha1</code> and <code>sha256</code>.  The value specified must be different from the
+value of extensions.objectFormat.  This allows client level
+interoperability between git repositories whose objectFormat matches
+this compatObjectFormat.  In particular when fully implemented the
+pushes and pulls from a repository in whose objectFormat matches
+compatObjectFormat.  As well as being able to use oids encoded in
+compatObjectFormat in addition to oids encoded with objectFormat to
+locally specify objects.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-extensionsrefStorage"> <a class="anchor" href="#Documentation/git-config.txt-extensionsrefStorage"></a>extensions.refStorage </dt>
+<dd>
+<p>Specify the ref storage format to use. The acceptable values are:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>files</code> for loose files with packed-refs. This is the default.</p>
+</li>
+<li>
+<p><code>reftable</code> for the reftable format. This format is experimental and its
+internals are subject to change.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>It is an error to specify this key unless <code>core.repositoryFormatVersion</code> is 1.</p>
+</div>
+<div class="paragraph">
+<p>+
+Note that this setting should only be set by <a href='{{< relurl "docs/git-init" >}}'>git-init[1]</a> or
+<a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a>. Trying to change it after initialization will not
+work and will produce hard-to-diagnose issues.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-extensionsworktreeConfig"> <a class="anchor" href="#Documentation/git-config.txt-extensionsworktreeConfig"></a>extensions.worktreeConfig </dt>
+<dd>
+<p>If enabled, then worktrees will load config settings from the
+<code>$GIT_DIR/config.worktree</code> file in addition to the
+<code>$GIT_COMMON_DIR/config</code> file. Note that <code>$GIT_COMMON_DIR</code> and
+<code>$GIT_DIR</code> are the same for the main working tree, while other
+working trees have <code>$GIT_DIR</code> equal to
+<code>$GIT_COMMON_DIR/worktrees/&lt;id&gt;/</code>. The settings in the
+<code>config.worktree</code> file will override settings from any other
+config files.</p>
+<div class="paragraph">
+<p>When enabling <code>extensions.worktreeConfig</code>, you must be careful to move
+certain values from the common config file to the main working tree&#8217;s
+<code>config.worktree</code> file, if present:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>core.worktree</code> must be moved from <code>$GIT_COMMON_DIR/config</code> to
+<code>$GIT_COMMON_DIR/config.worktree</code>.</p>
+</li>
+<li>
+<p>If <code>core.bare</code> is true, then it must be moved from <code>$GIT_COMMON_DIR/config</code>
+to <code>$GIT_COMMON_DIR/config.worktree</code>.</p>
+<div class="paragraph">
+<p>It may also be beneficial to adjust the locations of <code>core.sparseCheckout</code>
+and <code>core.sparseCheckoutCone</code> depending on your desire for customizable
+sparse-checkout settings for each worktree. By default, the <code>git
+sparse-checkout</code> builtin enables <code>extensions.worktreeConfig</code>, assigns
+these config values on a per-worktree basis, and uses the
+<code>$GIT_DIR/info/sparse-checkout</code> file to specify the sparsity for each
+worktree independently. See <a href='{{< relurl "docs/git-sparse-checkout" >}}'>git-sparse-checkout[1]</a> for more
+details.</p>
+</div>
+<div class="paragraph">
+<p>For historical reasons, <code>extensions.worktreeConfig</code> is respected
+regardless of the <code>core.repositoryFormatVersion</code> setting.</p>
+</div>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fastimportunpackLimit"> <a class="anchor" href="#Documentation/git-config.txt-fastimportunpackLimit"></a>fastimport.unpackLimit </dt>
+<dd>
+<p>If the number of objects imported by <a href='{{< relurl "docs/git-fast-import" >}}'>git-fast-import[1]</a>
+is below this limit, then the objects will be unpacked into
+loose object files.  However, if the number of imported objects
+equals or exceeds this limit, then the pack will be stored as a
+pack.  Storing the pack from a fast-import can make the import
+operation complete faster, especially on slow filesystems.  If
+not set, the value of <code>transfer.unpackLimit</code> is used instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-feature"> <a class="anchor" href="#Documentation/git-config.txt-feature"></a>feature.* </dt>
+<dd>
+<p>The config settings that start with <code>feature.</code> modify the defaults of
+a group of other config settings. These groups are created by the Git
+developer community as recommended defaults and are subject to change.
+In particular, new config options may be added with different defaults.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-featureexperimental"> <a class="anchor" href="#Documentation/git-config.txt-featureexperimental"></a>feature.experimental </dt>
+<dd>
+<p>Enable config options that are new to Git, and are being considered for
+future defaults. Config settings included here may be added or removed
+with each release, including minor version updates. These settings may
+have unintended interactions since they are so new. Please enable this
+setting if you are interested in providing feedback on experimental
+features. The new default values are:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>fetch.negotiationAlgorithm=skipping</code> may improve fetch negotiation times by
+skipping more commits at a time, reducing the number of round trips.</p>
+</li>
+<li>
+<p><code>pack.useBitmapBoundaryTraversal=true</code> may improve bitmap traversal times by
+walking fewer objects.</p>
+</li>
+<li>
+<p><code>pack.allowPackReuse=multi</code> may improve the time it takes to create a pack by
+reusing objects from multiple packs instead of just one.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-featuremanyFiles"> <a class="anchor" href="#Documentation/git-config.txt-featuremanyFiles"></a>feature.manyFiles </dt>
+<dd>
+<p>Enable config options that optimize for repos with many files in the
+working directory. With many files, commands such as <code>git status</code> and
+<code>git checkout</code> may be slow and these new defaults improve performance:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>index.skipHash=true</code> speeds up index writes by not computing a trailing
+checksum. Note that this will cause Git versions earlier than 2.13.0 to
+refuse to parse the index and Git versions earlier than 2.40.0 will report
+a corrupted index during <code>git fsck</code>.</p>
+</li>
+<li>
+<p><code>index.version=4</code> enables path-prefix compression in the index.</p>
+</li>
+<li>
+<p><code>core.untrackedCache=true</code> enables the untracked cache. This setting assumes
+that mtime is working on your machine.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchrecurseSubmodules"> <a class="anchor" href="#Documentation/git-config.txt-fetchrecurseSubmodules"></a>fetch.recurseSubmodules </dt>
+<dd>
+<p>This option controls whether <code>git fetch</code> (and the underlying fetch
+in <code>git pull</code>) will recursively fetch into populated submodules.
+This option can be set either to a boolean value or to <em>on-demand</em>.
+Setting it to a boolean changes the behavior of fetch and pull to
+recurse unconditionally into submodules when set to true or to not
+recurse at all when set to false. When set to <em>on-demand</em>, fetch and
+pull will only recurse into a populated submodule when its
+superproject retrieves a commit that updates the submodule&#8217;s
+reference.
+Defaults to <em>on-demand</em>, or to the value of <em>submodule.recurse</em> if set.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchfsckObjects"> <a class="anchor" href="#Documentation/git-config.txt-fetchfsckObjects"></a>fetch.fsckObjects </dt>
+<dd>
+<p>If it is set to true, git-fetch-pack will check all fetched
+objects. See <code>transfer.fsckObjects</code> for what&#8217;s
+checked. Defaults to false. If not set, the value of
+<code>transfer.fsckObjects</code> is used instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchfsckltmsg-idgt"> <a class="anchor" href="#Documentation/git-config.txt-fetchfsckltmsg-idgt"></a>fetch.fsck.&lt;msg-id&gt; </dt>
+<dd>
+<p>Acts like <code>fsck.&lt;msg-id&gt;</code>, but is used by
+<a href='{{< relurl "docs/git-fetch-pack" >}}'>git-fetch-pack[1]</a> instead of <a href='{{< relurl "docs/git-fsck" >}}'>git-fsck[1]</a>. See
+the <code>fsck.&lt;msg-id&gt;</code> documentation for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchfsckskipList"> <a class="anchor" href="#Documentation/git-config.txt-fetchfsckskipList"></a>fetch.fsck.skipList </dt>
+<dd>
+<p>Acts like <code>fsck.skipList</code>, but is used by
+<a href='{{< relurl "docs/git-fetch-pack" >}}'>git-fetch-pack[1]</a> instead of <a href='{{< relurl "docs/git-fsck" >}}'>git-fsck[1]</a>. See
+the <code>fsck.skipList</code> documentation for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchunpackLimit"> <a class="anchor" href="#Documentation/git-config.txt-fetchunpackLimit"></a>fetch.unpackLimit </dt>
+<dd>
+<p>If the number of objects fetched over the Git native
+transfer is below this
+limit, then the objects will be unpacked into loose object
+files. However if the number of received objects equals or
+exceeds this limit then the received pack will be stored as
+a pack, after adding any missing delta bases.  Storing the
+pack from a push can make the push operation complete faster,
+especially on slow filesystems.  If not set, the value of
+<code>transfer.unpackLimit</code> is used instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchprune"> <a class="anchor" href="#Documentation/git-config.txt-fetchprune"></a>fetch.prune </dt>
+<dd>
+<p>If true, fetch will automatically behave as if the <code>--prune</code>
+option was given on the command line.  See also <code>remote.&lt;name&gt;.prune</code>
+and the PRUNING section of <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchpruneTags"> <a class="anchor" href="#Documentation/git-config.txt-fetchpruneTags"></a>fetch.pruneTags </dt>
+<dd>
+<p>If true, fetch will automatically behave as if the
+<code>refs/tags/*:refs/tags/*</code> refspec was provided when pruning,
+if not set already. This allows for setting both this option
+and <code>fetch.prune</code> to maintain a 1=1 mapping to upstream
+refs. See also <code>remote.&lt;name&gt;.pruneTags</code> and the PRUNING
+section of <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchall"> <a class="anchor" href="#Documentation/git-config.txt-fetchall"></a>fetch.all </dt>
+<dd>
+<p>If true, fetch will attempt to update all available remotes.
+This behavior can be overridden by passing <code>--no-all</code> or by
+explicitly specifying one or more remote(s) to fetch from.
+Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchoutput"> <a class="anchor" href="#Documentation/git-config.txt-fetchoutput"></a>fetch.output </dt>
+<dd>
+<p>Control how ref update status is printed. Valid values are
+<code>full</code> and <code>compact</code>. Default value is <code>full</code>. See the
+OUTPUT section in <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchnegotiationAlgorithm"> <a class="anchor" href="#Documentation/git-config.txt-fetchnegotiationAlgorithm"></a>fetch.negotiationAlgorithm </dt>
+<dd>
+<p>Control how information about the commits in the local repository
+is sent when negotiating the contents of the packfile to be sent by
+the server.  Set to "consecutive" to use an algorithm that walks
+over consecutive commits checking each one.  Set to "skipping" to
+use an algorithm that skips commits in an effort to converge
+faster, but may result in a larger-than-necessary packfile; or set
+to "noop" to not send any information at all, which will almost
+certainly result in a larger-than-necessary packfile, but will skip
+the negotiation step.  Set to "default" to override settings made
+previously and use the default behaviour.  The default is normally
+"consecutive", but if <code>feature.experimental</code> is true, then the
+default is "skipping".  Unknown values will cause <em>git fetch</em> to
+error out.</p>
+<div class="paragraph">
+<p>See also the <code>--negotiate-only</code> and <code>--negotiation-tip</code> options to
+<a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchshowForcedUpdates"> <a class="anchor" href="#Documentation/git-config.txt-fetchshowForcedUpdates"></a>fetch.showForcedUpdates </dt>
+<dd>
+<p>Set to false to enable <code>--no-show-forced-updates</code> in
+<a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> and <a href='{{< relurl "docs/git-pull" >}}'>git-pull[1]</a> commands.
+Defaults to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchparallel"> <a class="anchor" href="#Documentation/git-config.txt-fetchparallel"></a>fetch.parallel </dt>
+<dd>
+<p>Specifies the maximal number of fetch operations to be run in parallel
+at a time (submodules, or remotes when the <code>--multiple</code> option of
+<a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> is in effect).</p>
+<div class="paragraph">
+<p>A value of 0 will give some reasonable default. If unset, it defaults to 1.</p>
+</div>
+<div class="paragraph">
+<p>For submodules, this setting can be overridden using the <code>submodule.fetchJobs</code>
+config setting.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchwriteCommitGraph"> <a class="anchor" href="#Documentation/git-config.txt-fetchwriteCommitGraph"></a>fetch.writeCommitGraph </dt>
+<dd>
+<p>Set to true to write a commit-graph after every <code>git fetch</code> command
+that downloads a pack-file from a remote. Using the <code>--split</code> option,
+most executions will create a very small commit-graph file on top of
+the existing commit-graph file(s). Occasionally, these files will
+merge and the write may take longer. Having an updated commit-graph
+file helps performance of many Git commands, including <code>git merge-base</code>,
+<code>git push -f</code>, and <code>git log --graph</code>. Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchbundleURI"> <a class="anchor" href="#Documentation/git-config.txt-fetchbundleURI"></a>fetch.bundleURI </dt>
+<dd>
+<p>This value stores a URI for downloading Git object data from a bundle
+URI before performing an incremental fetch from the origin Git server.
+This is similar to how the <code>--bundle-uri</code> option behaves in
+<a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a>. <code>git clone --bundle-uri</code> will set the
+<code>fetch.bundleURI</code> value if the supplied bundle URI contains a bundle
+list that is organized for incremental fetches.</p>
+<div class="paragraph">
+<p>If you modify this value and your repository has a <code>fetch.bundleCreationToken</code>
+value, then remove that <code>fetch.bundleCreationToken</code> value before fetching from
+the new bundle URI.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fetchbundleCreationToken"> <a class="anchor" href="#Documentation/git-config.txt-fetchbundleCreationToken"></a>fetch.bundleCreationToken </dt>
+<dd>
+<p>When using <code>fetch.bundleURI</code> to fetch incrementally from a bundle
+list that uses the "creationToken" heuristic, this config value
+stores the maximum <code>creationToken</code> value of the downloaded bundles.
+This value is used to prevent downloading bundles in the future
+if the advertised <code>creationToken</code> is not strictly larger than this
+value.</p>
+<div class="paragraph">
+<p>The creation token values are chosen by the provider serving the specific
+bundle URI. If you modify the URI at <code>fetch.bundleURI</code>, then be sure to
+remove the value for the <code>fetch.bundleCreationToken</code> value before fetching.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-filterltdrivergtclean"> <a class="anchor" href="#Documentation/git-config.txt-filterltdrivergtclean"></a>filter.&lt;driver&gt;.clean </dt>
+<dd>
+<p>The command which is used to convert the content of a worktree
+file to a blob upon checkin.  See <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for
+details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-filterltdrivergtsmudge"> <a class="anchor" href="#Documentation/git-config.txt-filterltdrivergtsmudge"></a>filter.&lt;driver&gt;.smudge </dt>
+<dd>
+<p>The command which is used to convert the content of a blob
+object to a worktree file upon checkout.  See
+<a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatattach"> <a class="anchor" href="#Documentation/git-config.txt-formatattach"></a>format.attach </dt>
+<dd>
+<p>Enable multipart/mixed attachments as the default for
+<em>format-patch</em>.  The value can also be a double quoted string
+which will enable attachments as the default and set the
+value as the boundary.  See the --attach option in
+<a href='{{< relurl "docs/git-format-patch" >}}'>git-format-patch[1]</a>.  To countermand an earlier
+value, set it to an empty string.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatfrom"> <a class="anchor" href="#Documentation/git-config.txt-formatfrom"></a>format.from </dt>
+<dd>
+<p>Provides the default value for the <code>--from</code> option to format-patch.
+Accepts a boolean value, or a name and email address.  If false,
+format-patch defaults to <code>--no-from</code>, using commit authors directly in
+the "From:" field of patch mails.  If true, format-patch defaults to
+<code>--from</code>, using your committer identity in the "From:" field of patch
+mails and including a "From:" field in the body of the patch mail if
+different.  If set to a non-boolean value, format-patch uses that
+value instead of your committer identity.  Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatforceInBodyFrom"> <a class="anchor" href="#Documentation/git-config.txt-formatforceInBodyFrom"></a>format.forceInBodyFrom </dt>
+<dd>
+<p>Provides the default value for the <code>--[no-]force-in-body-from</code>
+option to format-patch.  Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatnumbered"> <a class="anchor" href="#Documentation/git-config.txt-formatnumbered"></a>format.numbered </dt>
+<dd>
+<p>A boolean which can enable or disable sequence numbers in patch
+subjects.  It defaults to "auto" which enables it only if there
+is more than one patch.  It can be enabled or disabled for all
+messages by setting it to "true" or "false".  See --numbered
+option in <a href='{{< relurl "docs/git-format-patch" >}}'>git-format-patch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatheaders"> <a class="anchor" href="#Documentation/git-config.txt-formatheaders"></a>format.headers </dt>
+<dd>
+<p>Additional email headers to include in a patch to be submitted
+by mail.  See <a href='{{< relurl "docs/git-format-patch" >}}'>git-format-patch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatto"> <a class="anchor" href="#Documentation/git-config.txt-formatto"></a>format.to </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatcc"> <a class="anchor" href="#Documentation/git-config.txt-formatcc"></a>format.cc </dt>
+<dd>
+<p>Additional recipients to include in a patch to be submitted
+by mail.  See the --to and --cc options in
+<a href='{{< relurl "docs/git-format-patch" >}}'>git-format-patch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatsubjectPrefix"> <a class="anchor" href="#Documentation/git-config.txt-formatsubjectPrefix"></a>format.subjectPrefix </dt>
+<dd>
+<p>The default for format-patch is to output files with the <em>[PATCH]</em>
+subject prefix. Use this variable to change that prefix.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatcoverFromDescription"> <a class="anchor" href="#Documentation/git-config.txt-formatcoverFromDescription"></a>format.coverFromDescription </dt>
+<dd>
+<p>The default mode for format-patch to determine which parts of
+the cover letter will be populated using the branch&#8217;s
+description. See the <code>--cover-from-description</code> option in
+<a href='{{< relurl "docs/git-format-patch" >}}'>git-format-patch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatsignature"> <a class="anchor" href="#Documentation/git-config.txt-formatsignature"></a>format.signature </dt>
+<dd>
+<p>The default for format-patch is to output a signature containing
+the Git version number. Use this variable to change that default.
+Set this variable to the empty string ("") to suppress
+signature generation.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatsignatureFile"> <a class="anchor" href="#Documentation/git-config.txt-formatsignatureFile"></a>format.signatureFile </dt>
+<dd>
+<p>Works just like format.signature except the contents of the
+file specified by this variable will be used as the signature.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatsuffix"> <a class="anchor" href="#Documentation/git-config.txt-formatsuffix"></a>format.suffix </dt>
+<dd>
+<p>The default for format-patch is to output files with the suffix
+<code>.patch</code>. Use this variable to change that suffix (make sure to
+include the dot if you want it).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatencodeEmailHeaders"> <a class="anchor" href="#Documentation/git-config.txt-formatencodeEmailHeaders"></a>format.encodeEmailHeaders </dt>
+<dd>
+<p>Encode email headers that have non-ASCII characters with
+"Q-encoding" (described in RFC 2047) for email transmission.
+Defaults to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatpretty"> <a class="anchor" href="#Documentation/git-config.txt-formatpretty"></a>format.pretty </dt>
+<dd>
+<p>The default pretty format for log/show/whatchanged command.
+See <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a>, <a href='{{< relurl "docs/git-show" >}}'>git-show[1]</a>,
+<a href='{{< relurl "docs/git-whatchanged" >}}'>git-whatchanged[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatthread"> <a class="anchor" href="#Documentation/git-config.txt-formatthread"></a>format.thread </dt>
+<dd>
+<p>The default threading style for <em>git format-patch</em>.  Can be
+a boolean value, or <code>shallow</code> or <code>deep</code>.  <code>shallow</code> threading
+makes every mail a reply to the head of the series,
+where the head is chosen from the cover letter, the
+<code>--in-reply-to</code>, and the first patch mail, in this order.
+<code>deep</code> threading makes every mail a reply to the previous one.
+A true boolean value is the same as <code>shallow</code>, and a false
+value disables threading.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatsignOff"> <a class="anchor" href="#Documentation/git-config.txt-formatsignOff"></a>format.signOff </dt>
+<dd>
+<p>A boolean value which lets you enable the <code>-s/--signoff</code> option of
+format-patch by default. <strong>Note:</strong> Adding the <code>Signed-off-by</code> trailer to a
+patch should be a conscious act and means that you certify you have
+the rights to submit this work under the same open source license.
+Please see the <em>SubmittingPatches</em> document for further discussion.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatcoverLetter"> <a class="anchor" href="#Documentation/git-config.txt-formatcoverLetter"></a>format.coverLetter </dt>
+<dd>
+<p>A boolean that controls whether to generate a cover-letter when
+format-patch is invoked, but in addition can be set to "auto", to
+generate a cover-letter only when there&#8217;s more than one patch.
+Default is false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatoutputDirectory"> <a class="anchor" href="#Documentation/git-config.txt-formatoutputDirectory"></a>format.outputDirectory </dt>
+<dd>
+<p>Set a custom directory to store the resulting files instead of the
+current working directory. All directory components will be created.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatfilenameMaxLength"> <a class="anchor" href="#Documentation/git-config.txt-formatfilenameMaxLength"></a>format.filenameMaxLength </dt>
+<dd>
+<p>The maximum length of the output filenames generated by the
+<code>format-patch</code> command; defaults to 64.  Can be overridden
+by the <code>--filename-max-length=&lt;n&gt;</code> command line option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatuseAutoBase"> <a class="anchor" href="#Documentation/git-config.txt-formatuseAutoBase"></a>format.useAutoBase </dt>
+<dd>
+<p>A boolean value which lets you enable the <code>--base=auto</code> option of
+format-patch by default. Can also be set to "whenAble" to allow
+enabling <code>--base=auto</code> if a suitable base is available, but to skip
+adding base info otherwise without the format dying.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatnotes"> <a class="anchor" href="#Documentation/git-config.txt-formatnotes"></a>format.notes </dt>
+<dd>
+<p>Provides the default value for the <code>--notes</code> option to
+format-patch. Accepts a boolean value, or a ref which specifies
+where to get notes. If false, format-patch defaults to
+<code>--no-notes</code>. If true, format-patch defaults to <code>--notes</code>. If
+set to a non-boolean value, format-patch defaults to
+<code>--notes=&lt;ref&gt;</code>, where <code>ref</code> is the non-boolean value. Defaults
+to false.</p>
+<div class="paragraph">
+<p>If one wishes to use the ref <code>refs/notes/true</code>, please use that literal
+instead.</p>
+</div>
+<div class="paragraph">
+<p>This configuration can be specified multiple times in order to allow
+multiple notes refs to be included. In that case, it will behave
+similarly to multiple <code>--[no-]notes[=]</code> options passed in. That is, a
+value of <code>true</code> will show the default notes, a value of <code>&lt;ref&gt;</code> will
+also show notes from that notes ref and a value of <code>false</code> will negate
+previous configurations and not show notes.</p>
+</div>
+<div class="paragraph">
+<p>For example,</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>[format]
+	notes = true
+	notes = foo
+	notes = false
+	notes = bar</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>will only show notes from <code>refs/notes/bar</code>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatmboxrd"> <a class="anchor" href="#Documentation/git-config.txt-formatmboxrd"></a>format.mboxrd </dt>
+<dd>
+<p>A boolean value which enables the robust "mboxrd" format when
+<code>--stdout</code> is in use to escape "^&gt;+From " lines.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-formatnoprefix"> <a class="anchor" href="#Documentation/git-config.txt-formatnoprefix"></a>format.noprefix </dt>
+<dd>
+<p>If set, do not show any source or destination prefix in patches.
+This is equivalent to the <code>diff.noprefix</code> option used by <code>git
+diff</code> (but which is not respected by <code>format-patch</code>). Note that
+by setting this, the receiver of any patches you generate will
+have to apply them using the <code>-p0</code> option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fsckltmsg-idgt"> <a class="anchor" href="#Documentation/git-config.txt-fsckltmsg-idgt"></a>fsck.&lt;msg-id&gt; </dt>
+<dd>
+<p>During fsck git may find issues with legacy data which
+wouldn&#8217;t be generated by current versions of git, and which
+wouldn&#8217;t be sent over the wire if <code>transfer.fsckObjects</code> was
+set. This feature is intended to support working with legacy
+repositories containing such data.</p>
+<div class="paragraph">
+<p>Setting <code>fsck.&lt;msg-id&gt;</code> will be picked up by <a href='{{< relurl "docs/git-fsck" >}}'>git-fsck[1]</a>, but
+to accept pushes of such data set <code>receive.fsck.&lt;msg-id&gt;</code> instead, or
+to clone or fetch it set <code>fetch.fsck.&lt;msg-id&gt;</code>.</p>
+</div>
+<div class="paragraph">
+<p>The rest of the documentation discusses <code>fsck.*</code> for brevity, but the
+same applies for the corresponding <code>receive.fsck.*</code> and
+<code>fetch.fsck.*</code>. variables.</p>
+</div>
+<div class="paragraph">
+<p>Unlike variables like <code>color.ui</code> and <code>core.editor</code>, the
+<code>receive.fsck.&lt;msg-id&gt;</code> and <code>fetch.fsck.&lt;msg-id&gt;</code> variables will not
+fall back on the <code>fsck.&lt;msg-id&gt;</code> configuration if they aren&#8217;t set. To
+uniformly configure the same fsck settings in different circumstances,
+all three of them must be set to the same values.</p>
+</div>
+<div class="paragraph">
+<p>When <code>fsck.&lt;msg-id&gt;</code> is set, errors can be switched to warnings and
+vice versa by configuring the <code>fsck.&lt;msg-id&gt;</code> setting where the
+<code>&lt;msg-id&gt;</code> is the fsck message ID and the value is one of <code>error</code>,
+<code>warn</code> or <code>ignore</code>. For convenience, fsck prefixes the error/warning
+with the message ID, e.g. "missingEmail: invalid author/committer
+line - missing email" means that setting <code>fsck.missingEmail = ignore</code>
+will hide that issue.</p>
+</div>
+<div class="paragraph">
+<p>In general, it is better to enumerate existing objects with problems
+with <code>fsck.skipList</code>, instead of listing the kind of breakages these
+problematic objects share to be ignored, as doing the latter will
+allow new instances of the same breakages go unnoticed.</p>
+</div>
+<div class="paragraph">
+<p>Setting an unknown <code>fsck.&lt;msg-id&gt;</code> value will cause fsck to die, but
+doing the same for <code>receive.fsck.&lt;msg-id&gt;</code> and <code>fetch.fsck.&lt;msg-id&gt;</code>
+will only cause git to warn.</p>
+</div>
+<div class="paragraph">
+<p>See the <code>Fsck Messages</code> section of <a href='{{< relurl "docs/git-fsck" >}}'>git-fsck[1]</a> for supported
+values of <code>&lt;msg-id&gt;</code>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fsckskipList"> <a class="anchor" href="#Documentation/git-config.txt-fsckskipList"></a>fsck.skipList </dt>
+<dd>
+<p>The path to a list of object names (i.e. one unabbreviated SHA-1 per
+line) that are known to be broken in a non-fatal way and should
+be ignored. On versions of Git 2.20 and later, comments (<em>#</em>), empty
+lines, and any leading and trailing whitespace are ignored. Everything
+but a SHA-1 per line will error out on older versions.</p>
+<div class="paragraph">
+<p>This feature is useful when an established project should be accepted
+despite early commits containing errors that can be safely ignored,
+such as invalid committer email addresses.  Note: corrupt objects
+cannot be skipped with this setting.</p>
+</div>
+<div class="paragraph">
+<p>Like <code>fsck.&lt;msg-id&gt;</code> this variable has corresponding
+<code>receive.fsck.skipList</code> and <code>fetch.fsck.skipList</code> variants.</p>
+</div>
+<div class="paragraph">
+<p>Unlike variables like <code>color.ui</code> and <code>core.editor</code> the
+<code>receive.fsck.skipList</code> and <code>fetch.fsck.skipList</code> variables will not
+fall back on the <code>fsck.skipList</code> configuration if they aren&#8217;t set. To
+uniformly configure the same fsck settings in different circumstances,
+all three of them must be set to the same values.</p>
+</div>
+<div class="paragraph">
+<p>Older versions of Git (before 2.20) documented that the object names
+list should be sorted. This was never a requirement; the object names
+could appear in any order, but when reading the list we tracked whether
+the list was sorted for the purposes of an internal binary search
+implementation, which could save itself some work with an already sorted
+list. Unless you had a humongous list there was no reason to go out of
+your way to pre-sort the list. After Git version 2.20 a hash implementation
+is used instead, so there&#8217;s now no reason to pre-sort the list.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fsmonitorallowRemote"> <a class="anchor" href="#Documentation/git-config.txt-fsmonitorallowRemote"></a>fsmonitor.allowRemote </dt>
+<dd>
+<p>By default, the fsmonitor daemon refuses to work with network-mounted
+repositories. Setting <code>fsmonitor.allowRemote</code> to <code>true</code> overrides this
+behavior.  Only respected when <code>core.fsmonitor</code> is set to <code>true</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-fsmonitorsocketDir"> <a class="anchor" href="#Documentation/git-config.txt-fsmonitorsocketDir"></a>fsmonitor.socketDir </dt>
+<dd>
+<p>This Mac OS-specific option, if set, specifies the directory in
+which to create the Unix domain socket used for communication
+between the fsmonitor daemon and various Git commands. The directory must
+reside on a native Mac OS filesystem.  Only respected when <code>core.fsmonitor</code>
+is set to <code>true</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcaggressiveDepth"> <a class="anchor" href="#Documentation/git-config.txt-gcaggressiveDepth"></a>gc.aggressiveDepth </dt>
+<dd>
+<p>The depth parameter used in the delta compression
+algorithm used by <em>git gc --aggressive</em>.  This defaults
+to 50, which is the default for the <code>--depth</code> option when
+<code>--aggressive</code> isn&#8217;t in use.</p>
+<div class="paragraph">
+<p>See the documentation for the <code>--depth</code> option in
+<a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a> for more details.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcaggressiveWindow"> <a class="anchor" href="#Documentation/git-config.txt-gcaggressiveWindow"></a>gc.aggressiveWindow </dt>
+<dd>
+<p>The window size parameter used in the delta compression
+algorithm used by <em>git gc --aggressive</em>.  This defaults
+to 250, which is a much more aggressive window size than
+the default <code>--window</code> of 10.</p>
+<div class="paragraph">
+<p>See the documentation for the <code>--window</code> option in
+<a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a> for more details.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcauto"> <a class="anchor" href="#Documentation/git-config.txt-gcauto"></a>gc.auto </dt>
+<dd>
+<p>When there are approximately more than this many loose
+objects in the repository, <code>git gc --auto</code> will pack them.
+Some Porcelain commands use this command to perform a
+light-weight garbage collection from time to time.  The
+default value is 6700.</p>
+<div class="paragraph">
+<p>Setting this to 0 disables not only automatic packing based on the
+number of loose objects, but also any other heuristic <code>git gc --auto</code> will
+otherwise use to determine if there&#8217;s work to do, such as
+<code>gc.autoPackLimit</code>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcautoPackLimit"> <a class="anchor" href="#Documentation/git-config.txt-gcautoPackLimit"></a>gc.autoPackLimit </dt>
+<dd>
+<p>When there are more than this many packs that are not
+marked with <code>*.keep</code> file in the repository, <code>git gc
+--auto</code> consolidates them into one larger pack.  The
+default value is 50.  Setting this to 0 disables it.
+Setting <code>gc.auto</code> to 0 will also disable this.</p>
+<div class="paragraph">
+<p>See the <code>gc.bigPackThreshold</code> configuration variable below. When in
+use, it&#8217;ll affect how the auto pack limit works.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcautoDetach"> <a class="anchor" href="#Documentation/git-config.txt-gcautoDetach"></a>gc.autoDetach </dt>
+<dd>
+<p>Make <code>git gc --auto</code> return immediately and run in the background
+if the system supports it. Default is true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcbigPackThreshold"> <a class="anchor" href="#Documentation/git-config.txt-gcbigPackThreshold"></a>gc.bigPackThreshold </dt>
+<dd>
+<p>If non-zero, all non-cruft packs larger than this limit are kept
+when <code>git gc</code> is run. This is very similar to
+<code>--keep-largest-pack</code> except that all non-cruft packs that meet
+the threshold are kept, not just the largest pack. Defaults to
+zero. Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>
+<div class="paragraph">
+<p>Note that if the number of kept packs is more than gc.autoPackLimit,
+this configuration variable is ignored, all packs except the base pack
+will be repacked. After this the number of packs should go below
+gc.autoPackLimit and gc.bigPackThreshold should be respected again.</p>
+</div>
+<div class="paragraph">
+<p>If the amount of memory estimated for <code>git repack</code> to run smoothly is
+not available and <code>gc.bigPackThreshold</code> is not set, the largest pack
+will also be excluded (this is the equivalent of running <code>git gc</code> with
+<code>--keep-largest-pack</code>).</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcwriteCommitGraph"> <a class="anchor" href="#Documentation/git-config.txt-gcwriteCommitGraph"></a>gc.writeCommitGraph </dt>
+<dd>
+<p>If true, then gc will rewrite the commit-graph file when
+<a href='{{< relurl "docs/git-gc" >}}'>git-gc[1]</a> is run. When using <code>git gc --auto</code>
+the commit-graph will be updated if housekeeping is
+required. Default is true. See <a href='{{< relurl "docs/git-commit-graph" >}}'>git-commit-graph[1]</a>
+for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gclogExpiry"> <a class="anchor" href="#Documentation/git-config.txt-gclogExpiry"></a>gc.logExpiry </dt>
+<dd>
+<p>If the file gc.log exists, then <code>git gc --auto</code> will print
+its content and exit with status zero instead of running
+unless that file is more than <em>gc.logExpiry</em> old.  Default is
+"1.day".  See <code>gc.pruneExpire</code> for more ways to specify its
+value.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcpackRefs"> <a class="anchor" href="#Documentation/git-config.txt-gcpackRefs"></a>gc.packRefs </dt>
+<dd>
+<p>Running <code>git pack-refs</code> in a repository renders it
+unclonable by Git versions prior to 1.5.1.2 over dumb
+transports such as HTTP.  This variable determines whether
+<em>git gc</em> runs <code>git pack-refs</code>. This can be set to <code>notbare</code>
+to enable it within all non-bare repos or it can be set to a
+boolean value.  The default is <code>true</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gccruftPacks"> <a class="anchor" href="#Documentation/git-config.txt-gccruftPacks"></a>gc.cruftPacks </dt>
+<dd>
+<p>Store unreachable objects in a cruft pack (see
+<a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a>) instead of as loose objects. The default
+is <code>true</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcmaxCruftSize"> <a class="anchor" href="#Documentation/git-config.txt-gcmaxCruftSize"></a>gc.maxCruftSize </dt>
+<dd>
+<p>Limit the size of new cruft packs when repacking. When
+specified in addition to <code>--max-cruft-size</code>, the command line
+option takes priority. See the <code>--max-cruft-size</code> option of
+<a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcpruneExpire"> <a class="anchor" href="#Documentation/git-config.txt-gcpruneExpire"></a>gc.pruneExpire </dt>
+<dd>
+<p>When <em>git gc</em> is run, it will call <em>prune --expire 2.weeks.ago</em>
+(and <em>repack --cruft --cruft-expiration 2.weeks.ago</em> if using
+cruft packs via <code>gc.cruftPacks</code> or <code>--cruft</code>).  Override the
+grace period with this config variable.  The value "now" may be
+used to disable this grace period and always prune unreachable
+objects immediately, or "never" may be used to suppress pruning.
+This feature helps prevent corruption when <em>git gc</em> runs
+concurrently with another process writing to the repository; see
+the "NOTES" section of <a href='{{< relurl "docs/git-gc" >}}'>git-gc[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcworktreePruneExpire"> <a class="anchor" href="#Documentation/git-config.txt-gcworktreePruneExpire"></a>gc.worktreePruneExpire </dt>
+<dd>
+<p>When <em>git gc</em> is run, it calls
+<em>git worktree prune --expire 3.months.ago</em>.
+This config variable can be used to set a different grace
+period. The value "now" may be used to disable the grace
+period and prune <code>$GIT_DIR/worktrees</code> immediately, or "never"
+may be used to suppress pruning.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcreflogExpire"> <a class="anchor" href="#Documentation/git-config.txt-gcreflogExpire"></a>gc.reflogExpire </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcltpatterngtreflogExpire"> <a class="anchor" href="#Documentation/git-config.txt-gcltpatterngtreflogExpire"></a>gc.&lt;pattern&gt;.reflogExpire </dt>
+<dd>
+<p><em>git reflog expire</em> removes reflog entries older than
+this time; defaults to 90 days. The value "now" expires all
+entries immediately, and "never" suppresses expiration
+altogether. With "&lt;pattern&gt;" (e.g.
+"refs/stash") in the middle the setting applies only to
+the refs that match the &lt;pattern&gt;.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcreflogExpireUnreachable"> <a class="anchor" href="#Documentation/git-config.txt-gcreflogExpireUnreachable"></a>gc.reflogExpireUnreachable </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcltpatterngtreflogExpireUnreachable"> <a class="anchor" href="#Documentation/git-config.txt-gcltpatterngtreflogExpireUnreachable"></a>gc.&lt;pattern&gt;.reflogExpireUnreachable </dt>
+<dd>
+<p><em>git reflog expire</em> removes reflog entries older than
+this time and are not reachable from the current tip;
+defaults to 30 days. The value "now" expires all entries
+immediately, and "never" suppresses expiration altogether.
+With "&lt;pattern&gt;" (e.g. "refs/stash")
+in the middle, the setting applies only to the refs that
+match the &lt;pattern&gt;.</p>
+<div class="paragraph">
+<p>These types of entries are generally created as a result of using <code>git
+commit --amend</code> or <code>git rebase</code> and are the commits prior to the amend
+or rebase occurring.  Since these changes are not part of the current
+project most users will want to expire them sooner, which is why the
+default is more aggressive than <code>gc.reflogExpire</code>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcrecentObjectsHook"> <a class="anchor" href="#Documentation/git-config.txt-gcrecentObjectsHook"></a>gc.recentObjectsHook </dt>
+<dd>
+<p>When considering whether or not to remove an object (either when
+generating a cruft pack or storing unreachable objects as
+loose), use the shell to execute the specified command(s).
+Interpret their output as object IDs which Git will consider as
+"recent", regardless of their age. By treating their mtimes as
+"now", any objects (and their descendants) mentioned in the
+output will be kept regardless of their true age.</p>
+<div class="paragraph">
+<p>Output must contain exactly one hex object ID per line, and nothing
+else. Objects which cannot be found in the repository are ignored.
+Multiple hooks are supported, but all must exit successfully, else the
+operation (either generating a cruft pack or unpacking unreachable
+objects) will be halted.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcrepackFilter"> <a class="anchor" href="#Documentation/git-config.txt-gcrepackFilter"></a>gc.repackFilter </dt>
+<dd>
+<p>When repacking, use the specified filter to move certain
+objects into a separate packfile.  See the
+<code>--filter=&lt;filter-spec&gt;</code> option of <a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcrepackFilterTo"> <a class="anchor" href="#Documentation/git-config.txt-gcrepackFilterTo"></a>gc.repackFilterTo </dt>
+<dd>
+<p>When repacking and using a filter, see <code>gc.repackFilter</code>, the
+specified location will be used to create the packfile
+containing the filtered out objects. <strong>WARNING:</strong> The
+specified location should be accessible, using for example the
+Git alternates mechanism, otherwise the repo could be
+considered corrupt by Git as it migh not be able to access the
+objects in that packfile. See the <code>--filter-to=&lt;dir&gt;</code> option
+of <a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a> and the <code>objects/info/alternates</code>
+section of <a href='{{< relurl "docs/gitrepository-layout" >}}'>gitrepository-layout[5]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcrerereResolved"> <a class="anchor" href="#Documentation/git-config.txt-gcrerereResolved"></a>gc.rerereResolved </dt>
+<dd>
+<p>Records of conflicted merge you resolved earlier are
+kept for this many days when <em>git rerere gc</em> is run.
+You can also use more human-readable "1.month.ago", etc.
+The default is 60 days.  See <a href='{{< relurl "docs/git-rerere" >}}'>git-rerere[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gcrerereUnresolved"> <a class="anchor" href="#Documentation/git-config.txt-gcrerereUnresolved"></a>gc.rerereUnresolved </dt>
+<dd>
+<p>Records of conflicted merge you have not resolved are
+kept for this many days when <em>git rerere gc</em> is run.
+You can also use more human-readable "1.month.ago", etc.
+The default is 15 days.  See <a href='{{< relurl "docs/git-rerere" >}}'>git-rerere[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitcvscommitMsgAnnotation"> <a class="anchor" href="#Documentation/git-config.txt-gitcvscommitMsgAnnotation"></a>gitcvs.commitMsgAnnotation </dt>
+<dd>
+<p>Append this string to each commit message. Set to empty string
+to disable this feature. Defaults to "via git-CVS emulator".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitcvsenabled"> <a class="anchor" href="#Documentation/git-config.txt-gitcvsenabled"></a>gitcvs.enabled </dt>
+<dd>
+<p>Whether the CVS server interface is enabled for this repository.
+See <a href='{{< relurl "docs/git-cvsserver" >}}'>git-cvsserver[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitcvslogFile"> <a class="anchor" href="#Documentation/git-config.txt-gitcvslogFile"></a>gitcvs.logFile </dt>
+<dd>
+<p>Path to a log file where the CVS server interface well&#8230;&#8203; logs
+various stuff. See <a href='{{< relurl "docs/git-cvsserver" >}}'>git-cvsserver[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitcvsusecrlfattr"> <a class="anchor" href="#Documentation/git-config.txt-gitcvsusecrlfattr"></a>gitcvs.usecrlfattr </dt>
+<dd>
+<p>If true, the server will look up the end-of-line conversion
+attributes for files to determine the <code>-k</code> modes to use. If
+the attributes force Git to treat a file as text,
+the <code>-k</code> mode will be left blank so CVS clients will
+treat it as text. If they suppress text conversion, the file
+will be set with <em>-kb</em> mode, which suppresses any newline munging
+the client might otherwise do. If the attributes do not allow
+the file type to be determined, then <code>gitcvs.allBinary</code> is
+used. See <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitcvsallBinary"> <a class="anchor" href="#Documentation/git-config.txt-gitcvsallBinary"></a>gitcvs.allBinary </dt>
+<dd>
+<p>This is used if <code>gitcvs.usecrlfattr</code> does not resolve
+the correct <em>-kb</em> mode to use. If true, all
+unresolved files are sent to the client in
+mode <em>-kb</em>. This causes the client to treat them
+as binary files, which suppresses any newline munging it
+otherwise might do. Alternatively, if it is set to "guess",
+then the contents of the file are examined to decide if
+it is binary, similar to <code>core.autocrlf</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitcvsdbName"> <a class="anchor" href="#Documentation/git-config.txt-gitcvsdbName"></a>gitcvs.dbName </dt>
+<dd>
+<p>Database used by git-cvsserver to cache revision information
+derived from the Git repository. The exact meaning depends on the
+used database driver, for SQLite (which is the default driver) this
+is a filename. Supports variable substitution (see
+<a href='{{< relurl "docs/git-cvsserver" >}}'>git-cvsserver[1]</a> for details). May not contain semicolons (<code>;</code>).
+Default: <em>%Ggitcvs.%m.sqlite</em></p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitcvsdbDriver"> <a class="anchor" href="#Documentation/git-config.txt-gitcvsdbDriver"></a>gitcvs.dbDriver </dt>
+<dd>
+<p>Used Perl DBI driver. You can specify any available driver
+for this here, but it might not work. git-cvsserver is tested
+with <em>DBD::SQLite</em>, reported to work with <em>DBD::Pg</em>, and
+reported <strong>not</strong> to work with <em>DBD::mysql</em>. Experimental feature.
+May not contain double colons (<code>:</code>). Default: <em>SQLite</em>.
+See <a href='{{< relurl "docs/git-cvsserver" >}}'>git-cvsserver[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitcvsdbUsergitcvsdbPass"> <a class="anchor" href="#Documentation/git-config.txt-gitcvsdbUsergitcvsdbPass"></a>gitcvs.dbUser, gitcvs.dbPass </dt>
+<dd>
+<p>Database user and password. Only useful if setting <code>gitcvs.dbDriver</code>,
+since SQLite has no concept of database users and/or passwords.
+<em>gitcvs.dbUser</em> supports variable substitution (see
+<a href='{{< relurl "docs/git-cvsserver" >}}'>git-cvsserver[1]</a> for details).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitcvsdbTableNamePrefix"> <a class="anchor" href="#Documentation/git-config.txt-gitcvsdbTableNamePrefix"></a>gitcvs.dbTableNamePrefix </dt>
+<dd>
+<p>Database table name prefix.  Prepended to the names of any
+database tables used, allowing a single database to be used
+for several repositories.  Supports variable substitution (see
+<a href='{{< relurl "docs/git-cvsserver" >}}'>git-cvsserver[1]</a> for details).  Any non-alphabetic
+characters will be replaced with underscores.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>All gitcvs variables except for <code>gitcvs.usecrlfattr</code> and
+<code>gitcvs.allBinary</code> can also be specified as
+<em>gitcvs.&lt;access_method&gt;.&lt;varname&gt;</em> (where <em>access_method</em>
+is one of "ext" and "pserver") to make them apply only for the given
+access method.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebcategory"> <a class="anchor" href="#Documentation/git-config.txt-gitwebcategory"></a>gitweb.category </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebdescription"> <a class="anchor" href="#Documentation/git-config.txt-gitwebdescription"></a>gitweb.description </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebowner"> <a class="anchor" href="#Documentation/git-config.txt-gitwebowner"></a>gitweb.owner </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitweburl"> <a class="anchor" href="#Documentation/git-config.txt-gitweburl"></a>gitweb.url </dt>
+<dd>
+<p>See <a href='{{< relurl "docs/gitweb" >}}'>gitweb[1]</a> for description.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebavatar"> <a class="anchor" href="#Documentation/git-config.txt-gitwebavatar"></a>gitweb.avatar </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebblame"> <a class="anchor" href="#Documentation/git-config.txt-gitwebblame"></a>gitweb.blame </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebgrep"> <a class="anchor" href="#Documentation/git-config.txt-gitwebgrep"></a>gitweb.grep </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebhighlight"> <a class="anchor" href="#Documentation/git-config.txt-gitwebhighlight"></a>gitweb.highlight </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebpatches"> <a class="anchor" href="#Documentation/git-config.txt-gitwebpatches"></a>gitweb.patches </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebpickaxe"> <a class="anchor" href="#Documentation/git-config.txt-gitwebpickaxe"></a>gitweb.pickaxe </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebremoteheads"> <a class="anchor" href="#Documentation/git-config.txt-gitwebremoteheads"></a>gitweb.remote_heads </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebshowSizes"> <a class="anchor" href="#Documentation/git-config.txt-gitwebshowSizes"></a>gitweb.showSizes </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-gitwebsnapshot"> <a class="anchor" href="#Documentation/git-config.txt-gitwebsnapshot"></a>gitweb.snapshot </dt>
+<dd>
+<p>See <a href='{{< relurl "docs/gitweb.conf" >}}'>gitweb.conf[5]</a> for description.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gpgprogram"> <a class="anchor" href="#Documentation/git-config.txt-gpgprogram"></a>gpg.program </dt>
+<dd>
+<p>Use this custom program instead of "<code>gpg</code>" found on <code>$PATH</code> when
+making or verifying a PGP signature. The program must support the
+same command-line interface as GPG, namely, to verify a detached
+signature, "<code>gpg --verify $signature - &lt;$file</code>" is run, and the
+program is expected to signal a good signature by exiting with
+code 0.  To generate an ASCII-armored detached signature, the
+standard input of "<code>gpg -bsau $key</code>" is fed with the contents to be
+signed, and the program is expected to send the result to its
+standard output.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gpgformat"> <a class="anchor" href="#Documentation/git-config.txt-gpgformat"></a>gpg.format </dt>
+<dd>
+<p>Specifies which key format to use when signing with <code>--gpg-sign</code>.
+Default is "openpgp". Other possible values are "x509", "ssh".</p>
+<div class="paragraph">
+<p>See <a href='{{< relurl "docs/gitformat-signature" >}}'>gitformat-signature[5]</a> for the signature format, which differs
+based on the selected <code>gpg.format</code>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gpgltformatgtprogram"> <a class="anchor" href="#Documentation/git-config.txt-gpgltformatgtprogram"></a>gpg.&lt;format&gt;.program </dt>
+<dd>
+<p>Use this to customize the program used for the signing format you
+chose. (see <code>gpg.program</code> and <code>gpg.format</code>) <code>gpg.program</code> can still
+be used as a legacy synonym for <code>gpg.openpgp.program</code>. The default
+value for <code>gpg.x509.program</code> is "gpgsm" and <code>gpg.ssh.program</code> is "ssh-keygen".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gpgminTrustLevel"> <a class="anchor" href="#Documentation/git-config.txt-gpgminTrustLevel"></a>gpg.minTrustLevel </dt>
+<dd>
+<p>Specifies a minimum trust level for signature verification.  If
+this option is unset, then signature verification for merge
+operations requires a key with at least <code>marginal</code> trust.  Other
+operations that perform signature verification require a key
+with at least <code>undefined</code> trust.  Setting this option overrides
+the required trust-level for all operations.  Supported values,
+in increasing order of significance:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>undefined</code></p>
+</li>
+<li>
+<p><code>never</code></p>
+</li>
+<li>
+<p><code>marginal</code></p>
+</li>
+<li>
+<p><code>fully</code></p>
+</li>
+<li>
+<p><code>ultimate</code></p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gpgsshdefaultKeyCommand"> <a class="anchor" href="#Documentation/git-config.txt-gpgsshdefaultKeyCommand"></a>gpg.ssh.defaultKeyCommand </dt>
+<dd>
+<p>This command will be run when user.signingkey is not set and a ssh
+signature is requested. On successful exit a valid ssh public key
+prefixed with <code>key::</code> is expected in the first line of its output.
+This allows for a script doing a dynamic lookup of the correct public
+key when it is impractical to statically configure <code>user.signingKey</code>.
+For example when keys or SSH Certificates are rotated frequently or
+selection of the right key depends on external factors unknown to git.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gpgsshallowedSignersFile"> <a class="anchor" href="#Documentation/git-config.txt-gpgsshallowedSignersFile"></a>gpg.ssh.allowedSignersFile </dt>
+<dd>
+<p>A file containing ssh public keys which you are willing to trust.
+The file consists of one or more lines of principals followed by an ssh
+public key.
+e.g.: <code>user1@example.com,user2@example.com ssh-rsa AAAAX1...</code>
+See ssh-keygen(1) "ALLOWED SIGNERS" for details.
+The principal is only used to identify the key and is available when
+verifying a signature.</p>
+<div class="paragraph">
+<p>SSH has no concept of trust levels like gpg does. To be able to differentiate
+between valid signatures and trusted signatures the trust level of a signature
+verification is set to <code>fully</code> when the public key is present in the allowedSignersFile.
+Otherwise the trust level is <code>undefined</code> and git verify-commit/tag will fail.</p>
+</div>
+<div class="paragraph">
+<p>This file can be set to a location outside of the repository and every developer
+maintains their own trust store. A central repository server could generate this
+file automatically from ssh keys with push access to verify the code against.
+In a corporate setting this file is probably generated at a global location
+from automation that already handles developer ssh keys.</p>
+</div>
+<div class="paragraph">
+<p>A repository that only allows signed commits can store the file
+in the repository itself using a path relative to the top-level of the working tree.
+This way only committers with an already valid key can add or change keys in the keyring.</p>
+</div>
+<div class="paragraph">
+<p>Since OpensSSH 8.8 this file allows specifying a key lifetime using valid-after &amp;
+valid-before options. Git will mark signatures as valid if the signing key was
+valid at the time of the signature&#8217;s creation. This allows users to change a
+signing key without invalidating all previously made signatures.</p>
+</div>
+<div class="paragraph">
+<p>Using a SSH CA key with the cert-authority option
+(see ssh-keygen(1) "CERTIFICATES") is also valid.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-gpgsshrevocationFile"> <a class="anchor" href="#Documentation/git-config.txt-gpgsshrevocationFile"></a>gpg.ssh.revocationFile </dt>
+<dd>
+<p>Either a SSH KRL or a list of revoked public keys (without the principal prefix).
+See ssh-keygen(1) for details.
+If a public key is found in this file then it will always be treated
+as having trust level "never" and signatures will show as invalid.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-greplineNumber"> <a class="anchor" href="#Documentation/git-config.txt-greplineNumber"></a>grep.lineNumber </dt>
+<dd>
+<p>If set to true, enable <code>-n</code> option by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-grepcolumn"> <a class="anchor" href="#Documentation/git-config.txt-grepcolumn"></a>grep.column </dt>
+<dd>
+<p>If set to true, enable the <code>--column</code> option by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-greppatternType"> <a class="anchor" href="#Documentation/git-config.txt-greppatternType"></a>grep.patternType </dt>
+<dd>
+<p>Set the default matching behavior. Using a value of <em>basic</em>, <em>extended</em>,
+<em>fixed</em>, or <em>perl</em> will enable the <code>--basic-regexp</code>, <code>--extended-regexp</code>,
+<code>--fixed-strings</code>, or <code>--perl-regexp</code> option accordingly, while the
+value <em>default</em> will use the <code>grep.extendedRegexp</code> option to choose
+between <em>basic</em> and <em>extended</em>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-grepextendedRegexp"> <a class="anchor" href="#Documentation/git-config.txt-grepextendedRegexp"></a>grep.extendedRegexp </dt>
+<dd>
+<p>If set to true, enable <code>--extended-regexp</code> option by default. This
+option is ignored when the <code>grep.patternType</code> option is set to a value
+other than <em>default</em>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-grepthreads"> <a class="anchor" href="#Documentation/git-config.txt-grepthreads"></a>grep.threads </dt>
+<dd>
+<p>Number of grep worker threads to use. If unset (or set to 0), Git will
+use as many threads as the number of logical cores available.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-grepfullName"> <a class="anchor" href="#Documentation/git-config.txt-grepfullName"></a>grep.fullName </dt>
+<dd>
+<p>If set to true, enable <code>--full-name</code> option by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-grepfallbackToNoIndex"> <a class="anchor" href="#Documentation/git-config.txt-grepfallbackToNoIndex"></a>grep.fallbackToNoIndex </dt>
+<dd>
+<p>If set to true, fall back to <code>git grep --no-index</code> if <code>git grep</code>
+is executed outside of a git repository.  Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guicommitMsgWidth"> <a class="anchor" href="#Documentation/git-config.txt-guicommitMsgWidth"></a>gui.commitMsgWidth </dt>
+<dd>
+<p>Defines how wide the commit message window is in the
+<a href='{{< relurl "docs/git-gui" >}}'>git-gui[1]</a>. "75" is the default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guidiffContext"> <a class="anchor" href="#Documentation/git-config.txt-guidiffContext"></a>gui.diffContext </dt>
+<dd>
+<p>Specifies how many context lines should be used in calls to diff
+made by the <a href='{{< relurl "docs/git-gui" >}}'>git-gui[1]</a>. The default is "5".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guidisplayUntracked"> <a class="anchor" href="#Documentation/git-config.txt-guidisplayUntracked"></a>gui.displayUntracked </dt>
+<dd>
+<p>Determines if <a href='{{< relurl "docs/git-gui" >}}'>git-gui[1]</a> shows untracked files
+in the file list. The default is "true".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guiencoding"> <a class="anchor" href="#Documentation/git-config.txt-guiencoding"></a>gui.encoding </dt>
+<dd>
+<p>Specifies the default character encoding to use for displaying of
+file contents in <a href='{{< relurl "docs/git-gui" >}}'>git-gui[1]</a> and <a href='{{< relurl "docs/gitk" >}}'>gitk[1]</a>.
+It can be overridden by setting the <em>encoding</em> attribute
+for relevant files (see <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a>).
+If this option is not set, the tools default to the
+locale encoding.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guimatchTrackingBranch"> <a class="anchor" href="#Documentation/git-config.txt-guimatchTrackingBranch"></a>gui.matchTrackingBranch </dt>
+<dd>
+<p>Determines if new branches created with <a href='{{< relurl "docs/git-gui" >}}'>git-gui[1]</a> should
+default to tracking remote branches with matching names or
+not. Default: "false".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guinewBranchTemplate"> <a class="anchor" href="#Documentation/git-config.txt-guinewBranchTemplate"></a>gui.newBranchTemplate </dt>
+<dd>
+<p>Is used as a suggested name when creating new branches using the
+<a href='{{< relurl "docs/git-gui" >}}'>git-gui[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guipruneDuringFetch"> <a class="anchor" href="#Documentation/git-config.txt-guipruneDuringFetch"></a>gui.pruneDuringFetch </dt>
+<dd>
+<p>"true" if <a href='{{< relurl "docs/git-gui" >}}'>git-gui[1]</a> should prune remote-tracking branches when
+performing a fetch. The default value is "false".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitrustmtime"> <a class="anchor" href="#Documentation/git-config.txt-guitrustmtime"></a>gui.trustmtime </dt>
+<dd>
+<p>Determines if <a href='{{< relurl "docs/git-gui" >}}'>git-gui[1]</a> should trust the file modification
+timestamp or not. By default the timestamps are not trusted.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guispellingDictionary"> <a class="anchor" href="#Documentation/git-config.txt-guispellingDictionary"></a>gui.spellingDictionary </dt>
+<dd>
+<p>Specifies the dictionary used for spell checking commit messages in
+the <a href='{{< relurl "docs/git-gui" >}}'>git-gui[1]</a>. When set to "none" spell checking is turned
+off.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guifastCopyBlame"> <a class="anchor" href="#Documentation/git-config.txt-guifastCopyBlame"></a>gui.fastCopyBlame </dt>
+<dd>
+<p>If true, <em>git gui blame</em> uses <code>-C</code> instead of <code>-C -C</code> for original
+location detection. It makes blame significantly faster on huge
+repositories at the expense of less thorough copy detection.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guicopyBlameThreshold"> <a class="anchor" href="#Documentation/git-config.txt-guicopyBlameThreshold"></a>gui.copyBlameThreshold </dt>
+<dd>
+<p>Specifies the threshold to use in <em>git gui blame</em> original location
+detection, measured in alphanumeric characters. See the
+<a href='{{< relurl "docs/git-blame" >}}'>git-blame[1]</a> manual for more information on copy detection.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guiblamehistoryctx"> <a class="anchor" href="#Documentation/git-config.txt-guiblamehistoryctx"></a>gui.blamehistoryctx </dt>
+<dd>
+<p>Specifies the radius of history context in days to show in
+<a href='{{< relurl "docs/gitk" >}}'>gitk[1]</a> for the selected commit, when the <code>Show History
+Context</code> menu item is invoked from <em>git gui blame</em>. If this
+variable is set to zero, the whole history is shown.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitoolltnamegtcmd"> <a class="anchor" href="#Documentation/git-config.txt-guitoolltnamegtcmd"></a>guitool.&lt;name&gt;.cmd </dt>
+<dd>
+<p>Specifies the shell command line to execute when the corresponding item
+of the <a href='{{< relurl "docs/git-gui" >}}'>git-gui[1]</a> <code>Tools</code> menu is invoked. This option is
+mandatory for every tool. The command is executed from the root of
+the working directory, and in the environment it receives the name of
+the tool as <code>GIT_GUITOOL</code>, the name of the currently selected file as
+<em>FILENAME</em>, and the name of the current branch as <em>CUR_BRANCH</em> (if
+the head is detached, <em>CUR_BRANCH</em> is empty).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitoolltnamegtneedsFile"> <a class="anchor" href="#Documentation/git-config.txt-guitoolltnamegtneedsFile"></a>guitool.&lt;name&gt;.needsFile </dt>
+<dd>
+<p>Run the tool only if a diff is selected in the GUI. It guarantees
+that <em>FILENAME</em> is not empty.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitoolltnamegtnoConsole"> <a class="anchor" href="#Documentation/git-config.txt-guitoolltnamegtnoConsole"></a>guitool.&lt;name&gt;.noConsole </dt>
+<dd>
+<p>Run the command silently, without creating a window to display its
+output.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitoolltnamegtnoRescan"> <a class="anchor" href="#Documentation/git-config.txt-guitoolltnamegtnoRescan"></a>guitool.&lt;name&gt;.noRescan </dt>
+<dd>
+<p>Don&#8217;t rescan the working directory for changes after the tool
+finishes execution.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitoolltnamegtconfirm"> <a class="anchor" href="#Documentation/git-config.txt-guitoolltnamegtconfirm"></a>guitool.&lt;name&gt;.confirm </dt>
+<dd>
+<p>Show a confirmation dialog before actually running the tool.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitoolltnamegtargPrompt"> <a class="anchor" href="#Documentation/git-config.txt-guitoolltnamegtargPrompt"></a>guitool.&lt;name&gt;.argPrompt </dt>
+<dd>
+<p>Request a string argument from the user, and pass it to the tool
+through the <code>ARGS</code> environment variable. Since requesting an
+argument implies confirmation, the <em>confirm</em> option has no effect
+if this is enabled. If the option is set to <em>true</em>, <em>yes</em>, or <em>1</em>,
+the dialog uses a built-in generic prompt; otherwise the exact
+value of the variable is used.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitoolltnamegtrevPrompt"> <a class="anchor" href="#Documentation/git-config.txt-guitoolltnamegtrevPrompt"></a>guitool.&lt;name&gt;.revPrompt </dt>
+<dd>
+<p>Request a single valid revision from the user, and set the
+<code>REVISION</code> environment variable. In other aspects this option
+is similar to <em>argPrompt</em>, and can be used together with it.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitoolltnamegtrevUnmerged"> <a class="anchor" href="#Documentation/git-config.txt-guitoolltnamegtrevUnmerged"></a>guitool.&lt;name&gt;.revUnmerged </dt>
+<dd>
+<p>Show only unmerged branches in the <em>revPrompt</em> subdialog.
+This is useful for tools similar to merge or rebase, but not
+for things like checkout or reset.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitoolltnamegttitle"> <a class="anchor" href="#Documentation/git-config.txt-guitoolltnamegttitle"></a>guitool.&lt;name&gt;.title </dt>
+<dd>
+<p>Specifies the title to use for the prompt dialog. The default
+is the tool name.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-guitoolltnamegtprompt"> <a class="anchor" href="#Documentation/git-config.txt-guitoolltnamegtprompt"></a>guitool.&lt;name&gt;.prompt </dt>
+<dd>
+<p>Specifies the general prompt string to display at the top of
+the dialog, before subsections for <em>argPrompt</em> and <em>revPrompt</em>.
+The default value includes the actual command.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-helpbrowser"> <a class="anchor" href="#Documentation/git-config.txt-helpbrowser"></a>help.browser </dt>
+<dd>
+<p>Specify the browser that will be used to display help in the
+<em>web</em> format. See <a href='{{< relurl "docs/git-help" >}}'>git-help[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-helpformat"> <a class="anchor" href="#Documentation/git-config.txt-helpformat"></a>help.format </dt>
+<dd>
+<p>Override the default help format used by <a href='{{< relurl "docs/git-help" >}}'>git-help[1]</a>.
+Values <em>man</em>, <em>info</em>, <em>web</em> and <em>html</em> are supported. <em>man</em> is
+the default. <em>web</em> and <em>html</em> are the same.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-helpautoCorrect"> <a class="anchor" href="#Documentation/git-config.txt-helpautoCorrect"></a>help.autoCorrect </dt>
+<dd>
+<p>If git detects typos and can identify exactly one valid command similar
+to the error, git will try to suggest the correct command or even
+run the suggestion automatically. Possible config values are:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>0 (default): show the suggested command.</p>
+</li>
+<li>
+<p>positive number: run the suggested command after specified
+deciseconds (0.1 sec).</p>
+</li>
+<li>
+<p>"immediate": run the suggested command immediately.</p>
+</li>
+<li>
+<p>"prompt": show the suggestion and prompt for confirmation to run
+the command.</p>
+</li>
+<li>
+<p>"never": don&#8217;t run or show any suggested command.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-helphtmlPath"> <a class="anchor" href="#Documentation/git-config.txt-helphtmlPath"></a>help.htmlPath </dt>
+<dd>
+<p>Specify the path where the HTML documentation resides. File system paths
+and URLs are supported. HTML pages will be prefixed with this path when
+help is displayed in the <em>web</em> format. This defaults to the documentation
+path of your Git installation.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpproxy"> <a class="anchor" href="#Documentation/git-config.txt-httpproxy"></a>http.proxy </dt>
+<dd>
+<p>Override the HTTP proxy, normally configured using the <em>http_proxy</em>,
+<em>https_proxy</em>, and <em>all_proxy</em> environment variables (see <code>curl(1)</code>). In
+addition to the syntax understood by curl, it is possible to specify a
+proxy string with a user name but no password, in which case git will
+attempt to acquire one in the same way it does for other credentials. See
+<a href='{{< relurl "docs/gitcredentials" >}}'>gitcredentials[7]</a> for more information. The syntax thus is
+<em>[protocol://][user[:password]@]proxyhost[:port]</em>. This can be overridden
+on a per-remote basis; see remote.&lt;name&gt;.proxy</p>
+<div class="paragraph">
+<p>Any proxy, however configured, must be completely transparent and must not
+modify, transform, or buffer the request or response in any way.  Proxies which
+are not completely transparent are known to cause various forms of breakage
+with Git.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpproxyAuthMethod"> <a class="anchor" href="#Documentation/git-config.txt-httpproxyAuthMethod"></a>http.proxyAuthMethod </dt>
+<dd>
+<p>Set the method with which to authenticate against the HTTP proxy. This
+only takes effect if the configured proxy string contains a user name part
+(i.e. is of the form <em>user@host</em> or <em>user@host:port</em>). This can be
+overridden on a per-remote basis; see <code>remote.&lt;name&gt;.proxyAuthMethod</code>.
+Both can be overridden by the <code>GIT_HTTP_PROXY_AUTHMETHOD</code> environment
+variable.  Possible values are:</p>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>anyauth</code> - Automatically pick a suitable authentication method. It is
+assumed that the proxy answers an unauthenticated request with a 407
+status code and one or more Proxy-authenticate headers with supported
+authentication methods. This is the default.</p>
+</li>
+<li>
+<p><code>basic</code> - HTTP Basic authentication</p>
+</li>
+<li>
+<p><code>digest</code> - HTTP Digest authentication; this prevents the password from being
+transmitted to the proxy in clear text</p>
+</li>
+<li>
+<p><code>negotiate</code> - GSS-Negotiate authentication (compare the --negotiate option
+of <code>curl(1)</code>)</p>
+</li>
+<li>
+<p><code>ntlm</code> - NTLM authentication (compare the --ntlm option of <code>curl(1)</code>)</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpproxySSLCert"> <a class="anchor" href="#Documentation/git-config.txt-httpproxySSLCert"></a>http.proxySSLCert </dt>
+<dd>
+<p>The pathname of a file that stores a client certificate to use to authenticate
+with an HTTPS proxy. Can be overridden by the <code>GIT_PROXY_SSL_CERT</code> environment
+variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpproxySSLKey"> <a class="anchor" href="#Documentation/git-config.txt-httpproxySSLKey"></a>http.proxySSLKey </dt>
+<dd>
+<p>The pathname of a file that stores a private key to use to authenticate with
+an HTTPS proxy. Can be overridden by the <code>GIT_PROXY_SSL_KEY</code> environment
+variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpproxySSLCertPasswordProtected"> <a class="anchor" href="#Documentation/git-config.txt-httpproxySSLCertPasswordProtected"></a>http.proxySSLCertPasswordProtected </dt>
+<dd>
+<p>Enable Git&#8217;s password prompt for the proxy SSL certificate.  Otherwise OpenSSL
+will prompt the user, possibly many times, if the certificate or private key
+is encrypted. Can be overridden by the <code>GIT_PROXY_SSL_CERT_PASSWORD_PROTECTED</code>
+environment variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpproxySSLCAInfo"> <a class="anchor" href="#Documentation/git-config.txt-httpproxySSLCAInfo"></a>http.proxySSLCAInfo </dt>
+<dd>
+<p>Pathname to the file containing the certificate bundle that should be used to
+verify the proxy with when using an HTTPS proxy. Can be overridden by the
+<code>GIT_PROXY_SSL_CAINFO</code> environment variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpemptyAuth"> <a class="anchor" href="#Documentation/git-config.txt-httpemptyAuth"></a>http.emptyAuth </dt>
+<dd>
+<p>Attempt authentication without seeking a username or password.  This
+can be used to attempt GSS-Negotiate authentication without specifying
+a username in the URL, as libcurl normally requires a username for
+authentication.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpproactiveAuth"> <a class="anchor" href="#Documentation/git-config.txt-httpproactiveAuth"></a>http.proactiveAuth </dt>
+<dd>
+<p>Attempt authentication without first making an unauthenticated attempt and
+receiving a 401 response. This can be used to ensure that all requests are
+authenticated. If <code>http.emptyAuth</code> is set to true, this value has no effect.</p>
+<div class="paragraph">
+<p>If the credential helper used specifies an authentication scheme (i.e., via the
+<code>authtype</code> field), that value will be used; if a username and password is
+provided without a scheme, then Basic authentication is used.  The value of the
+option determines the scheme requested from the helper. Possible values are:</p>
+</div>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>basic</code> - Request Basic authentication from the helper.</p>
+</li>
+<li>
+<p><code>auto</code> - Allow the helper to pick an appropriate scheme.</p>
+</li>
+<li>
+<p><code>none</code> - Disable proactive authentication.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Note that TLS should always be used with this configuration, since otherwise it
+is easy to accidentally expose plaintext credentials if Basic authentication
+is selected.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpdelegation"> <a class="anchor" href="#Documentation/git-config.txt-httpdelegation"></a>http.delegation </dt>
+<dd>
+<p>Control GSSAPI credential delegation. The delegation is disabled
+by default in libcurl since version 7.21.7. Set parameter to tell
+the server what it is allowed to delegate when it comes to user
+credentials. Used with GSS/kerberos. Possible values are:</p>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>none</code> - Don&#8217;t allow any delegation.</p>
+</li>
+<li>
+<p><code>policy</code> - Delegates if and only if the OK-AS-DELEGATE flag is set in the
+Kerberos service ticket, which is a matter of realm policy.</p>
+</li>
+<li>
+<p><code>always</code> - Unconditionally allow the server to delegate.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpextraHeader"> <a class="anchor" href="#Documentation/git-config.txt-httpextraHeader"></a>http.extraHeader </dt>
+<dd>
+<p>Pass an additional HTTP header when communicating with a server.  If
+more than one such entry exists, all of them are added as extra
+headers.  To allow overriding the settings inherited from the system
+config, an empty value will reset the extra headers to the empty list.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpcookieFile"> <a class="anchor" href="#Documentation/git-config.txt-httpcookieFile"></a>http.cookieFile </dt>
+<dd>
+<p>The pathname of a file containing previously stored cookie lines,
+which should be used
+in the Git http session, if they match the server. The file format
+of the file to read cookies from should be plain HTTP headers or
+the Netscape/Mozilla cookie file format (see <code>curl(1)</code>).
+Set it to an empty string, to accept only new cookies from
+the server and send them back in successive requests within same
+connection.
+NOTE that the file specified with http.cookieFile is used only as
+input unless http.saveCookies is set.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsaveCookies"> <a class="anchor" href="#Documentation/git-config.txt-httpsaveCookies"></a>http.saveCookies </dt>
+<dd>
+<p>If set, store cookies received during requests to the file specified by
+http.cookieFile. Has no effect if http.cookieFile is unset, or set to
+an empty string.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpversion"> <a class="anchor" href="#Documentation/git-config.txt-httpversion"></a>http.version </dt>
+<dd>
+<p>Use the specified HTTP protocol version when communicating with a server.
+If you want to force the default. The available and default version depend
+on libcurl. Currently the possible values of
+this option are:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>HTTP/2</p>
+</li>
+<li>
+<p>HTTP/1.1</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpcurloptResolve"> <a class="anchor" href="#Documentation/git-config.txt-httpcurloptResolve"></a>http.curloptResolve </dt>
+<dd>
+<p>Hostname resolution information that will be used first by
+libcurl when sending HTTP requests.  This information should
+be in one of the following formats:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>[+]HOST:PORT:ADDRESS[,ADDRESS]</p>
+</li>
+<li>
+<p>-HOST:PORT</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The first format redirects all requests to the given <code>HOST:PORT</code>
+to the provided <code>ADDRESS</code>(s). The second format clears all
+previous config values for that <code>HOST:PORT</code> combination.  To
+allow easy overriding of all the settings inherited from the
+system config, an empty value will reset all resolution
+information to the empty list.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsslVersion"> <a class="anchor" href="#Documentation/git-config.txt-httpsslVersion"></a>http.sslVersion </dt>
+<dd>
+<p>The SSL version to use when negotiating an SSL connection, if you
+want to force the default.  The available and default version
+depend on whether libcurl was built against NSS or OpenSSL and the
+particular configuration of the crypto library in use. Internally
+this sets the <em>CURLOPT_SSL_VERSION</em> option; see the libcurl
+documentation for more details on the format of this option and
+for the ssl version supported. Currently the possible values of
+this option are:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>sslv2</p>
+</li>
+<li>
+<p>sslv3</p>
+</li>
+<li>
+<p>tlsv1</p>
+</li>
+<li>
+<p>tlsv1.0</p>
+</li>
+<li>
+<p>tlsv1.1</p>
+</li>
+<li>
+<p>tlsv1.2</p>
+</li>
+<li>
+<p>tlsv1.3</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Can be overridden by the <code>GIT_SSL_VERSION</code> environment variable.
+To force git to use libcurl&#8217;s default ssl version and ignore any
+explicit http.sslversion option, set <code>GIT_SSL_VERSION</code> to the
+empty string.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsslCipherList"> <a class="anchor" href="#Documentation/git-config.txt-httpsslCipherList"></a>http.sslCipherList </dt>
+<dd>
+<p>A list of SSL ciphers to use when negotiating an SSL connection.
+The available ciphers depend on whether libcurl was built against
+NSS or OpenSSL and the particular configuration of the crypto
+library in use.  Internally this sets the <em>CURLOPT_SSL_CIPHER_LIST</em>
+option; see the libcurl documentation for more details on the format
+of this list.</p>
+<div class="paragraph">
+<p>Can be overridden by the <code>GIT_SSL_CIPHER_LIST</code> environment variable.
+To force git to use libcurl&#8217;s default cipher list and ignore any
+explicit http.sslCipherList option, set <code>GIT_SSL_CIPHER_LIST</code> to the
+empty string.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsslVerify"> <a class="anchor" href="#Documentation/git-config.txt-httpsslVerify"></a>http.sslVerify </dt>
+<dd>
+<p>Whether to verify the SSL certificate when fetching or pushing
+over HTTPS. Defaults to true. Can be overridden by the
+<code>GIT_SSL_NO_VERIFY</code> environment variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsslCert"> <a class="anchor" href="#Documentation/git-config.txt-httpsslCert"></a>http.sslCert </dt>
+<dd>
+<p>File containing the SSL certificate when fetching or pushing
+over HTTPS. Can be overridden by the <code>GIT_SSL_CERT</code> environment
+variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsslKey"> <a class="anchor" href="#Documentation/git-config.txt-httpsslKey"></a>http.sslKey </dt>
+<dd>
+<p>File containing the SSL private key when fetching or pushing
+over HTTPS. Can be overridden by the <code>GIT_SSL_KEY</code> environment
+variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsslCertPasswordProtected"> <a class="anchor" href="#Documentation/git-config.txt-httpsslCertPasswordProtected"></a>http.sslCertPasswordProtected </dt>
+<dd>
+<p>Enable Git&#8217;s password prompt for the SSL certificate.  Otherwise
+OpenSSL will prompt the user, possibly many times, if the
+certificate or private key is encrypted.  Can be overridden by the
+<code>GIT_SSL_CERT_PASSWORD_PROTECTED</code> environment variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsslCAInfo"> <a class="anchor" href="#Documentation/git-config.txt-httpsslCAInfo"></a>http.sslCAInfo </dt>
+<dd>
+<p>File containing the certificates to verify the peer with when
+fetching or pushing over HTTPS. Can be overridden by the
+<code>GIT_SSL_CAINFO</code> environment variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsslCAPath"> <a class="anchor" href="#Documentation/git-config.txt-httpsslCAPath"></a>http.sslCAPath </dt>
+<dd>
+<p>Path containing files with the CA certificates to verify the peer
+with when fetching or pushing over HTTPS. Can be overridden
+by the <code>GIT_SSL_CAPATH</code> environment variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsslBackend"> <a class="anchor" href="#Documentation/git-config.txt-httpsslBackend"></a>http.sslBackend </dt>
+<dd>
+<p>Name of the SSL backend to use (e.g. "openssl" or "schannel").
+This option is ignored if cURL lacks support for choosing the SSL
+backend at runtime.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpschannelCheckRevoke"> <a class="anchor" href="#Documentation/git-config.txt-httpschannelCheckRevoke"></a>http.schannelCheckRevoke </dt>
+<dd>
+<p>Used to enforce or disable certificate revocation checks in cURL
+when http.sslBackend is set to "schannel". Defaults to <code>true</code> if
+unset. Only necessary to disable this if Git consistently errors
+and the message is about checking the revocation status of a
+certificate. This option is ignored if cURL lacks support for
+setting the relevant SSL option at runtime.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpschannelUseSSLCAInfo"> <a class="anchor" href="#Documentation/git-config.txt-httpschannelUseSSLCAInfo"></a>http.schannelUseSSLCAInfo </dt>
+<dd>
+<p>As of cURL v7.60.0, the Secure Channel backend can use the
+certificate bundle provided via <code>http.sslCAInfo</code>, but that would
+override the Windows Certificate Store. Since this is not desirable
+by default, Git will tell cURL not to use that bundle by default
+when the <code>schannel</code> backend was configured via <code>http.sslBackend</code>,
+unless <code>http.schannelUseSSLCAInfo</code> overrides this behavior.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httppinnedPubkey"> <a class="anchor" href="#Documentation/git-config.txt-httppinnedPubkey"></a>http.pinnedPubkey </dt>
+<dd>
+<p>Public key of the https service. It may either be the filename of
+a PEM or DER encoded public key file or a string starting with
+<em>sha256//</em> followed by the base64 encoded sha256 hash of the
+public key. See also libcurl <em>CURLOPT_PINNEDPUBLICKEY</em>. git will
+exit with an error if this option is set but not supported by
+cURL.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpsslTry"> <a class="anchor" href="#Documentation/git-config.txt-httpsslTry"></a>http.sslTry </dt>
+<dd>
+<p>Attempt to use AUTH SSL/TLS and encrypted data transfers
+when connecting via regular FTP protocol. This might be needed
+if the FTP server requires it for security reasons or you wish
+to connect securely whenever remote FTP server supports it.
+Default is false since it might trigger certificate verification
+errors on misconfigured servers.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpmaxRequests"> <a class="anchor" href="#Documentation/git-config.txt-httpmaxRequests"></a>http.maxRequests </dt>
+<dd>
+<p>How many HTTP requests to launch in parallel. Can be overridden
+by the <code>GIT_HTTP_MAX_REQUESTS</code> environment variable. Default is 5.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpminSessions"> <a class="anchor" href="#Documentation/git-config.txt-httpminSessions"></a>http.minSessions </dt>
+<dd>
+<p>The number of curl sessions (counted across slots) to be kept across
+requests. They will not be ended with curl_easy_cleanup() until
+http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
+value will be capped at 1. Defaults to 1.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httppostBuffer"> <a class="anchor" href="#Documentation/git-config.txt-httppostBuffer"></a>http.postBuffer </dt>
+<dd>
+<p>Maximum size in bytes of the buffer used by smart HTTP
+transports when POSTing data to the remote system.
+For requests larger than this buffer size, HTTP/1.1 and
+Transfer-Encoding: chunked is used to avoid creating a
+massive pack file locally.  Default is 1 MiB, which is
+sufficient for most requests.</p>
+<div class="paragraph">
+<p>Note that raising this limit is only effective for disabling chunked
+transfer encoding and therefore should be used only where the remote
+server or a proxy only supports HTTP/1.0 or is noncompliant with the
+HTTP standard.  Raising this is not, in general, an effective solution
+for most push problems, but can increase memory consumption
+significantly since the entire buffer is allocated even for small
+pushes.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httplowSpeedLimithttplowSpeedTime"> <a class="anchor" href="#Documentation/git-config.txt-httplowSpeedLimithttplowSpeedTime"></a>http.lowSpeedLimit, http.lowSpeedTime </dt>
+<dd>
+<p>If the HTTP transfer speed, in bytes per second, is less than
+<em>http.lowSpeedLimit</em> for longer than <em>http.lowSpeedTime</em> seconds,
+the transfer is aborted.
+Can be overridden by the <code>GIT_HTTP_LOW_SPEED_LIMIT</code> and
+<code>GIT_HTTP_LOW_SPEED_TIME</code> environment variables.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpnoEPSV"> <a class="anchor" href="#Documentation/git-config.txt-httpnoEPSV"></a>http.noEPSV </dt>
+<dd>
+<p>A boolean which disables using of EPSV ftp command by curl.
+This can be helpful with some "poor" ftp servers which don&#8217;t
+support EPSV mode. Can be overridden by the <code>GIT_CURL_FTP_NO_EPSV</code>
+environment variable. Default is false (curl will use EPSV).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpuserAgent"> <a class="anchor" href="#Documentation/git-config.txt-httpuserAgent"></a>http.userAgent </dt>
+<dd>
+<p>The HTTP USER_AGENT string presented to an HTTP server.  The default
+value represents the version of the Git client such as git/1.7.1.
+This option allows you to override this value to a more common value
+such as Mozilla/4.0.  This may be necessary, for instance, if
+connecting through a firewall that restricts HTTP connections to a set
+of common USER_AGENT strings (but not including those like git/1.7.1).
+Can be overridden by the <code>GIT_HTTP_USER_AGENT</code> environment variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httpfollowRedirects"> <a class="anchor" href="#Documentation/git-config.txt-httpfollowRedirects"></a>http.followRedirects </dt>
+<dd>
+<p>Whether git should follow HTTP redirects. If set to <code>true</code>, git
+will transparently follow any redirect issued by a server it
+encounters. If set to <code>false</code>, git will treat all redirects as
+errors. If set to <code>initial</code>, git will follow redirects only for
+the initial request to a remote, but not for subsequent
+follow-up HTTP requests. Since git uses the redirected URL as
+the base for the follow-up requests, this is generally
+sufficient. The default is <code>initial</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-httplturlgt"> <a class="anchor" href="#Documentation/git-config.txt-httplturlgt"></a>http.&lt;url&gt;.* </dt>
+<dd>
+<p>Any of the http.* options above can be applied selectively to some URLs.
+For a config key to match a URL, each element of the config key is
+compared to that of the URL, in the following order:</p>
+<div class="openblock">
+<div class="content">
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Scheme (e.g., <code>https</code> in <code>https://example.com/</code>). This field
+must match exactly between the config key and the URL.</p>
+</li>
+<li>
+<p>Host/domain name (e.g., <code>example.com</code> in <code>https://example.com/</code>).
+This field must match between the config key and the URL. It is
+possible to specify a <code>*</code> as part of the host name to match all subdomains
+at this level. <code>https://*.example.com/</code> for example would match
+<code>https://foo.example.com/</code>, but not <code>https://foo.bar.example.com/</code>.</p>
+</li>
+<li>
+<p>Port number (e.g., <code>8080</code> in <code>http://example.com:8080/</code>).
+This field must match exactly between the config key and the URL.
+Omitted port numbers are automatically converted to the correct
+default for the scheme before matching.</p>
+</li>
+<li>
+<p>Path (e.g., <code>repo.git</code> in <code>https://example.com/repo.git</code>). The
+path field of the config key must match the path field of the URL
+either exactly or as a prefix of slash-delimited path elements.  This means
+a config key with path <code>foo/</code> matches URL path <code>foo/bar</code>.  A prefix can only
+match on a slash (<code>/</code>) boundary.  Longer matches take precedence (so a config
+key with path <code>foo/bar</code> is a better match to URL path <code>foo/bar</code> than a config
+key with just path <code>foo/</code>).</p>
+</li>
+<li>
+<p>User name (e.g., <code>user</code> in <code>https://user@example.com/repo.git</code>). If
+the config key has a user name it must match the user name in the
+URL exactly. If the config key does not have a user name, that
+config key will match a URL with any user name (including none),
+but at a lower precedence than a config key with a user name.</p>
+</li>
+</ol>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The list above is ordered by decreasing precedence; a URL that matches
+a config key&#8217;s path is preferred to one that matches its user name. For example,
+if the URL is <code>https://user@example.com/foo/bar</code> a config key match of
+<code>https://example.com/foo</code> will be preferred over a config key match of
+<code>https://user@example.com</code>.</p>
+</div>
+<div class="paragraph">
+<p>All URLs are normalized before attempting any matching (the password part,
+if embedded in the URL, is always ignored for matching purposes) so that
+equivalent URLs that are simply spelled differently will match properly.
+Environment variable settings always override any matches.  The URLs that are
+matched against are those given directly to Git commands.  This means any URLs
+visited as a result of a redirection do not participate in matching.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-i18ncommitEncoding"> <a class="anchor" href="#Documentation/git-config.txt-i18ncommitEncoding"></a>i18n.commitEncoding </dt>
+<dd>
+<p>Character encoding the commit messages are stored in; Git itself
+does not care per se, but this information is necessary e.g. when
+importing commits from emails or in the gitk graphical history
+browser (and possibly in other places in the future or in other
+porcelains). See e.g. <a href='{{< relurl "docs/git-mailinfo" >}}'>git-mailinfo[1]</a>. Defaults to <em>utf-8</em>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-i18nlogOutputEncoding"> <a class="anchor" href="#Documentation/git-config.txt-i18nlogOutputEncoding"></a>i18n.logOutputEncoding </dt>
+<dd>
+<p>Character encoding the commit messages are converted to when
+running <em>git log</em> and friends.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-imapfolder"> <a class="anchor" href="#Documentation/git-config.txt-imapfolder"></a>imap.folder </dt>
+<dd>
+<p>The folder to drop the mails into, which is typically the Drafts
+folder. For example: "INBOX.Drafts", "INBOX/Drafts" or
+"[Gmail]/Drafts". Required.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-imaptunnel"> <a class="anchor" href="#Documentation/git-config.txt-imaptunnel"></a>imap.tunnel </dt>
+<dd>
+<p>Command used to set up a tunnel to the IMAP server through which
+commands will be piped instead of using a direct network connection
+to the server. Required when imap.host is not set.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-imaphost"> <a class="anchor" href="#Documentation/git-config.txt-imaphost"></a>imap.host </dt>
+<dd>
+<p>A URL identifying the server. Use an <code>imap://</code> prefix for non-secure
+connections and an <code>imaps://</code> prefix for secure connections.
+Ignored when imap.tunnel is set, but required otherwise.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-imapuser"> <a class="anchor" href="#Documentation/git-config.txt-imapuser"></a>imap.user </dt>
+<dd>
+<p>The username to use when logging in to the server.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-imappass"> <a class="anchor" href="#Documentation/git-config.txt-imappass"></a>imap.pass </dt>
+<dd>
+<p>The password to use when logging in to the server.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-imapport"> <a class="anchor" href="#Documentation/git-config.txt-imapport"></a>imap.port </dt>
+<dd>
+<p>An integer port number to connect to on the server.
+Defaults to 143 for imap:// hosts and 993 for imaps:// hosts.
+Ignored when imap.tunnel is set.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-imapsslverify"> <a class="anchor" href="#Documentation/git-config.txt-imapsslverify"></a>imap.sslverify </dt>
+<dd>
+<p>A boolean to enable/disable verification of the server certificate
+used by the SSL/TLS connection. Default is <code>true</code>. Ignored when
+imap.tunnel is set.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-imappreformattedHTML"> <a class="anchor" href="#Documentation/git-config.txt-imappreformattedHTML"></a>imap.preformattedHTML </dt>
+<dd>
+<p>A boolean to enable/disable the use of html encoding when sending
+a patch.  An html encoded patch will be bracketed with &lt;pre&gt;
+and have a content type of text/html.  Ironically, enabling this
+option causes Thunderbird to send the patch as a plain/text,
+format=fixed email.  Default is <code>false</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-imapauthMethod"> <a class="anchor" href="#Documentation/git-config.txt-imapauthMethod"></a>imap.authMethod </dt>
+<dd>
+<p>Specify the authentication method for authenticating with the IMAP server.
+If Git was built with the NO_CURL option, or if your curl version is older
+than 7.34.0, or if you&#8217;re running git-imap-send with the <code>--no-curl</code>
+option, the only supported method is <em>CRAM-MD5</em>. If this is not set
+then <em>git imap-send</em> uses the basic IMAP plaintext LOGIN command.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-includepath"> <a class="anchor" href="#Documentation/git-config.txt-includepath"></a>include.path </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-includeIfltconditiongtpath"> <a class="anchor" href="#Documentation/git-config.txt-includeIfltconditiongtpath"></a>includeIf.&lt;condition&gt;.path </dt>
+<dd>
+<p>Special variables to include other configuration files. See
+the "CONFIGURATION FILE" section in the main
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a> documentation,
+specifically the "Includes" and "Conditional Includes" subsections.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-indexrecordEndOfIndexEntries"> <a class="anchor" href="#Documentation/git-config.txt-indexrecordEndOfIndexEntries"></a>index.recordEndOfIndexEntries </dt>
+<dd>
+<p>Specifies whether the index file should include an "End Of Index
+Entry" section. This reduces index load time on multiprocessor
+machines but produces a message "ignoring EOIE extension" when
+reading the index using Git versions before 2.20. Defaults to
+<em>true</em> if index.threads has been explicitly enabled, <em>false</em>
+otherwise.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-indexrecordOffsetTable"> <a class="anchor" href="#Documentation/git-config.txt-indexrecordOffsetTable"></a>index.recordOffsetTable </dt>
+<dd>
+<p>Specifies whether the index file should include an "Index Entry
+Offset Table" section. This reduces index load time on
+multiprocessor machines but produces a message "ignoring IEOT
+extension" when reading the index using Git versions before 2.20.
+Defaults to <em>true</em> if index.threads has been explicitly enabled,
+<em>false</em> otherwise.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-indexsparse"> <a class="anchor" href="#Documentation/git-config.txt-indexsparse"></a>index.sparse </dt>
+<dd>
+<p>When enabled, write the index using sparse-directory entries. This
+has no effect unless <code>core.sparseCheckout</code> and
+<code>core.sparseCheckoutCone</code> are both enabled. Defaults to <em>false</em>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-indexthreads"> <a class="anchor" href="#Documentation/git-config.txt-indexthreads"></a>index.threads </dt>
+<dd>
+<p>Specifies the number of threads to spawn when loading the index.
+This is meant to reduce index load time on multiprocessor machines.
+Specifying 0 or <em>true</em> will cause Git to auto-detect the number of
+CPUs and set the number of threads accordingly. Specifying 1 or
+<em>false</em> will disable multithreading. Defaults to <em>true</em>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-indexversion"> <a class="anchor" href="#Documentation/git-config.txt-indexversion"></a>index.version </dt>
+<dd>
+<p>Specify the version with which new index files should be
+initialized.  This does not affect existing repositories.
+If <code>feature.manyFiles</code> is enabled, then the default is 4.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-indexskipHash"> <a class="anchor" href="#Documentation/git-config.txt-indexskipHash"></a>index.skipHash </dt>
+<dd>
+<p>When enabled, do not compute the trailing hash for the index file.
+This accelerates Git commands that manipulate the index, such as
+<code>git add</code>, <code>git commit</code>, or <code>git status</code>. Instead of storing the
+checksum, write a trailing set of bytes with value zero, indicating
+that the computation was skipped.</p>
+<div class="paragraph">
+<p>If you enable <code>index.skipHash</code>, then Git clients older than 2.13.0 will
+refuse to parse the index and Git clients older than 2.40.0 will report an
+error during <code>git fsck</code>.</p>
+</div>
+</dd>
+</dl>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeinittemplateDircode"> <a class="anchor" href="#Documentation/git-config.txt-codeinittemplateDircode"></a><code>init.templateDir</code> </dt>
+<dd>
+<p>Specify the directory from which templates will be copied. (See the "TEMPLATE DIRECTORY" section of <a href='{{< relurl "docs/git-init" >}}'>git-init[1]</a>.)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-codeinitdefaultBranchcode"> <a class="anchor" href="#Documentation/git-config.txt-codeinitdefaultBranchcode"></a><code>init.defaultBranch</code> </dt>
+<dd>
+<p>Allows overriding the default branch name e.g. when initializing
+a new repository.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-instawebbrowser"> <a class="anchor" href="#Documentation/git-config.txt-instawebbrowser"></a>instaweb.browser </dt>
+<dd>
+<p>Specify the program that will be used to browse your working
+repository in gitweb. See <a href='{{< relurl "docs/git-instaweb" >}}'>git-instaweb[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-instawebhttpd"> <a class="anchor" href="#Documentation/git-config.txt-instawebhttpd"></a>instaweb.httpd </dt>
+<dd>
+<p>The HTTP daemon command-line to start gitweb on your working
+repository. See <a href='{{< relurl "docs/git-instaweb" >}}'>git-instaweb[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-instaweblocal"> <a class="anchor" href="#Documentation/git-config.txt-instaweblocal"></a>instaweb.local </dt>
+<dd>
+<p>If true the web server started by <a href='{{< relurl "docs/git-instaweb" >}}'>git-instaweb[1]</a> will
+be bound to the local IP (127.0.0.1).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-instawebmodulePath"> <a class="anchor" href="#Documentation/git-config.txt-instawebmodulePath"></a>instaweb.modulePath </dt>
+<dd>
+<p>The default module path for <a href='{{< relurl "docs/git-instaweb" >}}'>git-instaweb[1]</a> to use
+instead of /usr/lib/apache2/modules.  Only used if httpd
+is Apache.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-instawebport"> <a class="anchor" href="#Documentation/git-config.txt-instawebport"></a>instaweb.port </dt>
+<dd>
+<p>The port number to bind the gitweb httpd to. See
+<a href='{{< relurl "docs/git-instaweb" >}}'>git-instaweb[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-interactivesingleKey"> <a class="anchor" href="#Documentation/git-config.txt-interactivesingleKey"></a>interactive.singleKey </dt>
+<dd>
+<p>When set to true, allow the user to provide one-letter input
+with a single key (i.e., without hitting the Enter key) in
+interactive commands.  This is currently used by the <code>--patch</code>
+mode of <a href='{{< relurl "docs/git-add" >}}'>git-add[1]</a>, <a href='{{< relurl "docs/git-checkout" >}}'>git-checkout[1]</a>,
+<a href='{{< relurl "docs/git-restore" >}}'>git-restore[1]</a>, <a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a>,
+<a href='{{< relurl "docs/git-reset" >}}'>git-reset[1]</a>, and <a href='{{< relurl "docs/git-stash" >}}'>git-stash[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-interactivediffFilter"> <a class="anchor" href="#Documentation/git-config.txt-interactivediffFilter"></a>interactive.diffFilter </dt>
+<dd>
+<p>When an interactive command (such as <code>git add --patch</code>) shows
+a colorized diff, git will pipe the diff through the shell
+command defined by this configuration variable. The command may
+mark up the diff further for human consumption, provided that it
+retains a one-to-one correspondence with the lines in the
+original diff. Defaults to disabled (no filtering).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-logabbrevCommit"> <a class="anchor" href="#Documentation/git-config.txt-logabbrevCommit"></a>log.abbrevCommit </dt>
+<dd>
+<p>If true, makes <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a>, <a href='{{< relurl "docs/git-show" >}}'>git-show[1]</a>, and
+<a href='{{< relurl "docs/git-whatchanged" >}}'>git-whatchanged[1]</a> assume <code>--abbrev-commit</code>. You may
+override this option with <code>--no-abbrev-commit</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-logdate"> <a class="anchor" href="#Documentation/git-config.txt-logdate"></a>log.date </dt>
+<dd>
+<p>Set the default date-time mode for the <em>log</em> command.
+Setting a value for log.date is similar to using <em>git log</em>'s
+<code>--date</code> option.  See <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a> for details.</p>
+<div class="paragraph">
+<p>If the format is set to "auto:foo" and the pager is in use, format
+"foo" will be used for the date format. Otherwise, "default" will
+be used.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-logdecorate"> <a class="anchor" href="#Documentation/git-config.txt-logdecorate"></a>log.decorate </dt>
+<dd>
+<p>Print out the ref names of any commits that are shown by the log
+command. If <em>short</em> is specified, the ref name prefixes <em>refs/heads/</em>,
+<em>refs/tags/</em> and <em>refs/remotes/</em> will not be printed. If <em>full</em> is
+specified, the full ref name (including prefix) will be printed.
+If <em>auto</em> is specified, then if the output is going to a terminal,
+the ref names are shown as if <em>short</em> were given, otherwise no ref
+names are shown. This is the same as the <code>--decorate</code> option
+of the <code>git log</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-loginitialDecorationSet"> <a class="anchor" href="#Documentation/git-config.txt-loginitialDecorationSet"></a>log.initialDecorationSet </dt>
+<dd>
+<p>By default, <code>git log</code> only shows decorations for certain known ref
+namespaces. If <em>all</em> is specified, then show all refs as
+decorations.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-logexcludeDecoration"> <a class="anchor" href="#Documentation/git-config.txt-logexcludeDecoration"></a>log.excludeDecoration </dt>
+<dd>
+<p>Exclude the specified patterns from the log decorations. This is
+similar to the <code>--decorate-refs-exclude</code> command-line option, but
+the config option can be overridden by the <code>--decorate-refs</code>
+option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-logdiffMerges"> <a class="anchor" href="#Documentation/git-config.txt-logdiffMerges"></a>log.diffMerges </dt>
+<dd>
+<p>Set diff format to be used when <code>--diff-merges=on</code> is
+specified, see <code>--diff-merges</code> in <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a> for
+details. Defaults to <code>separate</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-logfollow"> <a class="anchor" href="#Documentation/git-config.txt-logfollow"></a>log.follow </dt>
+<dd>
+<p>If <code>true</code>, <code>git log</code> will act as if the <code>--follow</code> option was used when
+a single &lt;path&gt; is given.  This has the same limitations as <code>--follow</code>,
+i.e. it cannot be used to follow multiple files and does not work well
+on non-linear history.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-loggraphColors"> <a class="anchor" href="#Documentation/git-config.txt-loggraphColors"></a>log.graphColors </dt>
+<dd>
+<p>A list of colors, separated by commas, that can be used to draw
+history lines in <code>git log --graph</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-logshowRoot"> <a class="anchor" href="#Documentation/git-config.txt-logshowRoot"></a>log.showRoot </dt>
+<dd>
+<p>If true, the initial commit will be shown as a big creation event.
+This is equivalent to a diff against an empty tree.
+Tools like <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a> or <a href='{{< relurl "docs/git-whatchanged" >}}'>git-whatchanged[1]</a>, which
+normally hide the root commit will now show it. True by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-logshowSignature"> <a class="anchor" href="#Documentation/git-config.txt-logshowSignature"></a>log.showSignature </dt>
+<dd>
+<p>If true, makes <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a>, <a href='{{< relurl "docs/git-show" >}}'>git-show[1]</a>, and
+<a href='{{< relurl "docs/git-whatchanged" >}}'>git-whatchanged[1]</a> assume <code>--show-signature</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-logmailmap"> <a class="anchor" href="#Documentation/git-config.txt-logmailmap"></a>log.mailmap </dt>
+<dd>
+<p>If true, makes <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a>, <a href='{{< relurl "docs/git-show" >}}'>git-show[1]</a>, and
+<a href='{{< relurl "docs/git-whatchanged" >}}'>git-whatchanged[1]</a> assume <code>--use-mailmap</code>, otherwise
+assume <code>--no-use-mailmap</code>. True by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-lsrefsunborn"> <a class="anchor" href="#Documentation/git-config.txt-lsrefsunborn"></a>lsrefs.unborn </dt>
+<dd>
+<p>May be "advertise" (the default), "allow", or "ignore". If "advertise",
+the server will respond to the client sending "unborn" (as described in
+<a href='{{< relurl "docs/gitprotocol-v2" >}}'>gitprotocol-v2[5]</a>) and will advertise support for this feature during the
+protocol v2 capability advertisement. "allow" is the same as
+"advertise" except that the server will not advertise support for this
+feature; this is useful for load-balanced servers that cannot be
+updated atomically (for example), since the administrator could
+configure "allow", then after a delay, configure "advertise".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mailinfoscissors"> <a class="anchor" href="#Documentation/git-config.txt-mailinfoscissors"></a>mailinfo.scissors </dt>
+<dd>
+<p>If true, makes <a href='{{< relurl "docs/git-mailinfo" >}}'>git-mailinfo[1]</a> (and therefore
+<a href='{{< relurl "docs/git-am" >}}'>git-am[1]</a>) act by default as if the --scissors option
+was provided on the command-line. When active, this feature
+removes everything from the message body before a scissors
+line (i.e. consisting mainly of "&gt;8", "8&lt;" and "-").</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mailmapfile"> <a class="anchor" href="#Documentation/git-config.txt-mailmapfile"></a>mailmap.file </dt>
+<dd>
+<p>The location of an augmenting mailmap file. The default
+mailmap, located in the root of the repository, is loaded
+first, then the mailmap file pointed to by this variable.
+The location of the mailmap file may be in a repository
+subdirectory, or somewhere outside of the repository itself.
+See <a href='{{< relurl "docs/git-shortlog" >}}'>git-shortlog[1]</a> and <a href='{{< relurl "docs/git-blame" >}}'>git-blame[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mailmapblob"> <a class="anchor" href="#Documentation/git-config.txt-mailmapblob"></a>mailmap.blob </dt>
+<dd>
+<p>Like <code>mailmap.file</code>, but consider the value as a reference to a
+blob in the repository. If both <code>mailmap.file</code> and
+<code>mailmap.blob</code> are given, both are parsed, with entries from
+<code>mailmap.file</code> taking precedence. In a bare repository, this
+defaults to <code>HEAD:.mailmap</code>. In a non-bare repository, it
+defaults to empty.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-maintenanceauto"> <a class="anchor" href="#Documentation/git-config.txt-maintenanceauto"></a>maintenance.auto </dt>
+<dd>
+<p>This boolean config option controls whether some commands run
+<code>git maintenance run --auto</code> after doing their normal work. Defaults
+to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-maintenancestrategy"> <a class="anchor" href="#Documentation/git-config.txt-maintenancestrategy"></a>maintenance.strategy </dt>
+<dd>
+<p>This string config option provides a way to specify one of a few
+recommended schedules for background maintenance. This only affects
+which tasks are run during <code>git maintenance run --schedule=X</code>
+commands, provided no <code>--task=&lt;task&gt;</code> arguments are provided.
+Further, if a <code>maintenance.&lt;task&gt;.schedule</code> config value is set,
+then that value is used instead of the one provided by
+<code>maintenance.strategy</code>. The possible strategy strings are:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>none</code>: This default setting implies no tasks are run at any schedule.</p>
+</li>
+<li>
+<p><code>incremental</code>: This setting optimizes for performing small maintenance
+activities that do not delete any data. This does not schedule the <code>gc</code>
+task, but runs the <code>prefetch</code> and <code>commit-graph</code> tasks hourly, the
+<code>loose-objects</code> and <code>incremental-repack</code> tasks daily, and the <code>pack-refs</code>
+task weekly.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-maintenancelttaskgtenabled"> <a class="anchor" href="#Documentation/git-config.txt-maintenancelttaskgtenabled"></a>maintenance.&lt;task&gt;.enabled </dt>
+<dd>
+<p>This boolean config option controls whether the maintenance task
+with name <code>&lt;task&gt;</code> is run when no <code>--task</code> option is specified to
+<code>git maintenance run</code>. These config values are ignored if a
+<code>--task</code> option exists. By default, only <code>maintenance.gc.enabled</code>
+is true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-maintenancelttaskgtschedule"> <a class="anchor" href="#Documentation/git-config.txt-maintenancelttaskgtschedule"></a>maintenance.&lt;task&gt;.schedule </dt>
+<dd>
+<p>This config option controls whether or not the given <code>&lt;task&gt;</code> runs
+during a <code>git maintenance run --schedule=&lt;frequency&gt;</code> command. The
+value must be one of "hourly", "daily", or "weekly".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-maintenancecommit-graphauto"> <a class="anchor" href="#Documentation/git-config.txt-maintenancecommit-graphauto"></a>maintenance.commit-graph.auto </dt>
+<dd>
+<p>This integer config option controls how often the <code>commit-graph</code> task
+should be run as part of <code>git maintenance run --auto</code>. If zero, then
+the <code>commit-graph</code> task will not run with the <code>--auto</code> option. A
+negative value will force the task to run every time. Otherwise, a
+positive value implies the command should run when the number of
+reachable commits that are not in the commit-graph file is at least
+the value of <code>maintenance.commit-graph.auto</code>. The default value is
+100.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-maintenanceloose-objectsauto"> <a class="anchor" href="#Documentation/git-config.txt-maintenanceloose-objectsauto"></a>maintenance.loose-objects.auto </dt>
+<dd>
+<p>This integer config option controls how often the <code>loose-objects</code> task
+should be run as part of <code>git maintenance run --auto</code>. If zero, then
+the <code>loose-objects</code> task will not run with the <code>--auto</code> option. A
+negative value will force the task to run every time. Otherwise, a
+positive value implies the command should run when the number of
+loose objects is at least the value of <code>maintenance.loose-objects.auto</code>.
+The default value is 100.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-maintenanceincremental-repackauto"> <a class="anchor" href="#Documentation/git-config.txt-maintenanceincremental-repackauto"></a>maintenance.incremental-repack.auto </dt>
+<dd>
+<p>This integer config option controls how often the <code>incremental-repack</code>
+task should be run as part of <code>git maintenance run --auto</code>. If zero,
+then the <code>incremental-repack</code> task will not run with the <code>--auto</code>
+option. A negative value will force the task to run every time.
+Otherwise, a positive value implies the command should run when the
+number of pack-files not in the multi-pack-index is at least the value
+of <code>maintenance.incremental-repack.auto</code>. The default value is 10.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-manviewer"> <a class="anchor" href="#Documentation/git-config.txt-manviewer"></a>man.viewer </dt>
+<dd>
+<p>Specify the programs that may be used to display help in the
+<em>man</em> format. See <a href='{{< relurl "docs/git-help" >}}'>git-help[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-manlttoolgtcmd"> <a class="anchor" href="#Documentation/git-config.txt-manlttoolgtcmd"></a>man.&lt;tool&gt;.cmd </dt>
+<dd>
+<p>Specify the command to invoke the specified man viewer. The
+specified command is evaluated in shell with the man page
+passed as an argument. (See <a href='{{< relurl "docs/git-help" >}}'>git-help[1]</a>.)</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-manlttoolgtpath"> <a class="anchor" href="#Documentation/git-config.txt-manlttoolgtpath"></a>man.&lt;tool&gt;.path </dt>
+<dd>
+<p>Override the path for the given tool that may be used to
+display help in the <em>man</em> format. See <a href='{{< relurl "docs/git-help" >}}'>git-help[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergeconflictStyle"> <a class="anchor" href="#Documentation/git-config.txt-mergeconflictStyle"></a>merge.conflictStyle </dt>
+<dd>
+<p>Specify the style in which conflicted hunks are written out to
+working tree files upon merge.  The default is "merge", which
+shows a <code>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</code> conflict marker, changes made by one side,
+a <code>=======</code> marker, changes made by the other side, and then
+a <code>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</code> marker.  An alternate style, "diff3", adds a <code>|||||||</code>
+marker and the original text before the <code>=======</code> marker.  The
+"merge" style tends to produce smaller conflict regions than diff3,
+both because of the exclusion of the original text, and because
+when a subset of lines match on the two sides, they are just pulled
+out of the conflict region.  Another alternate style, "zdiff3", is
+similar to diff3 but removes matching lines on the two sides from
+the conflict region when those matching lines appear near either
+the beginning or end of a conflict region.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergedefaultToUpstream"> <a class="anchor" href="#Documentation/git-config.txt-mergedefaultToUpstream"></a>merge.defaultToUpstream </dt>
+<dd>
+<p>If merge is called without any commit argument, merge the upstream
+branches configured for the current branch by using their last
+observed values stored in their remote-tracking branches.
+The values of the <code>branch.&lt;current branch&gt;.merge</code> that name the
+branches at the remote named by <code>branch.&lt;current branch&gt;.remote</code>
+are consulted, and then they are mapped via <code>remote.&lt;remote&gt;.fetch</code>
+to their corresponding remote-tracking branches, and the tips of
+these tracking branches are merged. Defaults to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergeff"> <a class="anchor" href="#Documentation/git-config.txt-mergeff"></a>merge.ff </dt>
+<dd>
+<p>By default, Git does not create an extra merge commit when merging
+a commit that is a descendant of the current commit. Instead, the
+tip of the current branch is fast-forwarded. When set to <code>false</code>,
+this variable tells Git to create an extra merge commit in such
+a case (equivalent to giving the <code>--no-ff</code> option from the command
+line). When set to <code>only</code>, only such fast-forward merges are
+allowed (equivalent to giving the <code>--ff-only</code> option from the
+command line).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergeverifySignatures"> <a class="anchor" href="#Documentation/git-config.txt-mergeverifySignatures"></a>merge.verifySignatures </dt>
+<dd>
+<p>If true, this is equivalent to the --verify-signatures command
+line option. See <a href='{{< relurl "docs/git-merge" >}}'>git-merge[1]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergebranchdesc"> <a class="anchor" href="#Documentation/git-config.txt-mergebranchdesc"></a>merge.branchdesc </dt>
+<dd>
+<p>In addition to branch names, populate the log message with
+the branch description text associated with them.  Defaults
+to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergelog"> <a class="anchor" href="#Documentation/git-config.txt-mergelog"></a>merge.log </dt>
+<dd>
+<p>In addition to branch names, populate the log message with at
+most the specified number of one-line descriptions from the
+actual commits that are being merged.  Defaults to false, and
+true is a synonym for 20.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergesuppressDest"> <a class="anchor" href="#Documentation/git-config.txt-mergesuppressDest"></a>merge.suppressDest </dt>
+<dd>
+<p>By adding a glob that matches the names of integration
+branches to this multi-valued configuration variable, the
+default merge message computed for merges into these
+integration branches will omit "into &lt;branch name&gt;" from
+its title.</p>
+<div class="paragraph">
+<p>An element with an empty value can be used to clear the list
+of globs accumulated from previous configuration entries.
+When there is no <code>merge.suppressDest</code> variable defined, the
+default value of <code>master</code> is used for backward compatibility.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergerenameLimit"> <a class="anchor" href="#Documentation/git-config.txt-mergerenameLimit"></a>merge.renameLimit </dt>
+<dd>
+<p>The number of files to consider in the exhaustive portion of
+rename detection during a merge.  If not specified, defaults
+to the value of diff.renameLimit.  If neither
+merge.renameLimit nor diff.renameLimit are specified,
+currently defaults to 7000.  This setting has no effect if
+rename detection is turned off.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergerenames"> <a class="anchor" href="#Documentation/git-config.txt-mergerenames"></a>merge.renames </dt>
+<dd>
+<p>Whether Git detects renames.  If set to "false", rename detection
+is disabled. If set to "true", basic rename detection is enabled.
+Defaults to the value of diff.renames.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergedirectoryRenames"> <a class="anchor" href="#Documentation/git-config.txt-mergedirectoryRenames"></a>merge.directoryRenames </dt>
+<dd>
+<p>Whether Git detects directory renames, affecting what happens at
+merge time to new files added to a directory on one side of
+history when that directory was renamed on the other side of
+history.  If merge.directoryRenames is set to "false", directory
+rename detection is disabled, meaning that such new files will be
+left behind in the old directory.  If set to "true", directory
+rename detection is enabled, meaning that such new files will be
+moved into the new directory.  If set to "conflict", a conflict
+will be reported for such paths.  If merge.renames is false,
+merge.directoryRenames is ignored and treated as false.  Defaults
+to "conflict".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergerenormalize"> <a class="anchor" href="#Documentation/git-config.txt-mergerenormalize"></a>merge.renormalize </dt>
+<dd>
+<p>Tell Git that canonical representation of files in the
+repository has changed over time (e.g. earlier commits record
+text files with CRLF line endings, but recent ones use LF line
+endings).  In such a repository, Git can convert the data
+recorded in commits to a canonical form before performing a
+merge to reduce unnecessary conflicts.  For more information,
+see section "Merging branches with differing checkin/checkout
+attributes" in <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergestat"> <a class="anchor" href="#Documentation/git-config.txt-mergestat"></a>merge.stat </dt>
+<dd>
+<p>Whether to print the diffstat between ORIG_HEAD and the merge result
+at the end of the merge.  True by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergeautoStash"> <a class="anchor" href="#Documentation/git-config.txt-mergeautoStash"></a>merge.autoStash </dt>
+<dd>
+<p>When set to true, automatically create a temporary stash entry
+before the operation begins, and apply it after the operation
+ends.  This means that you can run merge on a dirty worktree.
+However, use with care: the final stash application after a
+successful merge might result in non-trivial conflicts.
+This option can be overridden by the <code>--no-autostash</code> and
+<code>--autostash</code> options of <a href='{{< relurl "docs/git-merge" >}}'>git-merge[1]</a>.
+Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetool"> <a class="anchor" href="#Documentation/git-config.txt-mergetool"></a>merge.tool </dt>
+<dd>
+<p>Controls which merge tool is used by <a href='{{< relurl "docs/git-mergetool" >}}'>git-mergetool[1]</a>.
+The list below shows the valid built-in values.
+Any other value is treated as a custom merge tool and requires
+that a corresponding mergetool.&lt;tool&gt;.cmd variable is defined.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergeguitool"> <a class="anchor" href="#Documentation/git-config.txt-mergeguitool"></a>merge.guitool </dt>
+<dd>
+<p>Controls which merge tool is used by <a href='{{< relurl "docs/git-mergetool" >}}'>git-mergetool[1]</a> when the
+-g/--gui flag is specified. The list below shows the valid built-in values.
+Any other value is treated as a custom merge tool and requires that a
+corresponding mergetool.&lt;guitool&gt;.cmd variable is defined.</p>
+<div class="ulist">
+<ul>
+<li>
+<p>araxis</p>
+</li>
+<li>
+<p>bc</p>
+</li>
+<li>
+<p>codecompare</p>
+</li>
+<li>
+<p>deltawalker</p>
+</li>
+<li>
+<p>diffmerge</p>
+</li>
+<li>
+<p>diffuse</p>
+</li>
+<li>
+<p>ecmerge</p>
+</li>
+<li>
+<p>emerge</p>
+</li>
+<li>
+<p>examdiff</p>
+</li>
+<li>
+<p>guiffy</p>
+</li>
+<li>
+<p>gvimdiff</p>
+</li>
+<li>
+<p>kdiff3</p>
+</li>
+<li>
+<p>meld</p>
+</li>
+<li>
+<p>nvimdiff</p>
+</li>
+<li>
+<p>opendiff</p>
+</li>
+<li>
+<p>p4merge</p>
+</li>
+<li>
+<p>smerge</p>
+</li>
+<li>
+<p>tkdiff</p>
+</li>
+<li>
+<p>tortoisemerge</p>
+</li>
+<li>
+<p>vimdiff</p>
+</li>
+<li>
+<p>winmerge</p>
+</li>
+<li>
+<p>xxdiff</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergeverbosity"> <a class="anchor" href="#Documentation/git-config.txt-mergeverbosity"></a>merge.verbosity </dt>
+<dd>
+<p>Controls the amount of output shown by the recursive merge
+strategy.  Level 0 outputs nothing except a final error
+message if conflicts were detected. Level 1 outputs only
+conflicts, 2 outputs conflicts and file changes.  Level 5 and
+above outputs debugging information.  The default is level 2.
+Can be overridden by the <code>GIT_MERGE_VERBOSITY</code> environment variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergeltdrivergtname"> <a class="anchor" href="#Documentation/git-config.txt-mergeltdrivergtname"></a>merge.&lt;driver&gt;.name </dt>
+<dd>
+<p>Defines a human-readable name for a custom low-level
+merge driver.  See <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergeltdrivergtdriver"> <a class="anchor" href="#Documentation/git-config.txt-mergeltdrivergtdriver"></a>merge.&lt;driver&gt;.driver </dt>
+<dd>
+<p>Defines the command that implements a custom low-level
+merge driver.  See <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergeltdrivergtrecursive"> <a class="anchor" href="#Documentation/git-config.txt-mergeltdrivergtrecursive"></a>merge.&lt;driver&gt;.recursive </dt>
+<dd>
+<p>Names a low-level merge driver to be used when
+performing an internal merge between common ancestors.
+See <a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoollttoolgtpath"> <a class="anchor" href="#Documentation/git-config.txt-mergetoollttoolgtpath"></a>mergetool.&lt;tool&gt;.path </dt>
+<dd>
+<p>Override the path for the given tool.  This is useful in case
+your tool is not in the PATH.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoollttoolgtcmd"> <a class="anchor" href="#Documentation/git-config.txt-mergetoollttoolgtcmd"></a>mergetool.&lt;tool&gt;.cmd </dt>
+<dd>
+<p>Specify the command to invoke the specified merge tool.  The
+specified command is evaluated in shell with the following
+variables available: <em>BASE</em> is the name of a temporary file
+containing the common base of the files to be merged, if available;
+<em>LOCAL</em> is the name of a temporary file containing the contents of
+the file on the current branch; <em>REMOTE</em> is the name of a temporary
+file containing the contents of the file from the branch being
+merged; <em>MERGED</em> contains the name of the file to which the merge
+tool should write the results of a successful merge.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoollttoolgthideResolved"> <a class="anchor" href="#Documentation/git-config.txt-mergetoollttoolgthideResolved"></a>mergetool.&lt;tool&gt;.hideResolved </dt>
+<dd>
+<p>Allows the user to override the global <code>mergetool.hideResolved</code> value
+for a specific tool. See <code>mergetool.hideResolved</code> for the full
+description.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoollttoolgttrustExitCode"> <a class="anchor" href="#Documentation/git-config.txt-mergetoollttoolgttrustExitCode"></a>mergetool.&lt;tool&gt;.trustExitCode </dt>
+<dd>
+<p>For a custom merge command, specify whether the exit code of
+the merge command can be used to determine whether the merge was
+successful.  If this is not set to true then the merge target file
+timestamp is checked, and the merge is assumed to have been successful
+if the file has been updated; otherwise, the user is prompted to
+indicate the success of the merge.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoolmeldhasOutput"> <a class="anchor" href="#Documentation/git-config.txt-mergetoolmeldhasOutput"></a>mergetool.meld.hasOutput </dt>
+<dd>
+<p>Older versions of <code>meld</code> do not support the <code>--output</code> option.
+Git will attempt to detect whether <code>meld</code> supports <code>--output</code>
+by inspecting the output of <code>meld --help</code>.  Configuring
+<code>mergetool.meld.hasOutput</code> will make Git skip these checks and
+use the configured value instead.  Setting <code>mergetool.meld.hasOutput</code>
+to <code>true</code> tells Git to unconditionally use the <code>--output</code> option,
+and <code>false</code> avoids using <code>--output</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoolmelduseAutoMerge"> <a class="anchor" href="#Documentation/git-config.txt-mergetoolmelduseAutoMerge"></a>mergetool.meld.useAutoMerge </dt>
+<dd>
+<p>When the <code>--auto-merge</code> is given, meld will merge all non-conflicting
+parts automatically, highlight the conflicting parts, and wait for
+user decision.  Setting <code>mergetool.meld.useAutoMerge</code> to <code>true</code> tells
+Git to unconditionally use the <code>--auto-merge</code> option with <code>meld</code>.
+Setting this value to <code>auto</code> makes git detect whether <code>--auto-merge</code>
+is supported and will only use <code>--auto-merge</code> when available.  A
+value of <code>false</code> avoids using <code>--auto-merge</code> altogether, and is the
+default value.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoolltvimdiffvariantgtlayout"> <a class="anchor" href="#Documentation/git-config.txt-mergetoolltvimdiffvariantgtlayout"></a>mergetool.&lt;vimdiff variant&gt;.layout </dt>
+<dd>
+<p>Configure the split window layout for vimdiff&#8217;s <code>&lt;variant&gt;</code>, which is any of <code>vimdiff</code>,
+<code>nvimdiff</code>, <code>gvimdiff</code>.
+Upon launching <code>git mergetool</code> with <code>--tool=&lt;variant&gt;</code> (or without <code>--tool</code>
+if <code>merge.tool</code> is configured as <code>&lt;variant&gt;</code>), Git will consult
+<code>mergetool.&lt;variant&gt;.layout</code> to determine the tool&#8217;s layout. If the
+variant-specific configuration is not available, <code>vimdiff</code>'s is used as
+fallback.  If that too is not available, a default layout with 4 windows
+will be used.  To configure the layout, see the <code>BACKEND SPECIFIC HINTS</code>
+section in <a href='{{< relurl "docs/git-mergetool" >}}'>git-mergetool[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoolhideResolved"> <a class="anchor" href="#Documentation/git-config.txt-mergetoolhideResolved"></a>mergetool.hideResolved </dt>
+<dd>
+<p>During a merge, Git will automatically resolve as many conflicts as
+possible and write the <em>MERGED</em> file containing conflict markers around
+any conflicts that it cannot resolve; <em>LOCAL</em> and <em>REMOTE</em> normally
+represent the versions of the file from before Git&#8217;s conflict
+resolution. This flag causes <em>LOCAL</em> and <em>REMOTE</em> to be overwritten so
+that only the unresolved conflicts are presented to the merge tool. Can
+be configured per-tool via the <code>mergetool.&lt;tool&gt;.hideResolved</code>
+configuration variable. Defaults to <code>false</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoolkeepBackup"> <a class="anchor" href="#Documentation/git-config.txt-mergetoolkeepBackup"></a>mergetool.keepBackup </dt>
+<dd>
+<p>After performing a merge, the original file with conflict markers
+can be saved as a file with a <code>.orig</code> extension.  If this variable
+is set to <code>false</code> then this file is not preserved.  Defaults to
+<code>true</code> (i.e. keep the backup files).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoolkeepTemporaries"> <a class="anchor" href="#Documentation/git-config.txt-mergetoolkeepTemporaries"></a>mergetool.keepTemporaries </dt>
+<dd>
+<p>When invoking a custom merge tool, Git uses a set of temporary
+files to pass to the tool. If the tool returns an error and this
+variable is set to <code>true</code>, then these temporary files will be
+preserved; otherwise, they will be removed after the tool has
+exited. Defaults to <code>false</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoolwriteToTemp"> <a class="anchor" href="#Documentation/git-config.txt-mergetoolwriteToTemp"></a>mergetool.writeToTemp </dt>
+<dd>
+<p>Git writes temporary <em>BASE</em>, <em>LOCAL</em>, and <em>REMOTE</em> versions of
+conflicting files in the worktree by default.  Git will attempt
+to use a temporary directory for these files when set <code>true</code>.
+Defaults to <code>false</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoolprompt"> <a class="anchor" href="#Documentation/git-config.txt-mergetoolprompt"></a>mergetool.prompt </dt>
+<dd>
+<p>Prompt before each invocation of the merge resolution program.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-mergetoolguiDefault"> <a class="anchor" href="#Documentation/git-config.txt-mergetoolguiDefault"></a>mergetool.guiDefault </dt>
+<dd>
+<p>Set <code>true</code> to use the <code>merge.guitool</code> by default (equivalent to
+specifying the <code>--gui</code> argument), or <code>auto</code> to select <code>merge.guitool</code>
+or <code>merge.tool</code> depending on the presence of a <code>DISPLAY</code> environment
+variable value. The default is <code>false</code>, where the <code>--gui</code> argument
+must be provided explicitly for the <code>merge.guitool</code> to be used.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-notesmergeStrategy"> <a class="anchor" href="#Documentation/git-config.txt-notesmergeStrategy"></a>notes.mergeStrategy </dt>
+<dd>
+<p>Which merge strategy to choose by default when resolving notes
+conflicts.  Must be one of <code>manual</code>, <code>ours</code>, <code>theirs</code>, <code>union</code>, or
+<code>cat_sort_uniq</code>.  Defaults to <code>manual</code>.  See the "NOTES MERGE STRATEGIES"
+section of <a href='{{< relurl "docs/git-notes" >}}'>git-notes[1]</a> for more information on each strategy.</p>
+<div class="paragraph">
+<p>This setting can be overridden by passing the <code>--strategy</code> option to
+<a href='{{< relurl "docs/git-notes" >}}'>git-notes[1]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-notesltnamegtmergeStrategy"> <a class="anchor" href="#Documentation/git-config.txt-notesltnamegtmergeStrategy"></a>notes.&lt;name&gt;.mergeStrategy </dt>
+<dd>
+<p>Which merge strategy to choose when doing a notes merge into
+refs/notes/&lt;name&gt;.  This overrides the more general
+"notes.mergeStrategy".  See the "NOTES MERGE STRATEGIES" section in
+<a href='{{< relurl "docs/git-notes" >}}'>git-notes[1]</a> for more information on the available strategies.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-notesdisplayRef"> <a class="anchor" href="#Documentation/git-config.txt-notesdisplayRef"></a>notes.displayRef </dt>
+<dd>
+<p>Which ref (or refs, if a glob or specified more than once), in
+addition to the default set by <code>core.notesRef</code> or
+<code>GIT_NOTES_REF</code>, to read notes from when showing commit
+messages with the <em>git log</em> family of commands.</p>
+<div class="paragraph">
+<p>This setting can be overridden with the <code>GIT_NOTES_DISPLAY_REF</code>
+environment variable, which must be a colon separated list of refs or
+globs.</p>
+</div>
+<div class="paragraph">
+<p>A warning will be issued for refs that do not exist,
+but a glob that does not match any refs is silently ignored.</p>
+</div>
+<div class="paragraph">
+<p>This setting can be disabled by the <code>--no-notes</code> option to the <em>git
+log</em> family of commands, or by the <code>--notes=&lt;ref&gt;</code> option accepted by
+those commands.</p>
+</div>
+<div class="paragraph">
+<p>The effective value of "core.notesRef" (possibly overridden by
+GIT_NOTES_REF) is also implicitly added to the list of refs to be
+displayed.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-notesrewriteltcommandgt"> <a class="anchor" href="#Documentation/git-config.txt-notesrewriteltcommandgt"></a>notes.rewrite.&lt;command&gt; </dt>
+<dd>
+<p>When rewriting commits with &lt;command&gt; (currently <code>amend</code> or
+<code>rebase</code>), if this variable is <code>false</code>, git will not copy
+notes from the original to the rewritten commit.  Defaults to
+<code>true</code>.  See also "<code>notes.rewriteRef</code>" below.</p>
+<div class="paragraph">
+<p>This setting can be overridden with the <code>GIT_NOTES_REWRITE_REF</code>
+environment variable, which must be a colon separated list of refs or
+globs.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-notesrewriteMode"> <a class="anchor" href="#Documentation/git-config.txt-notesrewriteMode"></a>notes.rewriteMode </dt>
+<dd>
+<p>When copying notes during a rewrite (see the
+"notes.rewrite.&lt;command&gt;" option), determines what to do if
+the target commit already has a note.  Must be one of
+<code>overwrite</code>, <code>concatenate</code>, <code>cat_sort_uniq</code>, or <code>ignore</code>.
+Defaults to <code>concatenate</code>.</p>
+<div class="paragraph">
+<p>This setting can be overridden with the <code>GIT_NOTES_REWRITE_MODE</code>
+environment variable.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-notesrewriteRef"> <a class="anchor" href="#Documentation/git-config.txt-notesrewriteRef"></a>notes.rewriteRef </dt>
+<dd>
+<p>When copying notes during a rewrite, specifies the (fully
+qualified) ref whose notes should be copied.  May be a glob,
+in which case notes in all matching refs will be copied.  You
+may also specify this configuration several times.</p>
+<div class="paragraph">
+<p>Does not have a default value; you must configure this variable to
+enable note rewriting.  Set it to <code>refs/notes/commits</code> to enable
+rewriting for the default commit notes.</p>
+</div>
+<div class="paragraph">
+<p>Can be overridden with the <code>GIT_NOTES_REWRITE_REF</code> environment variable.
+See <code>notes.rewrite.&lt;command&gt;</code> above for a further description of its format.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packwindow"> <a class="anchor" href="#Documentation/git-config.txt-packwindow"></a>pack.window </dt>
+<dd>
+<p>The size of the window used by <a href='{{< relurl "docs/git-pack-objects" >}}'>git-pack-objects[1]</a> when no
+window size is given on the command line. Defaults to 10.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packdepth"> <a class="anchor" href="#Documentation/git-config.txt-packdepth"></a>pack.depth </dt>
+<dd>
+<p>The maximum delta depth used by <a href='{{< relurl "docs/git-pack-objects" >}}'>git-pack-objects[1]</a> when no
+maximum depth is given on the command line. Defaults to 50.
+Maximum value is 4095.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packwindowMemory"> <a class="anchor" href="#Documentation/git-config.txt-packwindowMemory"></a>pack.windowMemory </dt>
+<dd>
+<p>The maximum size of memory that is consumed by each thread
+in <a href='{{< relurl "docs/git-pack-objects" >}}'>git-pack-objects[1]</a> for pack window memory when
+no limit is given on the command line.  The value can be
+suffixed with "k", "m", or "g".  When left unconfigured (or
+set explicitly to 0), there will be no limit.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packcompression"> <a class="anchor" href="#Documentation/git-config.txt-packcompression"></a>pack.compression </dt>
+<dd>
+<p>An integer -1..9, indicating the compression level for objects
+in a pack file. -1 is the zlib default. 0 means no
+compression, and 1..9 are various speed/size tradeoffs, 9 being
+slowest.  If not set,  defaults to core.compression.  If that is
+not set,  defaults to -1, the zlib default, which is "a default
+compromise between speed and compression (currently equivalent
+to level 6)."</p>
+<div class="paragraph">
+<p>Note that changing the compression level will not automatically recompress
+all existing objects. You can force recompression by passing the -F option
+to <a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packallowPackReuse"> <a class="anchor" href="#Documentation/git-config.txt-packallowPackReuse"></a>pack.allowPackReuse </dt>
+<dd>
+<p>When true or "single", and when reachability bitmaps are
+enabled, pack-objects will try to send parts of the bitmapped
+packfile verbatim. When "multi", and when a multi-pack
+reachability bitmap is available, pack-objects will try to send
+parts of all packs in the MIDX.</p>
+<div class="paragraph">
+<p>If only a single pack bitmap is available, and <code>pack.allowPackReuse</code>
+is set to "multi", reuse parts of just the bitmapped packfile. This
+can reduce memory and CPU usage to serve fetches, but might result in
+sending a slightly larger pack. Defaults to true.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packisland"> <a class="anchor" href="#Documentation/git-config.txt-packisland"></a>pack.island </dt>
+<dd>
+<p>An extended regular expression configuring a set of delta
+islands. See "DELTA ISLANDS" in <a href='{{< relurl "docs/git-pack-objects" >}}'>git-pack-objects[1]</a>
+for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packislandCore"> <a class="anchor" href="#Documentation/git-config.txt-packislandCore"></a>pack.islandCore </dt>
+<dd>
+<p>Specify an island name which gets to have its objects be
+packed first. This creates a kind of pseudo-pack at the front
+of one pack, so that the objects from the specified island are
+hopefully faster to copy into any pack that should be served
+to a user requesting these objects. In practice this means
+that the island specified should likely correspond to what is
+the most commonly cloned in the repo. See also "DELTA ISLANDS"
+in <a href='{{< relurl "docs/git-pack-objects" >}}'>git-pack-objects[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packdeltaCacheSize"> <a class="anchor" href="#Documentation/git-config.txt-packdeltaCacheSize"></a>pack.deltaCacheSize </dt>
+<dd>
+<p>The maximum memory in bytes used for caching deltas in
+<a href='{{< relurl "docs/git-pack-objects" >}}'>git-pack-objects[1]</a> before writing them out to a pack.
+This cache is used to speed up the writing object phase by not
+having to recompute the final delta result once the best match
+for all objects is found.  Repacking large repositories on machines
+which are tight with memory might be badly impacted by this though,
+especially if this cache pushes the system into swapping.
+A value of 0 means no limit. The smallest size of 1 byte may be
+used to virtually disable this cache. Defaults to 256 MiB.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packdeltaCacheLimit"> <a class="anchor" href="#Documentation/git-config.txt-packdeltaCacheLimit"></a>pack.deltaCacheLimit </dt>
+<dd>
+<p>The maximum size of a delta, that is cached in
+<a href='{{< relurl "docs/git-pack-objects" >}}'>git-pack-objects[1]</a>. This cache is used to speed up the
+writing object phase by not having to recompute the final delta
+result once the best match for all objects is found.
+Defaults to 1000. Maximum value is 65535.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packthreads"> <a class="anchor" href="#Documentation/git-config.txt-packthreads"></a>pack.threads </dt>
+<dd>
+<p>Specifies the number of threads to spawn when searching for best
+delta matches.  This requires that <a href='{{< relurl "docs/git-pack-objects" >}}'>git-pack-objects[1]</a>
+be compiled with pthreads otherwise this option is ignored with a
+warning. This is meant to reduce packing time on multiprocessor
+machines. The required amount of memory for the delta search window
+is however multiplied by the number of threads.
+Specifying 0 will cause Git to auto-detect the number of CPUs
+and set the number of threads accordingly.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packindexVersion"> <a class="anchor" href="#Documentation/git-config.txt-packindexVersion"></a>pack.indexVersion </dt>
+<dd>
+<p>Specify the default pack index version.  Valid values are 1 for
+legacy pack index used by Git versions prior to 1.5.2, and 2 for
+the new pack index with capabilities for packs larger than 4 GB
+as well as proper protection against the repacking of corrupted
+packs.  Version 2 is the default.  Note that version 2 is enforced
+and this config option is ignored whenever the corresponding pack is
+larger than 2 GB.</p>
+<div class="paragraph">
+<p>If you have an old Git that does not understand the version 2 <code>*.idx</code> file,
+cloning or fetching over a non-native protocol (e.g. "http")
+that will copy both <code>*.pack</code> file and corresponding <code>*.idx</code> file from the
+other side may give you a repository that cannot be accessed with your
+older version of Git. If the <code>*.pack</code> file is smaller than 2 GB, however,
+you can use <a href='{{< relurl "docs/git-index-pack" >}}'>git-index-pack[1]</a> on the *.pack file to regenerate
+the <code>*.idx</code> file.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packpackSizeLimit"> <a class="anchor" href="#Documentation/git-config.txt-packpackSizeLimit"></a>pack.packSizeLimit </dt>
+<dd>
+<p>The maximum size of a pack.  This setting only affects
+packing to a file when repacking, i.e. the git:// protocol
+is unaffected.  It can be overridden by the <code>--max-pack-size</code>
+option of <a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a>.  Reaching this limit results
+in the creation of multiple packfiles.</p>
+<div class="paragraph">
+<p>Note that this option is rarely useful, and may result in a larger total
+on-disk size (because Git will not store deltas between packs) and
+worse runtime performance (object lookup within multiple packs is
+slower than a single pack, and optimizations like reachability bitmaps
+cannot cope with multiple packs).</p>
+</div>
+<div class="paragraph">
+<p>If you need to actively run Git using smaller packfiles (e.g., because your
+filesystem does not support large files), this option may help. But if
+your goal is to transmit a packfile over a medium that supports limited
+sizes (e.g., removable media that cannot store the whole repository),
+you are likely better off creating a single large packfile and splitting
+it using a generic multi-volume archive tool (e.g., Unix <code>split</code>).</p>
+</div>
+<div class="paragraph">
+<p>The minimum size allowed is limited to 1 MiB. The default is unlimited.
+Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packuseBitmaps"> <a class="anchor" href="#Documentation/git-config.txt-packuseBitmaps"></a>pack.useBitmaps </dt>
+<dd>
+<p>When true, git will use pack bitmaps (if available) when packing
+to stdout (e.g., during the server side of a fetch). Defaults to
+true. You should not generally need to turn this off unless
+you are debugging pack bitmaps.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packuseBitmapBoundaryTraversal"> <a class="anchor" href="#Documentation/git-config.txt-packuseBitmapBoundaryTraversal"></a>pack.useBitmapBoundaryTraversal </dt>
+<dd>
+<p>When true, Git will use an experimental algorithm for computing
+reachability queries with bitmaps. Instead of building up
+complete bitmaps for all of the negated tips and then OR-ing
+them together, consider negated tips with existing bitmaps as
+additive (i.e. OR-ing them into the result if they exist,
+ignoring them otherwise), and build up a bitmap at the boundary
+instead.</p>
+<div class="paragraph">
+<p>When using this algorithm, Git may include too many objects as a result
+of not opening up trees belonging to certain UNINTERESTING commits. This
+inexactness matches the non-bitmap traversal algorithm.</p>
+</div>
+<div class="paragraph">
+<p>In many cases, this can provide a speed-up over the exact algorithm,
+particularly when there is poor bitmap coverage of the negated side of
+the query.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packuseSparse"> <a class="anchor" href="#Documentation/git-config.txt-packuseSparse"></a>pack.useSparse </dt>
+<dd>
+<p>When true, git will default to using the <em>--sparse</em> option in
+<em>git pack-objects</em> when the <em>--revs</em> option is present. This
+algorithm only walks trees that appear in paths that introduce new
+objects. This can have significant performance benefits when
+computing a pack to send a small change. However, it is possible
+that extra objects are added to the pack-file if the included
+commits contain certain types of direct renames. Default is
+<code>true</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packpreferBitmapTips"> <a class="anchor" href="#Documentation/git-config.txt-packpreferBitmapTips"></a>pack.preferBitmapTips </dt>
+<dd>
+<p>When selecting which commits will receive bitmaps, prefer a
+commit at the tip of any reference that is a suffix of any value
+of this configuration over any other commits in the "selection
+window".</p>
+<div class="paragraph">
+<p>Note that setting this configuration to <code>refs/foo</code> does not mean that
+the commits at the tips of <code>refs/foo/bar</code> and <code>refs/foo/baz</code> will
+necessarily be selected. This is because commits are selected for
+bitmaps from within a series of windows of variable length.</p>
+</div>
+<div class="paragraph">
+<p>If a commit at the tip of any reference which is a suffix of any value
+of this configuration is seen in a window, it is immediately given
+preference over any other commit in that window.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packwriteBitmapsdeprecated"> <a class="anchor" href="#Documentation/git-config.txt-packwriteBitmapsdeprecated"></a>pack.writeBitmaps (deprecated) </dt>
+<dd>
+<p>This is a deprecated synonym for <code>repack.writeBitmaps</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packwriteBitmapHashCache"> <a class="anchor" href="#Documentation/git-config.txt-packwriteBitmapHashCache"></a>pack.writeBitmapHashCache </dt>
+<dd>
+<p>When true, git will include a "hash cache" section in the bitmap
+index (if one is written). This cache can be used to feed git&#8217;s
+delta heuristics, potentially leading to better deltas between
+bitmapped and non-bitmapped objects (e.g., when serving a fetch
+between an older, bitmapped pack and objects that have been
+pushed since the last gc). The downside is that it consumes 4
+bytes per object of disk space. Defaults to true.</p>
+<div class="paragraph">
+<p>When writing a multi-pack reachability bitmap, no new namehashes are
+computed; instead, any namehashes stored in an existing bitmap are
+permuted into their appropriate location when writing a new bitmap.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packwriteBitmapLookupTable"> <a class="anchor" href="#Documentation/git-config.txt-packwriteBitmapLookupTable"></a>pack.writeBitmapLookupTable </dt>
+<dd>
+<p>When true, Git will include a "lookup table" section in the
+bitmap index (if one is written). This table is used to defer
+loading individual bitmaps as late as possible. This can be
+beneficial in repositories that have relatively large bitmap
+indexes. Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packreadReverseIndex"> <a class="anchor" href="#Documentation/git-config.txt-packreadReverseIndex"></a>pack.readReverseIndex </dt>
+<dd>
+<p>When true, git will read any .rev file(s) that may be available
+(see: <a href='{{< relurl "docs/gitformat-pack" >}}'>gitformat-pack[5]</a>). When false, the reverse index
+will be generated from scratch and stored in memory. Defaults to
+true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-packwriteReverseIndex"> <a class="anchor" href="#Documentation/git-config.txt-packwriteReverseIndex"></a>pack.writeReverseIndex </dt>
+<dd>
+<p>When true, git will write a corresponding .rev file (see:
+<a href='{{< relurl "docs/gitformat-pack" >}}'>gitformat-pack[5]</a>)
+for each new packfile that it writes in all places except for
+<a href='{{< relurl "docs/git-fast-import" >}}'>git-fast-import[1]</a> and in the bulk checkin mechanism.
+Defaults to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pagerltcmdgt"> <a class="anchor" href="#Documentation/git-config.txt-pagerltcmdgt"></a>pager.&lt;cmd&gt; </dt>
+<dd>
+<p>If the value is boolean, turns on or off pagination of the
+output of a particular Git subcommand when writing to a tty.
+Otherwise, turns on pagination for the subcommand using the
+pager specified by the value of <code>pager.&lt;cmd&gt;</code>.  If <code>--paginate</code>
+or <code>--no-pager</code> is specified on the command line, it takes
+precedence over this option.  To disable pagination for all
+commands, set <code>core.pager</code> or <code>GIT_PAGER</code> to <code>cat</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-prettyltnamegt"> <a class="anchor" href="#Documentation/git-config.txt-prettyltnamegt"></a>pretty.&lt;name&gt; </dt>
+<dd>
+<p>Alias for a --pretty= format string, as specified in
+<a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a>. Any aliases defined here can be used just
+as the built-in pretty formats could. For example,
+running <code>git config pretty.changelog "format:* %H %s"</code>
+would cause the invocation <code>git log --pretty=changelog</code>
+to be equivalent to running <code>git log "--pretty=format:* %H %s"</code>.
+Note that an alias with the same name as a built-in format
+will be silently ignored.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-promisorquiet"> <a class="anchor" href="#Documentation/git-config.txt-promisorquiet"></a>promisor.quiet </dt>
+<dd>
+<p>If set to "true" assume <code>--quiet</code> when fetching additional
+objects for a partial clone.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-protocolallow"> <a class="anchor" href="#Documentation/git-config.txt-protocolallow"></a>protocol.allow </dt>
+<dd>
+<p>If set, provide a user defined default policy for all protocols which
+don&#8217;t explicitly have a policy (<code>protocol.&lt;name&gt;.allow</code>).  By default,
+if unset, known-safe protocols (http, https, git, ssh) have a
+default policy of <code>always</code>, known-dangerous protocols (ext) have a
+default policy of <code>never</code>, and all other protocols (including file)
+have a default policy of <code>user</code>.  Supported policies:</p>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>always</code> - protocol is always able to be used.</p>
+</li>
+<li>
+<p><code>never</code> - protocol is never able to be used.</p>
+</li>
+<li>
+<p><code>user</code> - protocol is only able to be used when <code>GIT_PROTOCOL_FROM_USER</code> is
+either unset or has a value of 1.  This policy should be used when you want a
+protocol to be directly usable by the user but don&#8217;t want it used by commands which
+execute clone/fetch/push commands without user input, e.g. recursive
+submodule initialization.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-protocolltnamegtallow"> <a class="anchor" href="#Documentation/git-config.txt-protocolltnamegtallow"></a>protocol.&lt;name&gt;.allow </dt>
+<dd>
+<p>Set a policy to be used by protocol <code>&lt;name&gt;</code> with clone/fetch/push
+commands. See <code>protocol.allow</code> above for the available policies.</p>
+<div class="paragraph">
+<p>The protocol names currently used by git are:</p>
+</div>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>file</code>: any local file-based path (including <code>file://</code> URLs,
+or local paths)</p>
+</li>
+<li>
+<p><code>git</code>: the anonymous git protocol over a direct TCP
+connection (or proxy, if configured)</p>
+</li>
+<li>
+<p><code>ssh</code>: git over ssh (including <code>host:path</code> syntax,
+<code>ssh://</code>, etc).</p>
+</li>
+<li>
+<p><code>http</code>: git over http, both "smart http" and "dumb http".
+Note that this does <em>not</em> include <code>https</code>; if you want to configure
+both, you must do so individually.</p>
+</li>
+<li>
+<p>any external helpers are named by their protocol (e.g., use
+<code>hg</code> to allow the <code>git-remote-hg</code> helper)</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-protocolversion"> <a class="anchor" href="#Documentation/git-config.txt-protocolversion"></a>protocol.version </dt>
+<dd>
+<p>If set, clients will attempt to communicate with a server
+using the specified protocol version.  If the server does
+not support it, communication falls back to version 0.
+If unset, the default is <code>2</code>.
+Supported versions:</p>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>0</code> - the original wire protocol.</p>
+</li>
+<li>
+<p><code>1</code> - the original wire protocol with the addition of a version string
+in the initial response from the server.</p>
+</li>
+<li>
+<p><code>2</code> - Wire protocol version 2, see <a href='{{< relurl "docs/gitprotocol-v2" >}}'>gitprotocol-v2[5]</a>.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pullff"> <a class="anchor" href="#Documentation/git-config.txt-pullff"></a>pull.ff </dt>
+<dd>
+<p>By default, Git does not create an extra merge commit when merging
+a commit that is a descendant of the current commit. Instead, the
+tip of the current branch is fast-forwarded. When set to <code>false</code>,
+this variable tells Git to create an extra merge commit in such
+a case (equivalent to giving the <code>--no-ff</code> option from the command
+line). When set to <code>only</code>, only such fast-forward merges are
+allowed (equivalent to giving the <code>--ff-only</code> option from the
+command line). This setting overrides <code>merge.ff</code> when pulling.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pullrebase"> <a class="anchor" href="#Documentation/git-config.txt-pullrebase"></a>pull.rebase </dt>
+<dd>
+<p>When true, rebase branches on top of the fetched branch, instead
+of merging the default branch from the default remote when "git
+pull" is run. See "branch.&lt;name&gt;.rebase" for setting this on a
+per-branch basis.</p>
+<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>
+so that the local merge commits are included in the rebase (see
+<a href='{{< relurl "docs/git-rebase" >}}'>git-rebase[1]</a> for details).</p>
+</div>
+<div class="paragraph">
+<p>When the value is <code>interactive</code> (or just <em>i</em>), the rebase is run in interactive
+mode.</p>
+</div>
+<div class="paragraph">
+<p><strong>NOTE</strong>: this is a possibly dangerous operation; do <strong>not</strong> use
+it unless you understand the implications (see <a href='{{< relurl "docs/git-rebase" >}}'>git-rebase[1]</a>
+for details).</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pulloctopus"> <a class="anchor" href="#Documentation/git-config.txt-pulloctopus"></a>pull.octopus </dt>
+<dd>
+<p>The default merge strategy to use when pulling multiple branches
+at once.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pulltwohead"> <a class="anchor" href="#Documentation/git-config.txt-pulltwohead"></a>pull.twohead </dt>
+<dd>
+<p>The default merge strategy to use when pulling a single branch.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushautoSetupRemote"> <a class="anchor" href="#Documentation/git-config.txt-pushautoSetupRemote"></a>push.autoSetupRemote </dt>
+<dd>
+<p>If set to "true" assume <code>--set-upstream</code> on default push when no
+upstream tracking exists for the current branch; this option
+takes effect with push.default options <em>simple</em>, <em>upstream</em>,
+and <em>current</em>. It is useful if by default you want new branches
+to be pushed to the default remote (like the behavior of
+<em>push.default=current</em>) and you also want the upstream tracking
+to be set. Workflows most likely to benefit from this option are
+<em>simple</em> central workflows where all branches are expected to
+have the same name on the remote.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushdefault"> <a class="anchor" href="#Documentation/git-config.txt-pushdefault"></a>push.default </dt>
+<dd>
+<p>Defines the action <code>git push</code> should take if no refspec is
+given (whether from the command-line, config, or elsewhere).
+Different values are well-suited for
+specific workflows; for instance, in a purely central workflow
+(i.e. the fetch source is equal to the push destination),
+<code>upstream</code> is probably what you want.  Possible values are:</p>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>nothing</code> - do not push anything (error out) unless a refspec is
+given. This is primarily meant for people who want to
+avoid mistakes by always being explicit.</p>
+</li>
+<li>
+<p><code>current</code> - push the current branch to update a branch with the same
+name on the receiving end.  Works in both central and non-central
+workflows.</p>
+</li>
+<li>
+<p><code>upstream</code> - push the current branch back to the branch whose
+changes are usually integrated into the current branch (which is
+called <code>@{upstream}</code>).  This mode only makes sense if you are
+pushing to the same repository you would normally pull from
+(i.e. central workflow).</p>
+</li>
+<li>
+<p><code>tracking</code> - This is a deprecated synonym for <code>upstream</code>.</p>
+</li>
+<li>
+<p><code>simple</code> - push the current branch with the same name on the remote.</p>
+<div class="paragraph">
+<p>If you are working on a centralized workflow (pushing to the same repository you
+pull from, which is typically <code>origin</code>), then you need to configure an upstream
+branch with the same name.</p>
+</div>
+<div class="paragraph">
+<p>This mode is the default since Git 2.0, and is the safest option suited for
+beginners.</p>
+</div>
+</li>
+<li>
+<p><code>matching</code> - push all branches having the same name on both ends.
+This makes the repository you are pushing to remember the set of
+branches that will be pushed out (e.g. if you always push <em>maint</em>
+and <em>master</em> there and no other branches, the repository you push
+to will have these two branches, and your local <em>maint</em> and
+<em>master</em> will be pushed there).</p>
+<div class="paragraph">
+<p>To use this mode effectively, you have to make sure <em>all</em> the
+branches you would push out are ready to be pushed out before
+running <em>git push</em>, as the whole point of this mode is to allow you
+to push all of the branches in one go.  If you usually finish work
+on only one branch and push out the result, while other branches are
+unfinished, this mode is not for you.  Also this mode is not
+suitable for pushing into a shared central repository, as other
+people may add new branches there, or update the tip of existing
+branches outside your control.</p>
+</div>
+<div class="paragraph">
+<p>This used to be the default, but not since Git 2.0 (<code>simple</code> is the
+new default).</p>
+</div>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushfollowTags"> <a class="anchor" href="#Documentation/git-config.txt-pushfollowTags"></a>push.followTags </dt>
+<dd>
+<p>If set to true, enable <code>--follow-tags</code> option by default.  You
+may override this configuration at time of push by specifying
+<code>--no-follow-tags</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushgpgSign"> <a class="anchor" href="#Documentation/git-config.txt-pushgpgSign"></a>push.gpgSign </dt>
+<dd>
+<p>May be set to a boolean value, or the string <em>if-asked</em>. A true
+value causes all pushes to be GPG signed, as if <code>--signed</code> is
+passed to <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>. The string <em>if-asked</em> causes
+pushes to be signed if the server supports it, as if
+<code>--signed=if-asked</code> is passed to <em>git push</em>. A false value may
+override a value from a lower-priority config file. An explicit
+command-line flag always overrides this config option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushpushOption"> <a class="anchor" href="#Documentation/git-config.txt-pushpushOption"></a>push.pushOption </dt>
+<dd>
+<p>When no <code>--push-option=&lt;option&gt;</code> argument is given from the
+command line, <code>git push</code> behaves as if each &lt;value&gt; of
+this variable is given as <code>--push-option=&lt;value&gt;</code>.</p>
+<div class="paragraph">
+<p>This is a multi-valued variable, and an empty value can be used in a
+higher priority configuration file (e.g. <code>.git/config</code> in a
+repository) to clear the values inherited from a lower priority
+configuration files (e.g. <code>$HOME/.gitconfig</code>).</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>Example:
+
+/etc/gitconfig
+  push.pushoption = a
+  push.pushoption = b
+
+~/.gitconfig
+  push.pushoption = c
+
+repo/.git/config
+  push.pushoption =
+  push.pushoption = b
+
+This will result in only b (a and c are cleared).</pre>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushrecurseSubmodules"> <a class="anchor" href="#Documentation/git-config.txt-pushrecurseSubmodules"></a>push.recurseSubmodules </dt>
+<dd>
+<p>May be "check", "on-demand", "only", or "no", with the same behavior
+as that of "push --recurse-submodules".
+If not set, <em>no</em> is used by default, unless <em>submodule.recurse</em> is
+set (in which case a <em>true</em> value means <em>on-demand</em>).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushuseForceIfIncludes"> <a class="anchor" href="#Documentation/git-config.txt-pushuseForceIfIncludes"></a>push.useForceIfIncludes </dt>
+<dd>
+<p>If set to "true", it is equivalent to specifying
+<code>--force-if-includes</code> as an option to <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>
+in the command line. Adding <code>--no-force-if-includes</code> at the
+time of push overrides this configuration setting.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushnegotiate"> <a class="anchor" href="#Documentation/git-config.txt-pushnegotiate"></a>push.negotiate </dt>
+<dd>
+<p>If set to "true", attempt to reduce the size of the packfile
+sent by rounds of negotiation in which the client and the
+server attempt to find commits in common. If "false", Git will
+rely solely on the server&#8217;s ref advertisement to find commits
+in common.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-pushuseBitmaps"> <a class="anchor" href="#Documentation/git-config.txt-pushuseBitmaps"></a>push.useBitmaps </dt>
+<dd>
+<p>If set to "false", disable use of bitmaps for "git push" even if
+<code>pack.useBitmaps</code> is "true", without preventing other git operations
+from using bitmaps. Default is true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebasebackend"> <a class="anchor" href="#Documentation/git-config.txt-rebasebackend"></a>rebase.backend </dt>
+<dd>
+<p>Default backend to use for rebasing.  Possible choices are
+<em>apply</em> or <em>merge</em>.  In the future, if the merge backend gains
+all remaining capabilities of the apply backend, this setting
+may become unused.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebasestat"> <a class="anchor" href="#Documentation/git-config.txt-rebasestat"></a>rebase.stat </dt>
+<dd>
+<p>Whether to show a diffstat of what changed upstream since the last
+rebase. False by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebaseautoSquash"> <a class="anchor" href="#Documentation/git-config.txt-rebaseautoSquash"></a>rebase.autoSquash </dt>
+<dd>
+<p>If set to true, enable the <code>--autosquash</code> option of
+<a href='{{< relurl "docs/git-rebase" >}}'>git-rebase[1]</a> by default for interactive mode.
+This can be overridden with the <code>--no-autosquash</code> option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebaseautoStash"> <a class="anchor" href="#Documentation/git-config.txt-rebaseautoStash"></a>rebase.autoStash </dt>
+<dd>
+<p>When set to true, automatically create a temporary stash entry
+before the operation begins, and apply it after the operation
+ends.  This means that you can run rebase on a dirty worktree.
+However, use with care: the final stash application after a
+successful rebase might result in non-trivial conflicts.
+This option can be overridden by the <code>--no-autostash</code> and
+<code>--autostash</code> options of <a href='{{< relurl "docs/git-rebase" >}}'>git-rebase[1]</a>.
+Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebaseupdateRefs"> <a class="anchor" href="#Documentation/git-config.txt-rebaseupdateRefs"></a>rebase.updateRefs </dt>
+<dd>
+<p>If set to true enable <code>--update-refs</code> option by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebasemissingCommitsCheck"> <a class="anchor" href="#Documentation/git-config.txt-rebasemissingCommitsCheck"></a>rebase.missingCommitsCheck </dt>
+<dd>
+<p>If set to "warn", git rebase -i will print a warning if some
+commits are removed (e.g. a line was deleted), however the
+rebase will still proceed. If set to "error", it will print
+the previous warning and stop the rebase, <em>git rebase
+--edit-todo</em> can then be used to correct the error. If set to
+"ignore", no checking is done.
+To drop a commit without warning or error, use the <code>drop</code>
+command in the todo list.
+Defaults to "ignore".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebaseinstructionFormat"> <a class="anchor" href="#Documentation/git-config.txt-rebaseinstructionFormat"></a>rebase.instructionFormat </dt>
+<dd>
+<p>A format string, as specified in <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a>, to be used for the
+todo list during an interactive rebase.  The format will
+automatically have the commit hash prepended to the format.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebaseabbreviateCommands"> <a class="anchor" href="#Documentation/git-config.txt-rebaseabbreviateCommands"></a>rebase.abbreviateCommands </dt>
+<dd>
+<p>If set to true, <code>git rebase</code> will use abbreviated command names in the
+todo list resulting in something like this:</p>
+<div class="listingblock">
+<div class="content">
+<pre>	p deadbee The oneline of the commit
+	p fa1afe1 The oneline of the next commit
+	...</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>instead of:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	pick deadbee The oneline of the commit
+	pick fa1afe1 The oneline of the next commit
+	...</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Defaults to false.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebaserescheduleFailedExec"> <a class="anchor" href="#Documentation/git-config.txt-rebaserescheduleFailedExec"></a>rebase.rescheduleFailedExec </dt>
+<dd>
+<p>Automatically reschedule <code>exec</code> commands that failed. This only makes
+sense in interactive mode (or when an <code>--exec</code> option was provided).
+This is the same as specifying the <code>--reschedule-failed-exec</code> option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebaseforkPoint"> <a class="anchor" href="#Documentation/git-config.txt-rebaseforkPoint"></a>rebase.forkPoint </dt>
+<dd>
+<p>If set to false set <code>--no-fork-point</code> option by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebaserebaseMerges"> <a class="anchor" href="#Documentation/git-config.txt-rebaserebaseMerges"></a>rebase.rebaseMerges </dt>
+<dd>
+<p>Whether and how to set the <code>--rebase-merges</code> option by default. Can
+be <code>rebase-cousins</code>, <code>no-rebase-cousins</code>, or a boolean. Setting to
+true or to <code>no-rebase-cousins</code> is equivalent to
+<code>--rebase-merges=no-rebase-cousins</code>, setting to <code>rebase-cousins</code> is
+equivalent to <code>--rebase-merges=rebase-cousins</code>, and setting to false is
+equivalent to <code>--no-rebase-merges</code>. Passing <code>--rebase-merges</code> on the
+command line, with or without an argument, overrides any
+<code>rebase.rebaseMerges</code> configuration.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rebasemaxLabelLength"> <a class="anchor" href="#Documentation/git-config.txt-rebasemaxLabelLength"></a>rebase.maxLabelLength </dt>
+<dd>
+<p>When generating label names from commit subjects, truncate the names to
+this length. By default, the names are truncated to a little less than
+<code>NAME_MAX</code> (to allow e.g. <code>.lock</code> files to be written for the
+corresponding loose refs).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receiveadvertiseAtomic"> <a class="anchor" href="#Documentation/git-config.txt-receiveadvertiseAtomic"></a>receive.advertiseAtomic </dt>
+<dd>
+<p>By default, git-receive-pack will advertise the atomic push
+capability to its clients. If you don&#8217;t want to advertise this
+capability, set this variable to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receiveadvertisePushOptions"> <a class="anchor" href="#Documentation/git-config.txt-receiveadvertisePushOptions"></a>receive.advertisePushOptions </dt>
+<dd>
+<p>When set to true, git-receive-pack will advertise the push options
+capability to its clients. False by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receiveautogc"> <a class="anchor" href="#Documentation/git-config.txt-receiveautogc"></a>receive.autogc </dt>
+<dd>
+<p>By default, git-receive-pack will run "git maintenance run --auto" after
+receiving data from git-push and updating refs.  You can stop
+it by setting this variable to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivecertNonceSeed"> <a class="anchor" href="#Documentation/git-config.txt-receivecertNonceSeed"></a>receive.certNonceSeed </dt>
+<dd>
+<p>By setting this variable to a string, <code>git receive-pack</code>
+will accept a <code>git push --signed</code> and verify it by using
+a "nonce" protected by HMAC using this string as a secret
+key.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivecertNonceSlop"> <a class="anchor" href="#Documentation/git-config.txt-receivecertNonceSlop"></a>receive.certNonceSlop </dt>
+<dd>
+<p>When a <code>git push --signed</code> sends a push certificate with a
+"nonce" that was issued by a receive-pack serving the same
+repository within this many seconds, export the "nonce"
+found in the certificate to <code>GIT_PUSH_CERT_NONCE</code> to the
+hooks (instead of what the receive-pack asked the sending
+side to include).  This may allow writing checks in
+<code>pre-receive</code> and <code>post-receive</code> a bit easier.  Instead of
+checking <code>GIT_PUSH_CERT_NONCE_SLOP</code> environment variable
+that records by how many seconds the nonce is stale to
+decide if they want to accept the certificate, they only
+can check <code>GIT_PUSH_CERT_NONCE_STATUS</code> is <code>OK</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivefsckObjects"> <a class="anchor" href="#Documentation/git-config.txt-receivefsckObjects"></a>receive.fsckObjects </dt>
+<dd>
+<p>If it is set to true, git-receive-pack will check all received
+objects. See <code>transfer.fsckObjects</code> for what&#8217;s checked.
+Defaults to false. If not set, the value of
+<code>transfer.fsckObjects</code> is used instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivefsckltmsg-idgt"> <a class="anchor" href="#Documentation/git-config.txt-receivefsckltmsg-idgt"></a>receive.fsck.&lt;msg-id&gt; </dt>
+<dd>
+<p>Acts like <code>fsck.&lt;msg-id&gt;</code>, but is used by
+<a href='{{< relurl "docs/git-receive-pack" >}}'>git-receive-pack[1]</a> instead of
+<a href='{{< relurl "docs/git-fsck" >}}'>git-fsck[1]</a>. See the <code>fsck.&lt;msg-id&gt;</code> documentation for
+details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivefsckskipList"> <a class="anchor" href="#Documentation/git-config.txt-receivefsckskipList"></a>receive.fsck.skipList </dt>
+<dd>
+<p>Acts like <code>fsck.skipList</code>, but is used by
+<a href='{{< relurl "docs/git-receive-pack" >}}'>git-receive-pack[1]</a> instead of
+<a href='{{< relurl "docs/git-fsck" >}}'>git-fsck[1]</a>. See the <code>fsck.skipList</code> documentation for
+details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivekeepAlive"> <a class="anchor" href="#Documentation/git-config.txt-receivekeepAlive"></a>receive.keepAlive </dt>
+<dd>
+<p>After receiving the pack from the client, <code>receive-pack</code> may
+produce no output (if <code>--quiet</code> was specified) while processing
+the pack, causing some networks to drop the TCP connection.
+With this option set, if <code>receive-pack</code> does not transmit
+any data in this phase for <code>receive.keepAlive</code> seconds, it will
+send a short keepalive packet.  The default is 5 seconds; set
+to 0 to disable keepalives entirely.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receiveunpackLimit"> <a class="anchor" href="#Documentation/git-config.txt-receiveunpackLimit"></a>receive.unpackLimit </dt>
+<dd>
+<p>If the number of objects received in a push is below this
+limit then the objects will be unpacked into loose object
+files. However if the number of received objects equals or
+exceeds this limit then the received pack will be stored as
+a pack, after adding any missing delta bases.  Storing the
+pack from a push can make the push operation complete faster,
+especially on slow filesystems.  If not set, the value of
+<code>transfer.unpackLimit</code> is used instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivemaxInputSize"> <a class="anchor" href="#Documentation/git-config.txt-receivemaxInputSize"></a>receive.maxInputSize </dt>
+<dd>
+<p>If the size of the incoming pack stream is larger than this
+limit, then git-receive-pack will error out, instead of
+accepting the pack file. If not set or set to 0, then the size
+is unlimited.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivedenyDeletes"> <a class="anchor" href="#Documentation/git-config.txt-receivedenyDeletes"></a>receive.denyDeletes </dt>
+<dd>
+<p>If set to true, git-receive-pack will deny a ref update that deletes
+the ref. Use this to prevent such a ref deletion via a push.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivedenyDeleteCurrent"> <a class="anchor" href="#Documentation/git-config.txt-receivedenyDeleteCurrent"></a>receive.denyDeleteCurrent </dt>
+<dd>
+<p>If set to true, git-receive-pack will deny a ref update that
+deletes the currently checked out branch of a non-bare repository.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivedenyCurrentBranch"> <a class="anchor" href="#Documentation/git-config.txt-receivedenyCurrentBranch"></a>receive.denyCurrentBranch </dt>
+<dd>
+<p>If set to true or "refuse", git-receive-pack will deny a ref update
+to the currently checked out branch of a non-bare repository.
+Such a push is potentially dangerous because it brings the HEAD
+out of sync with the index and working tree. If set to "warn",
+print a warning of such a push to stderr, but allow the push to
+proceed. If set to false or "ignore", allow such pushes with no
+message. Defaults to "refuse".</p>
+<div class="paragraph">
+<p>Another option is "updateInstead" which will update the working
+tree if pushing into the current branch.  This option is
+intended for synchronizing working directories when one side is not easily
+accessible via interactive ssh (e.g. a live web site, hence the requirement
+that the working directory be clean). This mode also comes in handy when
+developing inside a VM to test and fix code on different Operating Systems.</p>
+</div>
+<div class="paragraph">
+<p>By default, "updateInstead" will refuse the push if the working tree or
+the index have any difference from the HEAD, but the <code>push-to-checkout</code>
+hook can be used to customize this.  See <a href='{{< relurl "docs/githooks" >}}'>githooks[5]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivedenyNonFastForwards"> <a class="anchor" href="#Documentation/git-config.txt-receivedenyNonFastForwards"></a>receive.denyNonFastForwards </dt>
+<dd>
+<p>If set to true, git-receive-pack will deny a ref update which is
+not a fast-forward. Use this to prevent such an update via a push,
+even if that push is forced. This configuration variable is
+set when initializing a shared repository.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receivehideRefs"> <a class="anchor" href="#Documentation/git-config.txt-receivehideRefs"></a>receive.hideRefs </dt>
+<dd>
+<p>This variable is the same as <code>transfer.hideRefs</code>, but applies
+only to <code>receive-pack</code> (and so affects pushes, but not fetches).
+An attempt to update or delete a hidden ref by <code>git push</code> is
+rejected.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receiveprocReceiveRefs"> <a class="anchor" href="#Documentation/git-config.txt-receiveprocReceiveRefs"></a>receive.procReceiveRefs </dt>
+<dd>
+<p>This is a multi-valued variable that defines reference prefixes
+to match the commands in <code>receive-pack</code>.  Commands matching the
+prefixes will be executed by an external hook "proc-receive",
+instead of the internal <code>execute_commands</code> function.  If this
+variable is not defined, the "proc-receive" hook will never be
+used, and all commands will be executed by the internal
+<code>execute_commands</code> function.</p>
+<div class="paragraph">
+<p>For example, if this variable is set to "refs/for", pushing to reference
+such as "refs/for/master" will not create or update a reference named
+"refs/for/master", but may create or update a pull request directly by
+running the hook "proc-receive".</p>
+</div>
+<div class="paragraph">
+<p>Optional modifiers can be provided in the beginning of the value to filter
+commands for specific actions: create (a), modify (m), delete (d).
+A <code>!</code> can be included in the modifiers to negate the reference prefix entry.
+E.g.:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>git config --system --add receive.procReceiveRefs ad:refs/heads
+git config --system --add receive.procReceiveRefs !:refs/heads</pre>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receiveupdateServerInfo"> <a class="anchor" href="#Documentation/git-config.txt-receiveupdateServerInfo"></a>receive.updateServerInfo </dt>
+<dd>
+<p>If set to true, git-receive-pack will run git-update-server-info
+after receiving data from git-push and updating refs.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-receiveshallowUpdate"> <a class="anchor" href="#Documentation/git-config.txt-receiveshallowUpdate"></a>receive.shallowUpdate </dt>
+<dd>
+<p>If set to true, .git/shallow can be updated when new refs
+require new shallow roots. Otherwise those refs are rejected.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-reftableblockSize"> <a class="anchor" href="#Documentation/git-config.txt-reftableblockSize"></a>reftable.blockSize </dt>
+<dd>
+<p>The size in bytes used by the reftable backend when writing blocks.
+The block size is determined by the writer, and does not have to be a
+power of 2. The block size must be larger than the longest reference
+name or log entry used in the repository, as references cannot span
+blocks.</p>
+<div class="paragraph">
+<p>Powers of two that are friendly to the virtual memory system or
+filesystem (such as 4kB or 8kB) are recommended. Larger sizes (64kB) can
+yield better compression, with a possible increased cost incurred by
+readers during access.</p>
+</div>
+<div class="paragraph">
+<p>The largest block size is <code>16777215</code> bytes (15.99 MiB). The default value is
+<code>4096</code> bytes (4kB). A value of <code>0</code> will use the default value.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-reftablerestartInterval"> <a class="anchor" href="#Documentation/git-config.txt-reftablerestartInterval"></a>reftable.restartInterval </dt>
+<dd>
+<p>The interval at which to create restart points. The reftable backend
+determines the restart points at file creation. Every 16 may be
+more suitable for smaller block sizes (4k or 8k), every 64 for larger
+block sizes (64k).</p>
+<div class="paragraph">
+<p>More frequent restart points reduces prefix compression and increases
+space consumed by the restart table, both of which increase file size.</p>
+</div>
+<div class="paragraph">
+<p>Less frequent restart points makes prefix compression more effective,
+decreasing overall file size, with increased penalties for readers
+walking through more records after the binary search step.</p>
+</div>
+<div class="paragraph">
+<p>A maximum of <code>65535</code> restart points per block is supported.</p>
+</div>
+<div class="paragraph">
+<p>The default value is to create restart points every 16 records. A value of <code>0</code>
+will use the default value.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-reftableindexObjects"> <a class="anchor" href="#Documentation/git-config.txt-reftableindexObjects"></a>reftable.indexObjects </dt>
+<dd>
+<p>Whether the reftable backend shall write object blocks. Object blocks
+are a reverse mapping of object ID to the references pointing to them.</p>
+<div class="paragraph">
+<p>The default value is <code>true</code>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-reftablegeometricFactor"> <a class="anchor" href="#Documentation/git-config.txt-reftablegeometricFactor"></a>reftable.geometricFactor </dt>
+<dd>
+<p>Whenever the reftable backend appends a new table to the stack, it
+performs auto compaction to ensure that there is only a handful of
+tables. The backend does this by ensuring that tables form a geometric
+sequence regarding the respective sizes of each table.</p>
+<div class="paragraph">
+<p>By default, the geometric sequence uses a factor of 2, meaning that for any
+table, the next-biggest table must at least be twice as big. A maximum factor
+of 256 is supported.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remotepushDefault"> <a class="anchor" href="#Documentation/git-config.txt-remotepushDefault"></a>remote.pushDefault </dt>
+<dd>
+<p>The remote to push to by default.  Overrides
+<code>branch.&lt;name&gt;.remote</code> for all branches, and is overridden by
+<code>branch.&lt;name&gt;.pushRemote</code> for specific branches.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegturl"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegturl"></a>remote.&lt;name&gt;.url </dt>
+<dd>
+<p>The URL of a remote repository.  See <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> or
+<a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>. A configured remote can have multiple URLs;
+in this case the first is used for fetching, and all are used
+for pushing (assuming no <code>remote.&lt;name&gt;.pushurl</code> is defined).
+Setting this key to the empty string clears the list of urls,
+allowing you to override earlier config.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtpushurl"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtpushurl"></a>remote.&lt;name&gt;.pushurl </dt>
+<dd>
+<p>The push URL of a remote repository.  See <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>.
+If a <code>pushurl</code> option is present in a configured remote, it
+is used for pushing instead of <code>remote.&lt;name&gt;.url</code>. A configured
+remote can have multiple push URLs; in this case a push goes to
+all of them. Setting this key to the empty string clears the
+list of urls, allowing you to override earlier config.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtproxy"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtproxy"></a>remote.&lt;name&gt;.proxy </dt>
+<dd>
+<p>For remotes that require curl (http, https and ftp), the URL to
+the proxy to use for that remote.  Set to the empty string to
+disable proxying for that remote.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtproxyAuthMethod"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtproxyAuthMethod"></a>remote.&lt;name&gt;.proxyAuthMethod </dt>
+<dd>
+<p>For remotes that require curl (http, https and ftp), the method to use for
+authenticating against the proxy in use (probably set in
+<code>remote.&lt;name&gt;.proxy</code>). See <code>http.proxyAuthMethod</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtfetch"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtfetch"></a>remote.&lt;name&gt;.fetch </dt>
+<dd>
+<p>The default set of "refspec" for <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>. See
+<a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtpush"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtpush"></a>remote.&lt;name&gt;.push </dt>
+<dd>
+<p>The default set of "refspec" for <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>. See
+<a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtmirror"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtmirror"></a>remote.&lt;name&gt;.mirror </dt>
+<dd>
+<p>If true, pushing to this remote will automatically behave
+as if the <code>--mirror</code> option was given on the command line.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtskipDefaultUpdate"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtskipDefaultUpdate"></a>remote.&lt;name&gt;.skipDefaultUpdate </dt>
+<dd>
+<p>A deprecated synonym to <code>remote.&lt;name&gt;.skipFetchAll</code> (if
+both are set in the configuration files with different
+values, the value of the last occurrence will be used).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtskipFetchAll"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtskipFetchAll"></a>remote.&lt;name&gt;.skipFetchAll </dt>
+<dd>
+<p>If true, this remote will be skipped when updating
+using <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>, the <code>update</code> subcommand of
+<a href='{{< relurl "docs/git-remote" >}}'>git-remote[1]</a>, and ignored by the prefetch task
+of <code>git maitenance</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtreceivepack"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtreceivepack"></a>remote.&lt;name&gt;.receivepack </dt>
+<dd>
+<p>The default program to execute on the remote side when pushing.  See
+option --receive-pack of <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtuploadpack"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtuploadpack"></a>remote.&lt;name&gt;.uploadpack </dt>
+<dd>
+<p>The default program to execute on the remote side when fetching.  See
+option --upload-pack of <a href='{{< relurl "docs/git-fetch-pack" >}}'>git-fetch-pack[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegttagOpt"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegttagOpt"></a>remote.&lt;name&gt;.tagOpt </dt>
+<dd>
+<p>Setting this value to --no-tags disables automatic tag following when
+fetching from remote &lt;name&gt;. Setting it to --tags will fetch every
+tag from remote &lt;name&gt;, even if they are not reachable from remote
+branch heads. Passing these flags directly to <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> can
+override this setting. See options --tags and --no-tags of
+<a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtvcs"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtvcs"></a>remote.&lt;name&gt;.vcs </dt>
+<dd>
+<p>Setting this to a value &lt;vcs&gt; will cause Git to interact with
+the remote with the git-remote-&lt;vcs&gt; helper.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtprune"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtprune"></a>remote.&lt;name&gt;.prune </dt>
+<dd>
+<p>When set to true, fetching from this remote by default will also
+remove any remote-tracking references that no longer exist on the
+remote (as if the <code>--prune</code> option was given on the command line).
+Overrides <code>fetch.prune</code> settings, if any.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtpruneTags"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtpruneTags"></a>remote.&lt;name&gt;.pruneTags </dt>
+<dd>
+<p>When set to true, fetching from this remote by default will also
+remove any local tags that no longer exist on the remote if pruning
+is activated in general via <code>remote.&lt;name&gt;.prune</code>, <code>fetch.prune</code> or
+<code>--prune</code>. Overrides <code>fetch.pruneTags</code> settings, if any.</p>
+<div class="paragraph">
+<p>See also <code>remote.&lt;name&gt;.prune</code> and the PRUNING section of
+<a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtpromisor"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtpromisor"></a>remote.&lt;name&gt;.promisor </dt>
+<dd>
+<p>When set to true, this remote will be used to fetch promisor
+objects.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remoteltnamegtpartialclonefilter"> <a class="anchor" href="#Documentation/git-config.txt-remoteltnamegtpartialclonefilter"></a>remote.&lt;name&gt;.partialclonefilter </dt>
+<dd>
+<p>The filter that will be applied when fetching from this	promisor remote.
+Changing or clearing this value will only affect fetches for new commits.
+To fetch associated objects for commits already present in the local object
+database, use the <code>--refetch</code> option of <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-remotesltgroupgt"> <a class="anchor" href="#Documentation/git-config.txt-remotesltgroupgt"></a>remotes.&lt;group&gt; </dt>
+<dd>
+<p>The list of remotes which are fetched by "git remote update
+&lt;group&gt;".  See <a href='{{< relurl "docs/git-remote" >}}'>git-remote[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-repackuseDeltaBaseOffset"> <a class="anchor" href="#Documentation/git-config.txt-repackuseDeltaBaseOffset"></a>repack.useDeltaBaseOffset </dt>
+<dd>
+<p>By default, <a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a> creates packs that use
+delta-base offset. If you need to share your repository with
+Git older than version 1.4.4, either directly or via a dumb
+protocol such as http, then you need to set this option to
+"false" and repack. Access from old Git versions over the
+native protocol are unaffected by this option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-repackpackKeptObjects"> <a class="anchor" href="#Documentation/git-config.txt-repackpackKeptObjects"></a>repack.packKeptObjects </dt>
+<dd>
+<p>If set to true, makes <code>git repack</code> act as if
+<code>--pack-kept-objects</code> was passed. See <a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a> for
+details. Defaults to <code>false</code> normally, but <code>true</code> if a bitmap
+index is being written (either via <code>--write-bitmap-index</code> or
+<code>repack.writeBitmaps</code>).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-repackuseDeltaIslands"> <a class="anchor" href="#Documentation/git-config.txt-repackuseDeltaIslands"></a>repack.useDeltaIslands </dt>
+<dd>
+<p>If set to true, makes <code>git repack</code> act as if <code>--delta-islands</code>
+was passed. Defaults to <code>false</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-repackwriteBitmaps"> <a class="anchor" href="#Documentation/git-config.txt-repackwriteBitmaps"></a>repack.writeBitmaps </dt>
+<dd>
+<p>When true, git will write a bitmap index when packing all
+objects to disk (e.g., when <code>git repack -a</code> is run).  This
+index can speed up the "counting objects" phase of subsequent
+packs created for clones and fetches, at the cost of some disk
+space and extra time spent on the initial repack.  This has
+no effect if multiple packfiles are created.
+Defaults to true on bare repos, false otherwise.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-repackupdateServerInfo"> <a class="anchor" href="#Documentation/git-config.txt-repackupdateServerInfo"></a>repack.updateServerInfo </dt>
+<dd>
+<p>If set to false, <a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a> will not run
+<a href='{{< relurl "docs/git-update-server-info" >}}'>git-update-server-info[1]</a>. Defaults to true. Can be overridden
+when true by the <code>-n</code> option of <a href='{{< relurl "docs/git-repack" >}}'>git-repack[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-repackcruftWindow"> <a class="anchor" href="#Documentation/git-config.txt-repackcruftWindow"></a>repack.cruftWindow </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-repackcruftWindowMemory"> <a class="anchor" href="#Documentation/git-config.txt-repackcruftWindowMemory"></a>repack.cruftWindowMemory </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-repackcruftDepth"> <a class="anchor" href="#Documentation/git-config.txt-repackcruftDepth"></a>repack.cruftDepth </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-repackcruftThreads"> <a class="anchor" href="#Documentation/git-config.txt-repackcruftThreads"></a>repack.cruftThreads </dt>
+<dd>
+<p>Parameters used by <a href='{{< relurl "docs/git-pack-objects" >}}'>git-pack-objects[1]</a> when generating
+a cruft pack and the respective parameters are not given over
+the command line. See similarly named <code>pack.*</code> configuration
+variables for defaults and meaning.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rerereautoUpdate"> <a class="anchor" href="#Documentation/git-config.txt-rerereautoUpdate"></a>rerere.autoUpdate </dt>
+<dd>
+<p>When set to true, <code>git-rerere</code> updates the index with the
+resulting contents after it cleanly resolves conflicts using
+previously recorded resolutions.  Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-rerereenabled"> <a class="anchor" href="#Documentation/git-config.txt-rerereenabled"></a>rerere.enabled </dt>
+<dd>
+<p>Activate recording of resolved conflicts, so that identical
+conflict hunks can be resolved automatically, should they be
+encountered again.  By default, <a href='{{< relurl "docs/git-rerere" >}}'>git-rerere[1]</a> is
+enabled if there is an <code>rr-cache</code> directory under the
+<code>$GIT_DIR</code>, e.g. if "rerere" was previously used in the
+repository.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-revertreference"> <a class="anchor" href="#Documentation/git-config.txt-revertreference"></a>revert.reference </dt>
+<dd>
+<p>Setting this variable to true makes <code>git revert</code> behave
+as if the <code>--reference</code> option is given.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-safebareRepository"> <a class="anchor" href="#Documentation/git-config.txt-safebareRepository"></a>safe.bareRepository </dt>
+<dd>
+<p>Specifies which bare repositories Git will work with. The currently
+supported values are:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>all</code>: Git works with all bare repositories. This is the default.</p>
+</li>
+<li>
+<p><code>explicit</code>: Git only works with bare repositories specified via
+the top-level <code>--git-dir</code> command-line option, or the <code>GIT_DIR</code>
+environment variable (see <a href='{{< relurl "docs/git" >}}'>git[1]</a>).</p>
+<div class="paragraph">
+<p>If you do not use bare repositories in your workflow, then it may be
+beneficial to set <code>safe.bareRepository</code> to <code>explicit</code> in your global
+config. This will protect you from attacks that involve cloning a
+repository that contains a bare repository and running a Git command
+within that directory.</p>
+</div>
+<div class="paragraph">
+<p>This config setting is only respected in protected configuration (see
+<a href="#SCOPES">SCOPES</a>). This prevents untrusted repositories from tampering with
+this value.</p>
+</div>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-safedirectory"> <a class="anchor" href="#Documentation/git-config.txt-safedirectory"></a>safe.directory </dt>
+<dd>
+<p>These config entries specify Git-tracked directories that are
+considered safe even if they are owned by someone other than the
+current user. By default, Git will refuse to even parse a Git
+config of a repository owned by someone else, let alone run its
+hooks, and this config setting allows users to specify exceptions,
+e.g. for intentionally shared repositories (see the <code>--shared</code>
+option in <a href='{{< relurl "docs/git-init" >}}'>git-init[1]</a>).</p>
+<div class="paragraph">
+<p>This is a multi-valued setting, i.e. you can add more than one directory
+via <code>git config --add</code>. To reset the list of safe directories (e.g. to
+override any such directories specified in the system config), add a
+<code>safe.directory</code> entry with an empty value.</p>
+</div>
+<div class="paragraph">
+<p>This config setting is only respected in protected configuration (see
+<a href="#SCOPES">SCOPES</a>). This prevents untrusted repositories from tampering with this
+value.</p>
+</div>
+<div class="paragraph">
+<p>The value of this setting is interpolated, i.e. <code>~/&lt;path&gt;</code> expands to a
+path relative to the home directory and <code>%(prefix)/&lt;path&gt;</code> expands to a
+path relative to Git&#8217;s (runtime) prefix.</p>
+</div>
+<div class="paragraph">
+<p>To completely opt-out of this security check, set <code>safe.directory</code> to the
+string <code>*</code>. This will allow all repositories to be treated as if their
+directory was listed in the <code>safe.directory</code> list. If <code>safe.directory=*</code>
+is set in system config and you want to re-enable this protection, then
+initialize your list with an empty value before listing the repositories
+that you deem safe.  Giving a directory with <code>/*</code> appended to it will
+allow access to all repositories under the named directory.</p>
+</div>
+<div class="paragraph">
+<p>As explained, Git only allows you to access repositories owned by
+yourself, i.e. the user who is running Git, by default.  When Git
+is running as <em>root</em> in a non Windows platform that provides sudo,
+however, git checks the SUDO_UID environment variable that sudo creates
+and will allow access to the uid recorded as its value in addition to
+the id from <em>root</em>.
+This is to make it easy to perform a common sequence during installation
+"make &amp;&amp; sudo make install".  A git process running under <em>sudo</em> runs as
+<em>root</em> but the <em>sudo</em> command exports the environment variable to record
+which id the original user has.
+If that is not what you would prefer and want git to only trust
+repositories that are owned by root instead, then you can remove
+the <code>SUDO_UID</code> variable from root&#8217;s environment before invoking git.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailidentity"> <a class="anchor" href="#Documentation/git-config.txt-sendemailidentity"></a>sendemail.identity </dt>
+<dd>
+<p>A configuration identity. When given, causes values in the
+<em>sendemail.&lt;identity&gt;</em> subsection to take precedence over
+values in the <em>sendemail</em> section. The default identity is
+the value of <code>sendemail.identity</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsmtpEncryption"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsmtpEncryption"></a>sendemail.smtpEncryption </dt>
+<dd>
+<p>See <a href='{{< relurl "docs/git-send-email" >}}'>git-send-email[1]</a> for description.  Note that this
+setting is not subject to the <em>identity</em> mechanism.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsmtpSSLCertPath"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsmtpSSLCertPath"></a>sendemail.smtpSSLCertPath </dt>
+<dd>
+<p>Path to ca-certificates (either a directory or a single file).
+Set it to an empty string to disable certificate verification.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailltidentitygt"> <a class="anchor" href="#Documentation/git-config.txt-sendemailltidentitygt"></a>sendemail.&lt;identity&gt;.* </dt>
+<dd>
+<p>Identity-specific versions of the <em>sendemail.*</em> parameters
+found below, taking precedence over those when this
+identity is selected, through either the command-line or
+<code>sendemail.identity</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailmultiEdit"> <a class="anchor" href="#Documentation/git-config.txt-sendemailmultiEdit"></a>sendemail.multiEdit </dt>
+<dd>
+<p>If true (default), a single editor instance will be spawned to edit
+files you have to edit (patches when <code>--annotate</code> is used, and the
+summary when <code>--compose</code> is used). If false, files will be edited one
+after the other, spawning a new editor each time.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailconfirm"> <a class="anchor" href="#Documentation/git-config.txt-sendemailconfirm"></a>sendemail.confirm </dt>
+<dd>
+<p>Sets the default for whether to confirm before sending. Must be
+one of <em>always</em>, <em>never</em>, <em>cc</em>, <em>compose</em>, or <em>auto</em>. See <code>--confirm</code>
+in the <a href='{{< relurl "docs/git-send-email" >}}'>git-send-email[1]</a> documentation for the meaning of these
+values.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailaliasesFile"> <a class="anchor" href="#Documentation/git-config.txt-sendemailaliasesFile"></a>sendemail.aliasesFile </dt>
+<dd>
+<p>To avoid typing long email addresses, point this to one or more
+email aliases files.  You must also supply <code>sendemail.aliasFileType</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailaliasFileType"> <a class="anchor" href="#Documentation/git-config.txt-sendemailaliasFileType"></a>sendemail.aliasFileType </dt>
+<dd>
+<p>Format of the file(s) specified in sendemail.aliasesFile. Must be
+one of <em>mutt</em>, <em>mailrc</em>, <em>pine</em>, <em>elm</em>, <em>gnus</em>, or <em>sendmail</em>.</p>
+<div class="paragraph">
+<p>What an alias file in each format looks like can be found in
+the documentation of the email program of the same name. The
+differences and limitations from the standard formats are
+described below:</p>
+</div>
+<div class="openblock">
+<div class="content">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendmail"> <a class="anchor" href="#Documentation/git-config.txt-sendmail"></a>sendmail </dt>
+<dd>
+<div class="ulist">
+<ul>
+<li>
+<p>Quoted aliases and quoted addresses are not supported: lines that
+contain a <code>"</code> symbol are ignored.</p>
+</li>
+<li>
+<p>Redirection to a file (<code>/path/name</code>) or pipe (<code>|command</code>) is not
+supported.</p>
+</li>
+<li>
+<p>File inclusion (<code>:include: /path/name</code>) is not supported.</p>
+</li>
+<li>
+<p>Warnings are printed on the standard error output for any
+explicitly unsupported constructs, and any other lines that are not
+recognized by the parser.</p>
+</li>
+</ul>
+</div>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailannotate"> <a class="anchor" href="#Documentation/git-config.txt-sendemailannotate"></a>sendemail.annotate </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailbcc"> <a class="anchor" href="#Documentation/git-config.txt-sendemailbcc"></a>sendemail.bcc </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailcc"> <a class="anchor" href="#Documentation/git-config.txt-sendemailcc"></a>sendemail.cc </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailccCmd"> <a class="anchor" href="#Documentation/git-config.txt-sendemailccCmd"></a>sendemail.ccCmd </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailchainReplyTo"> <a class="anchor" href="#Documentation/git-config.txt-sendemailchainReplyTo"></a>sendemail.chainReplyTo </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailenvelopeSender"> <a class="anchor" href="#Documentation/git-config.txt-sendemailenvelopeSender"></a>sendemail.envelopeSender </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailfrom"> <a class="anchor" href="#Documentation/git-config.txt-sendemailfrom"></a>sendemail.from </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailheaderCmd"> <a class="anchor" href="#Documentation/git-config.txt-sendemailheaderCmd"></a>sendemail.headerCmd </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsignedOffByCc"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsignedOffByCc"></a>sendemail.signedOffByCc </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsmtpPass"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsmtpPass"></a>sendemail.smtpPass </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsuppressCc"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsuppressCc"></a>sendemail.suppressCc </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsuppressFrom"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsuppressFrom"></a>sendemail.suppressFrom </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailto"> <a class="anchor" href="#Documentation/git-config.txt-sendemailto"></a>sendemail.to </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailtoCmd"> <a class="anchor" href="#Documentation/git-config.txt-sendemailtoCmd"></a>sendemail.toCmd </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsmtpDomain"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsmtpDomain"></a>sendemail.smtpDomain </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsmtpServer"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsmtpServer"></a>sendemail.smtpServer </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsmtpServerPort"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsmtpServerPort"></a>sendemail.smtpServerPort </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsmtpServerOption"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsmtpServerOption"></a>sendemail.smtpServerOption </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsmtpUser"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsmtpUser"></a>sendemail.smtpUser </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailthread"> <a class="anchor" href="#Documentation/git-config.txt-sendemailthread"></a>sendemail.thread </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailtransferEncoding"> <a class="anchor" href="#Documentation/git-config.txt-sendemailtransferEncoding"></a>sendemail.transferEncoding </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailvalidate"> <a class="anchor" href="#Documentation/git-config.txt-sendemailvalidate"></a>sendemail.validate </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailxmailer"> <a class="anchor" href="#Documentation/git-config.txt-sendemailxmailer"></a>sendemail.xmailer </dt>
+<dd>
+<p>These configuration variables all provide a default for
+<a href='{{< relurl "docs/git-send-email" >}}'>git-send-email[1]</a> command-line options. See its
+documentation for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsignedOffCcdeprecated"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsignedOffCcdeprecated"></a>sendemail.signedOffCc (deprecated) </dt>
+<dd>
+<p>Deprecated alias for <code>sendemail.signedOffByCc</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsmtpBatchSize"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsmtpBatchSize"></a>sendemail.smtpBatchSize </dt>
+<dd>
+<p>Number of messages to be sent per connection, after that a relogin
+will happen.  If the value is 0 or undefined, send all messages in
+one connection.
+See also the <code>--batch-size</code> option of <a href='{{< relurl "docs/git-send-email" >}}'>git-send-email[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailsmtpReloginDelay"> <a class="anchor" href="#Documentation/git-config.txt-sendemailsmtpReloginDelay"></a>sendemail.smtpReloginDelay </dt>
+<dd>
+<p>Seconds to wait before reconnecting to the smtp server.
+See also the <code>--relogin-delay</code> option of <a href='{{< relurl "docs/git-send-email" >}}'>git-send-email[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sendemailforbidSendmailVariables"> <a class="anchor" href="#Documentation/git-config.txt-sendemailforbidSendmailVariables"></a>sendemail.forbidSendmailVariables </dt>
+<dd>
+<p>To avoid common misconfiguration mistakes, <a href='{{< relurl "docs/git-send-email" >}}'>git-send-email[1]</a>
+will abort with a warning if any configuration options for "sendmail"
+exist. Set this variable to bypass the check.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sequenceeditor"> <a class="anchor" href="#Documentation/git-config.txt-sequenceeditor"></a>sequence.editor </dt>
+<dd>
+<p>Text editor used by <code>git rebase -i</code> for editing the rebase instruction file.
+The value is meant to be interpreted by the shell when it is used.
+It can be overridden by the <code>GIT_SEQUENCE_EDITOR</code> environment variable.
+When not configured, the default commit message editor is used instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-showBranchdefault"> <a class="anchor" href="#Documentation/git-config.txt-showBranchdefault"></a>showBranch.default </dt>
+<dd>
+<p>The default set of branches for <a href='{{< relurl "docs/git-show-branch" >}}'>git-show-branch[1]</a>.
+See <a href='{{< relurl "docs/git-show-branch" >}}'>git-show-branch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sparseexpectFilesOutsideOfPatterns"> <a class="anchor" href="#Documentation/git-config.txt-sparseexpectFilesOutsideOfPatterns"></a>sparse.expectFilesOutsideOfPatterns </dt>
+<dd>
+<p>Typically with sparse checkouts, files not matching any
+sparsity patterns are marked with a SKIP_WORKTREE bit in the
+index and are missing from the working tree.  Accordingly, Git
+will ordinarily check whether files with the SKIP_WORKTREE bit
+are in fact present in the working tree contrary to
+expectations.  If Git finds any, it marks those paths as
+present by clearing the relevant SKIP_WORKTREE bits.  This
+option can be used to tell Git that such
+present-despite-skipped files are expected and to stop
+checking for them.</p>
+<div class="paragraph">
+<p>The default is <code>false</code>, which allows Git to automatically recover
+from the list of files in the index and working tree falling out of
+sync.</p>
+</div>
+<div class="paragraph">
+<p>Set this to <code>true</code> if you are in a setup where some external factor
+relieves Git of the responsibility for maintaining the consistency
+between the presence of working tree files and sparsity patterns.  For
+example, if you have a Git-aware virtual file system that has a robust
+mechanism for keeping the working tree and the sparsity patterns up to
+date based on access patterns.</p>
+</div>
+<div class="paragraph">
+<p>Regardless of this setting, Git does not check for
+present-despite-skipped files unless sparse checkout is enabled, so
+this config option has no effect unless <code>core.sparseCheckout</code> is
+<code>true</code>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-splitIndexmaxPercentChange"> <a class="anchor" href="#Documentation/git-config.txt-splitIndexmaxPercentChange"></a>splitIndex.maxPercentChange </dt>
+<dd>
+<p>When the split index feature is used, this specifies the
+percent of entries the split index can contain compared to the
+total number of entries in both the split index and the shared
+index before a new shared index is written.
+The value should be between 0 and 100. If the value is 0, then
+a new shared index is always written; if it is 100, a new
+shared index is never written.
+By default, the value is 20, so a new shared index is written
+if the number of entries in the split index would be greater
+than 20 percent of the total number of entries.
+See <a href='{{< relurl "docs/git-update-index" >}}'>git-update-index[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-splitIndexsharedIndexExpire"> <a class="anchor" href="#Documentation/git-config.txt-splitIndexsharedIndexExpire"></a>splitIndex.sharedIndexExpire </dt>
+<dd>
+<p>When the split index feature is used, shared index files that
+were not modified since the time this variable specifies will
+be removed when a new shared index file is created. The value
+"now" expires all entries immediately, and "never" suppresses
+expiration altogether.
+The default value is "2.weeks.ago".
+Note that a shared index file is considered modified (for the
+purpose of expiration) each time a new split-index file is
+either created based on it or read from it.
+See <a href='{{< relurl "docs/git-update-index" >}}'>git-update-index[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-sshvariant"> <a class="anchor" href="#Documentation/git-config.txt-sshvariant"></a>ssh.variant </dt>
+<dd>
+<p>By default, Git determines the command line arguments to use
+based on the basename of the configured SSH command (configured
+using the environment variable <code>GIT_SSH</code> or <code>GIT_SSH_COMMAND</code> or
+the config setting <code>core.sshCommand</code>). If the basename is
+unrecognized, Git will attempt to detect support of OpenSSH
+options by first invoking the configured SSH command with the
+<code>-G</code> (print configuration) option and will subsequently use
+OpenSSH options (if that is successful) or no options besides
+the host and remote command (if it fails).</p>
+<div class="paragraph">
+<p>The config variable <code>ssh.variant</code> can be set to override this detection.
+Valid values are <code>ssh</code> (to use OpenSSH options), <code>plink</code>, <code>putty</code>,
+<code>tortoiseplink</code>, <code>simple</code> (no options except the host and remote command).
+The default auto-detection can be explicitly requested using the value
+<code>auto</code>.  Any other value is treated as <code>ssh</code>.  This setting can also be
+overridden via the environment variable <code>GIT_SSH_VARIANT</code>.</p>
+</div>
+<div class="paragraph">
+<p>The current command-line parameters used for each variant are as
+follows:</p>
+</div>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>ssh</code> - [-p port] [-4] [-6] [-o option] [username@]host command</p>
+</li>
+<li>
+<p><code>simple</code> - [username@]host command</p>
+</li>
+<li>
+<p><code>plink</code> or <code>putty</code> - [-P port] [-4] [-6] [username@]host command</p>
+</li>
+<li>
+<p><code>tortoiseplink</code> - [-P port] [-4] [-6] -batch [username@]host command</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Except for the <code>simple</code> variant, command-line parameters are likely to
+change as git gains new features.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-stashshowIncludeUntracked"> <a class="anchor" href="#Documentation/git-config.txt-stashshowIncludeUntracked"></a>stash.showIncludeUntracked </dt>
+<dd>
+<p>If this is set to true, the <code>git stash show</code> command will show
+the untracked files of a stash entry.  Defaults to false. See
+the description of the <em>show</em> command in <a href='{{< relurl "docs/git-stash" >}}'>git-stash[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-stashshowPatch"> <a class="anchor" href="#Documentation/git-config.txt-stashshowPatch"></a>stash.showPatch </dt>
+<dd>
+<p>If this is set to true, the <code>git stash show</code> command without an
+option will show the stash entry in patch form.  Defaults to false.
+See the description of the <em>show</em> command in <a href='{{< relurl "docs/git-stash" >}}'>git-stash[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-stashshowStat"> <a class="anchor" href="#Documentation/git-config.txt-stashshowStat"></a>stash.showStat </dt>
+<dd>
+<p>If this is set to true, the <code>git stash show</code> command without an
+option will show a diffstat of the stash entry.  Defaults to true.
+See the description of the <em>show</em> command in <a href='{{< relurl "docs/git-stash" >}}'>git-stash[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusrelativePaths"> <a class="anchor" href="#Documentation/git-config.txt-statusrelativePaths"></a>status.relativePaths </dt>
+<dd>
+<p>By default, <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> shows paths relative to the
+current directory. Setting this variable to <code>false</code> shows paths
+relative to the repository root (this was the default for Git
+prior to v1.5.4).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusshort"> <a class="anchor" href="#Documentation/git-config.txt-statusshort"></a>status.short </dt>
+<dd>
+<p>Set to true to enable --short by default in <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a>.
+The option --no-short takes precedence over this variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusbranch"> <a class="anchor" href="#Documentation/git-config.txt-statusbranch"></a>status.branch </dt>
+<dd>
+<p>Set to true to enable --branch by default in <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a>.
+The option --no-branch takes precedence over this variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusaheadBehind"> <a class="anchor" href="#Documentation/git-config.txt-statusaheadBehind"></a>status.aheadBehind </dt>
+<dd>
+<p>Set to true to enable <code>--ahead-behind</code> and false to enable
+<code>--no-ahead-behind</code> by default in <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> for
+non-porcelain status formats.  Defaults to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusdisplayCommentPrefix"> <a class="anchor" href="#Documentation/git-config.txt-statusdisplayCommentPrefix"></a>status.displayCommentPrefix </dt>
+<dd>
+<p>If set to true, <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> will insert a comment
+prefix before each output line (starting with
+<code>core.commentChar</code>, i.e. <code>#</code> by default). This was the
+behavior of <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> in Git 1.8.4 and previous.
+Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusrenameLimit"> <a class="anchor" href="#Documentation/git-config.txt-statusrenameLimit"></a>status.renameLimit </dt>
+<dd>
+<p>The number of files to consider when performing rename detection
+in <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> and <a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a>. Defaults to
+the value of diff.renameLimit.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusrenames"> <a class="anchor" href="#Documentation/git-config.txt-statusrenames"></a>status.renames </dt>
+<dd>
+<p>Whether and how Git detects renames in <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> and
+<a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a> .  If set to "false", rename detection is
+disabled. If set to "true", basic rename detection is enabled.
+If set to "copies" or "copy", Git will detect copies, as well.
+Defaults to the value of diff.renames.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusshowStash"> <a class="anchor" href="#Documentation/git-config.txt-statusshowStash"></a>status.showStash </dt>
+<dd>
+<p>If set to true, <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> will display the number of
+entries currently stashed away.
+Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statusshowUntrackedFiles"> <a class="anchor" href="#Documentation/git-config.txt-statusshowUntrackedFiles"></a>status.showUntrackedFiles </dt>
+<dd>
+<p>By default, <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> and <a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a> show
+files which are not currently tracked by Git. Directories which
+contain only untracked files, are shown with the directory name
+only. Showing untracked files means that Git needs to lstat() all
+the files in the whole repository, which might be slow on some
+systems. So, this variable controls how the commands display
+the untracked files. Possible values are:</p>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>no</code> - Show no untracked files.</p>
+</li>
+<li>
+<p><code>normal</code> - Show untracked files and directories.</p>
+</li>
+<li>
+<p><code>all</code> - Show also individual files in untracked directories.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>If this variable is not specified, it defaults to <em>normal</em>.
+All usual spellings for Boolean value <code>true</code> are taken as <code>normal</code>
+and <code>false</code> as <code>no</code>.
+This variable can be overridden with the -u|--untracked-files option
+of <a href='{{< relurl "docs/git-status" >}}'>git-status[1]</a> and <a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-statussubmoduleSummary"> <a class="anchor" href="#Documentation/git-config.txt-statussubmoduleSummary"></a>status.submoduleSummary </dt>
+<dd>
+<p>Defaults to false.
+If this is set to a non-zero number or true (identical to -1 or an
+unlimited number), the submodule summary will be enabled and a
+summary of commits for modified submodules will be shown (see
+--summary-limit option of <a href='{{< relurl "docs/git-submodule" >}}'>git-submodule[1]</a>). Please note
+that the summary output command will be suppressed for all
+submodules when <code>diff.ignoreSubmodules</code> is set to <em>all</em> or only
+for those submodules where <code>submodule.&lt;name&gt;.ignore=all</code>. The only
+exception to that rule is that status and commit will show staged
+submodule changes. To
+also view the summary for ignored submodules you can either use
+the --ignore-submodules=dirty command-line option or the <em>git
+submodule summary</em> command, which shows a similar output but does
+not honor these settings.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submoduleltnamegturl"> <a class="anchor" href="#Documentation/git-config.txt-submoduleltnamegturl"></a>submodule.&lt;name&gt;.url </dt>
+<dd>
+<p>The URL for a submodule. This variable is copied from the .gitmodules
+file to the git config via <em>git submodule init</em>. The user can change
+the configured URL before obtaining the submodule via <em>git submodule
+update</em>. If neither submodule.&lt;name&gt;.active nor submodule.active are
+set, the presence of this variable is used as a fallback to indicate
+whether the submodule is of interest to git commands.
+See <a href='{{< relurl "docs/git-submodule" >}}'>git-submodule[1]</a> and <a href='{{< relurl "docs/gitmodules" >}}'>gitmodules[5]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submoduleltnamegtupdate"> <a class="anchor" href="#Documentation/git-config.txt-submoduleltnamegtupdate"></a>submodule.&lt;name&gt;.update </dt>
+<dd>
+<p>The method by which a submodule is updated by <em>git submodule update</em>,
+which is the only affected command, others such as
+<em>git checkout --recurse-submodules</em> are unaffected. It exists for
+historical reasons, when <em>git submodule</em> was the only command to
+interact with submodules; settings like <code>submodule.active</code>
+and <code>pull.rebase</code> are more specific. It is populated by
+<code>git submodule init</code> from the <a href='{{< relurl "docs/gitmodules" >}}'>gitmodules[5]</a> file.
+See description of <em>update</em> command in <a href='{{< relurl "docs/git-submodule" >}}'>git-submodule[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submoduleltnamegtbranch"> <a class="anchor" href="#Documentation/git-config.txt-submoduleltnamegtbranch"></a>submodule.&lt;name&gt;.branch </dt>
+<dd>
+<p>The remote branch name for a submodule, used by <code>git submodule
+update --remote</code>.  Set this option to override the value found in
+the <code>.gitmodules</code> file.  See <a href='{{< relurl "docs/git-submodule" >}}'>git-submodule[1]</a> and
+<a href='{{< relurl "docs/gitmodules" >}}'>gitmodules[5]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submoduleltnamegtfetchRecurseSubmodules"> <a class="anchor" href="#Documentation/git-config.txt-submoduleltnamegtfetchRecurseSubmodules"></a>submodule.&lt;name&gt;.fetchRecurseSubmodules </dt>
+<dd>
+<p>This option can be used to control recursive fetching of this
+submodule. It can be overridden by using the --[no-]recurse-submodules
+command-line option to "git fetch" and "git pull".
+This setting will override that from in the <a href='{{< relurl "docs/gitmodules" >}}'>gitmodules[5]</a>
+file.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submoduleltnamegtignore"> <a class="anchor" href="#Documentation/git-config.txt-submoduleltnamegtignore"></a>submodule.&lt;name&gt;.ignore </dt>
+<dd>
+<p>Defines under what circumstances "git status" and the diff family show
+a submodule as modified. When set to "all", it will never be considered
+modified (but it will nonetheless show up in the output of status and
+commit when it has been staged), "dirty" will ignore all changes
+to the submodule&#8217;s work tree and
+takes only differences between the HEAD of the submodule and the commit
+recorded in the superproject into account. "untracked" will additionally
+let submodules with modified tracked files in their work tree show up.
+Using "none" (the default when this option is not set) also shows
+submodules that have untracked files in their work tree as changed.
+This setting overrides any setting made in .gitmodules for this submodule,
+both settings can be overridden on the command line by using the
+"--ignore-submodules" option. The <em>git submodule</em> commands are not
+affected by this setting.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submoduleltnamegtactive"> <a class="anchor" href="#Documentation/git-config.txt-submoduleltnamegtactive"></a>submodule.&lt;name&gt;.active </dt>
+<dd>
+<p>Boolean value indicating if the submodule is of interest to git
+commands.  This config option takes precedence over the
+submodule.active config option. See <a href='{{< relurl "docs/gitsubmodules" >}}'>gitsubmodules[7]</a> for
+details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submoduleactive"> <a class="anchor" href="#Documentation/git-config.txt-submoduleactive"></a>submodule.active </dt>
+<dd>
+<p>A repeated field which contains a pathspec used to match against a
+submodule&#8217;s path to determine if the submodule is of interest to git
+commands. See <a href='{{< relurl "docs/gitsubmodules" >}}'>gitsubmodules[7]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submodulerecurse"> <a class="anchor" href="#Documentation/git-config.txt-submodulerecurse"></a>submodule.recurse </dt>
+<dd>
+<p>A boolean indicating if commands should enable the <code>--recurse-submodules</code>
+option by default. Defaults to false.</p>
+<div class="paragraph">
+<p>When set to true, it can be deactivated via the
+<code>--no-recurse-submodules</code> option. Note that some Git commands
+lacking this option may call some of the above commands affected by
+<code>submodule.recurse</code>; for instance <code>git remote update</code> will call
+<code>git fetch</code> but does not have a <code>--no-recurse-submodules</code> option.
+For these commands a workaround is to temporarily change the
+configuration value by using <code>git -c submodule.recurse=0</code>.</p>
+</div>
+<div class="paragraph">
+<p>The following list shows the commands that accept
+<code>--recurse-submodules</code> and whether they are supported by this
+setting.</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>checkout</code>, <code>fetch</code>, <code>grep</code>, <code>pull</code>, <code>push</code>, <code>read-tree</code>,
+<code>reset</code>, <code>restore</code> and <code>switch</code> are always supported.</p>
+</li>
+<li>
+<p><code>clone</code> and <code>ls-files</code> are not supported.</p>
+</li>
+<li>
+<p><code>branch</code> is supported only if <code>submodule.propagateBranches</code> is
+enabled</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submodulepropagateBranches"> <a class="anchor" href="#Documentation/git-config.txt-submodulepropagateBranches"></a>submodule.propagateBranches </dt>
+<dd>
+<p>[EXPERIMENTAL] A boolean that enables branching support when
+using <code>--recurse-submodules</code> or <code>submodule.recurse=true</code>.
+Enabling this will allow certain commands to accept
+<code>--recurse-submodules</code> and certain commands that already accept
+<code>--recurse-submodules</code> will now consider branches.
+Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submodulefetchJobs"> <a class="anchor" href="#Documentation/git-config.txt-submodulefetchJobs"></a>submodule.fetchJobs </dt>
+<dd>
+<p>Specifies how many submodules are fetched/cloned at the same time.
+A positive integer allows up to that number of submodules fetched
+in parallel. A value of 0 will give some reasonable default.
+If unset, it defaults to 1.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submodulealternateLocation"> <a class="anchor" href="#Documentation/git-config.txt-submodulealternateLocation"></a>submodule.alternateLocation </dt>
+<dd>
+<p>Specifies how the submodules obtain alternates when submodules are
+cloned. Possible values are <code>no</code>, <code>superproject</code>.
+By default <code>no</code> is assumed, which doesn&#8217;t add references. When the
+value is set to <code>superproject</code> the submodule to be cloned computes
+its alternates location relative to the superprojects alternate.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-submodulealternateErrorStrategy"> <a class="anchor" href="#Documentation/git-config.txt-submodulealternateErrorStrategy"></a>submodule.alternateErrorStrategy </dt>
+<dd>
+<p>Specifies how to treat errors with the alternates for a submodule
+as computed via <code>submodule.alternateLocation</code>. Possible values are
+<code>ignore</code>, <code>info</code>, <code>die</code>. Default is <code>die</code>. Note that if set to <code>ignore</code>
+or <code>info</code>, and if there is an error with the computed alternate, the
+clone proceeds as if no alternate was specified.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-tagforceSignAnnotated"> <a class="anchor" href="#Documentation/git-config.txt-tagforceSignAnnotated"></a>tag.forceSignAnnotated </dt>
+<dd>
+<p>A boolean to specify whether annotated tags created should be GPG signed.
+If <code>--annotate</code> is specified on the command line, it takes
+precedence over this option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-tagsort"> <a class="anchor" href="#Documentation/git-config.txt-tagsort"></a>tag.sort </dt>
+<dd>
+<p>This variable controls the sort ordering of tags when displayed by
+<a href='{{< relurl "docs/git-tag" >}}'>git-tag[1]</a>. Without the "--sort=&lt;value&gt;" option provided, the
+value of this variable will be used as the default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-taggpgSign"> <a class="anchor" href="#Documentation/git-config.txt-taggpgSign"></a>tag.gpgSign </dt>
+<dd>
+<p>A boolean to specify whether all tags should be GPG signed.
+Use of this option when running in an automated script can
+result in a large number of tags being signed. It is therefore
+convenient to use an agent to avoid typing your gpg passphrase
+several times. Note that this option doesn&#8217;t affect tag signing
+behavior enabled by "-u &lt;keyid&gt;" or "--local-user=&lt;keyid&gt;" options.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-tarumask"> <a class="anchor" href="#Documentation/git-config.txt-tarumask"></a>tar.umask </dt>
+<dd>
+<p>This variable can be used to restrict the permission bits of
+tar archive entries.  The default is 0002, which turns off the
+world write bit.  The special value "user" indicates that the
+archiving user&#8217;s umask will be used instead.  See umask(2) and
+<a href='{{< relurl "docs/git-archive" >}}'>git-archive[1]</a>.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>Trace2 config settings are only read from the system and global
+config files; repository local and worktree config files and <code>-c</code>
+command line arguments are not respected.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2normalTarget"> <a class="anchor" href="#Documentation/git-config.txt-trace2normalTarget"></a>trace2.normalTarget </dt>
+<dd>
+<p>This variable controls the normal target destination.
+It may be overridden by the <code>GIT_TRACE2</code> environment variable.
+The following table shows possible values.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2perfTarget"> <a class="anchor" href="#Documentation/git-config.txt-trace2perfTarget"></a>trace2.perfTarget </dt>
+<dd>
+<p>This variable controls the performance target destination.
+It may be overridden by the <code>GIT_TRACE2_PERF</code> environment variable.
+The following table shows possible values.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2eventTarget"> <a class="anchor" href="#Documentation/git-config.txt-trace2eventTarget"></a>trace2.eventTarget </dt>
+<dd>
+<p>This variable controls the event target destination.
+It may be overridden by the <code>GIT_TRACE2_EVENT</code> environment variable.
+The following table shows possible values.</p>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>0</code> or <code>false</code> - Disables the target.</p>
+</li>
+<li>
+<p><code>1</code> or <code>true</code> - Writes to <code>STDERR</code>.</p>
+</li>
+<li>
+<p><code>[2-9]</code> - Writes to the already opened file descriptor.</p>
+</li>
+<li>
+<p><code>&lt;absolute-pathname&gt;</code> - Writes to the file in append mode. If the target
+already exists and is a directory, the traces will be written to files (one
+per process) underneath the given directory.</p>
+</li>
+<li>
+<p><code>af_unix:[&lt;socket-type&gt;:]&lt;absolute-pathname&gt;</code> - Write to a
+Unix DomainSocket (on platforms that support them).  Socket
+type can be either <code>stream</code> or <code>dgram</code>; if omitted Git will
+try both.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2normalBrief"> <a class="anchor" href="#Documentation/git-config.txt-trace2normalBrief"></a>trace2.normalBrief </dt>
+<dd>
+<p>Boolean.  When true <code>time</code>, <code>filename</code>, and <code>line</code> fields are
+omitted from normal output.  May be overridden by the
+<code>GIT_TRACE2_BRIEF</code> environment variable.  Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2perfBrief"> <a class="anchor" href="#Documentation/git-config.txt-trace2perfBrief"></a>trace2.perfBrief </dt>
+<dd>
+<p>Boolean.  When true <code>time</code>, <code>filename</code>, and <code>line</code> fields are
+omitted from PERF output.  May be overridden by the
+<code>GIT_TRACE2_PERF_BRIEF</code> environment variable.  Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2eventBrief"> <a class="anchor" href="#Documentation/git-config.txt-trace2eventBrief"></a>trace2.eventBrief </dt>
+<dd>
+<p>Boolean.  When true <code>time</code>, <code>filename</code>, and <code>line</code> fields are
+omitted from event output.  May be overridden by the
+<code>GIT_TRACE2_EVENT_BRIEF</code> environment variable.  Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2eventNesting"> <a class="anchor" href="#Documentation/git-config.txt-trace2eventNesting"></a>trace2.eventNesting </dt>
+<dd>
+<p>Integer.  Specifies desired depth of nested regions in the
+event output.  Regions deeper than this value will be
+omitted.  May be overridden by the <code>GIT_TRACE2_EVENT_NESTING</code>
+environment variable.  Defaults to 2.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2configParams"> <a class="anchor" href="#Documentation/git-config.txt-trace2configParams"></a>trace2.configParams </dt>
+<dd>
+<p>A comma-separated list of patterns of "important" config
+settings that should be recorded in the trace2 output.
+For example, <code>core.*,remote.*.url</code> would cause the trace2
+output to contain events listing each configured remote.
+May be overridden by the <code>GIT_TRACE2_CONFIG_PARAMS</code> environment
+variable.  Unset by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2envVars"> <a class="anchor" href="#Documentation/git-config.txt-trace2envVars"></a>trace2.envVars </dt>
+<dd>
+<p>A comma-separated list of "important" environment variables that should
+be recorded in the trace2 output.  For example,
+<code>GIT_HTTP_USER_AGENT,GIT_CONFIG</code> would cause the trace2 output to
+contain events listing the overrides for HTTP user agent and the
+location of the Git configuration file (assuming any are set).  May be
+overridden by the <code>GIT_TRACE2_ENV_VARS</code> environment variable.  Unset by
+default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2destinationDebug"> <a class="anchor" href="#Documentation/git-config.txt-trace2destinationDebug"></a>trace2.destinationDebug </dt>
+<dd>
+<p>Boolean.  When true Git will print error messages when a
+trace target destination cannot be opened for writing.
+By default, these errors are suppressed and tracing is
+silently disabled.  May be overridden by the
+<code>GIT_TRACE2_DST_DEBUG</code> environment variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-trace2maxFiles"> <a class="anchor" href="#Documentation/git-config.txt-trace2maxFiles"></a>trace2.maxFiles </dt>
+<dd>
+<p>Integer.  When writing trace files to a target directory, do not
+write additional traces if doing so would exceed this many files. Instead,
+write a sentinel file that will block further tracing to this
+directory. Defaults to 0, which disables this check.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-transfercredentialsInUrl"> <a class="anchor" href="#Documentation/git-config.txt-transfercredentialsInUrl"></a>transfer.credentialsInUrl </dt>
+<dd>
+<p>A configured URL can contain plaintext credentials in the form
+<code>&lt;protocol&gt;://&lt;user&gt;:&lt;password&gt;@&lt;domain&gt;/&lt;path&gt;</code>. You may want
+to warn or forbid the use of such configuration (in favor of
+using <a href='{{< relurl "docs/git-credential" >}}'>git-credential[1]</a>). This will be used on
+<a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a>, <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>, <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>,
+and any other direct use of the configured URL.</p>
+<div class="paragraph">
+<p>Note that this is currently limited to detecting credentials in
+<code>remote.&lt;name&gt;.url</code> configuration; it won&#8217;t detect credentials in
+<code>remote.&lt;name&gt;.pushurl</code> configuration.</p>
+</div>
+<div class="paragraph">
+<p>You might want to enable this to prevent inadvertent credentials
+exposure, e.g. because:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The OS or system where you&#8217;re running git may not provide a way or
+otherwise allow you to configure the permissions of the
+configuration file where the username and/or password are stored.</p>
+</li>
+<li>
+<p>Even if it does, having such data stored "at rest" might expose you
+in other ways, e.g. a backup process might copy the data to another
+system.</p>
+</li>
+<li>
+<p>The git programs will pass the full URL to one another as arguments
+on the command-line, meaning the credentials will be exposed to other
+unprivileged users on systems that allow them to see the full
+process list of other users. On linux the "hidepid" setting
+documented in procfs(5) allows for configuring this behavior.</p>
+<div class="paragraph">
+<p>If such concerns don&#8217;t apply to you then you probably don&#8217;t need to be
+concerned about credentials exposure due to storing sensitive
+data in git&#8217;s configuration files. If you do want to use this, set
+<code>transfer.credentialsInUrl</code> to one of these values:</p>
+</div>
+</li>
+<li>
+<p><code>allow</code> (default): Git will proceed with its activity without warning.</p>
+</li>
+<li>
+<p><code>warn</code>: Git will write a warning message to <code>stderr</code> when parsing a URL
+with a plaintext credential.</p>
+</li>
+<li>
+<p><code>die</code>: Git will write a failure message to <code>stderr</code> when parsing a URL
+with a plaintext credential.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-transferfsckObjects"> <a class="anchor" href="#Documentation/git-config.txt-transferfsckObjects"></a>transfer.fsckObjects </dt>
+<dd>
+<p>When <code>fetch.fsckObjects</code> or <code>receive.fsckObjects</code> are
+not set, the value of this variable is used instead.
+Defaults to false.</p>
+<div class="paragraph">
+<p>When set, the fetch or receive will abort in the case of a malformed
+object or a link to a nonexistent object. In addition, various other
+issues are checked for, including legacy issues (see <code>fsck.&lt;msg-id&gt;</code>),
+and potential security issues like the existence of a <code>.GIT</code> directory
+or a malicious <code>.gitmodules</code> file (see the release notes for v2.2.1
+and v2.17.1 for details). Other sanity and security checks may be
+added in future releases.</p>
+</div>
+<div class="paragraph">
+<p>On the receiving side, failing fsckObjects will make those objects
+unreachable, see "QUARANTINE ENVIRONMENT" in
+<a href='{{< relurl "docs/git-receive-pack" >}}'>git-receive-pack[1]</a>. On the fetch side, malformed objects will
+instead be left unreferenced in the repository.</p>
+</div>
+<div class="paragraph">
+<p>Due to the non-quarantine nature of the <code>fetch.fsckObjects</code>
+implementation it cannot be relied upon to leave the object store
+clean like <code>receive.fsckObjects</code> can.</p>
+</div>
+<div class="paragraph">
+<p>As objects are unpacked they&#8217;re written to the object store, so there
+can be cases where malicious objects get introduced even though the
+"fetch" failed, only to have a subsequent "fetch" succeed because only
+new incoming objects are checked, not those that have already been
+written to the object store. That difference in behavior should not be
+relied upon. In the future, such objects may be quarantined for
+"fetch" as well.</p>
+</div>
+<div class="paragraph">
+<p>For now, the paranoid need to find some way to emulate the quarantine
+environment if they&#8217;d like the same protection as "push". E.g. in the
+case of an internal mirror do the mirroring in two steps, one to fetch
+the untrusted objects, and then do a second "push" (which will use the
+quarantine) to another internal repo, and have internal clients
+consume this pushed-to repository, or embargo internal fetches and
+only allow them once a full "fsck" has run (and no new fetches have
+happened in the meantime).</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-transferhideRefs"> <a class="anchor" href="#Documentation/git-config.txt-transferhideRefs"></a>transfer.hideRefs </dt>
+<dd>
+<p>String(s) <code>receive-pack</code> and <code>upload-pack</code> use to decide which
+refs to omit from their initial advertisements.  Use more than
+one definition to specify multiple prefix strings. A ref that is
+under the hierarchies listed in the value of this variable is
+excluded, and is hidden when responding to <code>git push</code> or <code>git
+fetch</code>.  See <code>receive.hideRefs</code> and <code>uploadpack.hideRefs</code> for
+program-specific versions of this config.</p>
+<div class="paragraph">
+<p>You may also include a <code>!</code> in front of the ref name to negate the entry,
+explicitly exposing it, even if an earlier entry marked it as hidden.
+If you have multiple hideRefs values, later entries override earlier ones
+(and entries in more-specific config files override less-specific ones).</p>
+</div>
+<div class="paragraph">
+<p>If a namespace is in use, the namespace prefix is stripped from each
+reference before it is matched against <code>transfer.hiderefs</code> patterns. In
+order to match refs before stripping, add a <code>^</code> in front of the ref name. If
+you combine <code>!</code> and <code>^</code>, <code>!</code> must be specified first.</p>
+</div>
+<div class="paragraph">
+<p>For example, if <code>refs/heads/master</code> is specified in <code>transfer.hideRefs</code> and
+the current namespace is <code>foo</code>, then <code>refs/namespaces/foo/refs/heads/master</code>
+is omitted from the advertisements. If <code>uploadpack.allowRefInWant</code> is set,
+<code>upload-pack</code> will treat <code>want-ref refs/heads/master</code> in a protocol v2
+<code>fetch</code> command as if <code>refs/namespaces/foo/refs/heads/master</code> did not exist.
+<code>receive-pack</code>, on the other hand, will still advertise the object id the
+ref is pointing to without mentioning its name (a so-called ".have" line).</p>
+</div>
+<div class="paragraph">
+<p>Even if you hide refs, a client may still be able to steal the target
+objects via the techniques described in the "SECURITY" section of the
+<a href='{{< relurl "docs/gitnamespaces" >}}'>gitnamespaces[7]</a> man page; it&#8217;s best to keep private data in a
+separate repository.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-transferunpackLimit"> <a class="anchor" href="#Documentation/git-config.txt-transferunpackLimit"></a>transfer.unpackLimit </dt>
+<dd>
+<p>When <code>fetch.unpackLimit</code> or <code>receive.unpackLimit</code> are
+not set, the value of this variable is used instead.
+The default value is 100.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-transferadvertiseSID"> <a class="anchor" href="#Documentation/git-config.txt-transferadvertiseSID"></a>transfer.advertiseSID </dt>
+<dd>
+<p>Boolean. When true, client and server processes will advertise their
+unique session IDs to their remote counterpart. Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-transferbundleURI"> <a class="anchor" href="#Documentation/git-config.txt-transferbundleURI"></a>transfer.bundleURI </dt>
+<dd>
+<p>When <code>true</code>, local <code>git clone</code> commands will request bundle
+information from the remote server (if advertised) and download
+bundles before continuing the clone through the Git protocol.
+Defaults to <code>false</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-transferadvertiseObjectInfo"> <a class="anchor" href="#Documentation/git-config.txt-transferadvertiseObjectInfo"></a>transfer.advertiseObjectInfo </dt>
+<dd>
+<p>When <code>true</code>, the <code>object-info</code> capability is advertised by
+servers. Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadarchiveallowUnreachable"> <a class="anchor" href="#Documentation/git-config.txt-uploadarchiveallowUnreachable"></a>uploadarchive.allowUnreachable </dt>
+<dd>
+<p>If true, allow clients to use <code>git archive --remote</code> to request
+any tree, whether reachable from the ref tips or not. See the
+discussion in the "SECURITY" section of
+<a href='{{< relurl "docs/git-upload-archive" >}}'>git-upload-archive[1]</a> for more details. Defaults to
+<code>false</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackhideRefs"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackhideRefs"></a>uploadpack.hideRefs </dt>
+<dd>
+<p>This variable is the same as <code>transfer.hideRefs</code>, but applies
+only to <code>upload-pack</code> (and so affects only fetches, not pushes).
+An attempt to fetch a hidden ref by <code>git fetch</code> will fail.  See
+also <code>uploadpack.allowTipSHA1InWant</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackallowTipSHA1InWant"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackallowTipSHA1InWant"></a>uploadpack.allowTipSHA1InWant </dt>
+<dd>
+<p>When <code>uploadpack.hideRefs</code> is in effect, allow <code>upload-pack</code>
+to accept a fetch request that asks for an object at the tip
+of a hidden ref (by default, such a request is rejected).
+See also <code>uploadpack.hideRefs</code>.  Even if this is false, a client
+may be able to steal objects via the techniques described in the
+"SECURITY" section of the <a href='{{< relurl "docs/gitnamespaces" >}}'>gitnamespaces[7]</a> man page; it&#8217;s
+best to keep private data in a separate repository.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackallowReachableSHA1InWant"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackallowReachableSHA1InWant"></a>uploadpack.allowReachableSHA1InWant </dt>
+<dd>
+<p>Allow <code>upload-pack</code> to accept a fetch request that asks for an
+object that is reachable from any ref tip. However, note that
+calculating object reachability is computationally expensive.
+Defaults to <code>false</code>.  Even if this is false, a client may be able
+to steal objects via the techniques described in the "SECURITY"
+section of the <a href='{{< relurl "docs/gitnamespaces" >}}'>gitnamespaces[7]</a> man page; it&#8217;s best to
+keep private data in a separate repository.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackallowAnySHA1InWant"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackallowAnySHA1InWant"></a>uploadpack.allowAnySHA1InWant </dt>
+<dd>
+<p>Allow <code>upload-pack</code> to accept a fetch request that asks for any
+object at all.
+Defaults to <code>false</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackkeepAlive"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackkeepAlive"></a>uploadpack.keepAlive </dt>
+<dd>
+<p>When <code>upload-pack</code> has started <code>pack-objects</code>, there may be a
+quiet period while <code>pack-objects</code> prepares the pack. Normally
+it would output progress information, but if <code>--quiet</code> was used
+for the fetch, <code>pack-objects</code> will output nothing at all until
+the pack data begins. Some clients and networks may consider
+the server to be hung and give up. Setting this option instructs
+<code>upload-pack</code> to send an empty keepalive packet every
+<code>uploadpack.keepAlive</code> seconds. Setting this option to 0
+disables keepalive packets entirely. The default is 5 seconds.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackpackObjectsHook"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackpackObjectsHook"></a>uploadpack.packObjectsHook </dt>
+<dd>
+<p>If this option is set, when <code>upload-pack</code> would run
+<code>git pack-objects</code> to create a packfile for a client, it will
+run this shell command instead.  The <code>pack-objects</code> command and
+arguments it <em>would</em> have run (including the <code>git pack-objects</code>
+at the beginning) are appended to the shell command. The stdin
+and stdout of the hook are treated as if <code>pack-objects</code> itself
+was run. I.e., <code>upload-pack</code> will feed input intended for
+<code>pack-objects</code> to the hook, and expects a completed packfile on
+stdout.</p>
+<div class="paragraph">
+<p>Note that this configuration variable is only respected when it is specified
+in protected configuration (see <a href="#SCOPES">SCOPES</a>). This is a safety measure
+against fetching from untrusted repositories.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackallowFilter"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackallowFilter"></a>uploadpack.allowFilter </dt>
+<dd>
+<p>If this option is set, <code>upload-pack</code> will support partial
+clone and partial fetch object filtering.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackfilterallow"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackfilterallow"></a>uploadpackfilter.allow </dt>
+<dd>
+<p>Provides a default value for unspecified object filters (see: the
+below configuration variable). If set to <code>true</code>, this will also
+enable all filters which get added in the future.
+Defaults to <code>true</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackfilterltfiltergtallow"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackfilterltfiltergtallow"></a>uploadpackfilter.&lt;filter&gt;.allow </dt>
+<dd>
+<p>Explicitly allow or ban the object filter corresponding to
+<code>&lt;filter&gt;</code>, where <code>&lt;filter&gt;</code> may be one of: <code>blob:none</code>,
+<code>blob:limit</code>, <code>object:type</code>, <code>tree</code>, <code>sparse:oid</code>, or <code>combine</code>.
+If using combined filters, both <code>combine</code> and all of the nested
+filter kinds must be allowed. Defaults to <code>uploadpackfilter.allow</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackfiltertreemaxDepth"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackfiltertreemaxDepth"></a>uploadpackfilter.tree.maxDepth </dt>
+<dd>
+<p>Only allow <code>--filter=tree:&lt;n&gt;</code> when <code>&lt;n&gt;</code> is no more than the value of
+<code>uploadpackfilter.tree.maxDepth</code>. If set, this also implies
+<code>uploadpackfilter.tree.allow=true</code>, unless this configuration
+variable had already been set. Has no effect if unset.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-uploadpackallowRefInWant"> <a class="anchor" href="#Documentation/git-config.txt-uploadpackallowRefInWant"></a>uploadpack.allowRefInWant </dt>
+<dd>
+<p>If this option is set, <code>upload-pack</code> will support the <code>ref-in-want</code>
+feature of the protocol version 2 <code>fetch</code> command.  This feature
+is intended for the benefit of load-balanced servers which may
+not have the same view of what OIDs their refs point to due to
+replication delay.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-urlltbasegtinsteadOf"> <a class="anchor" href="#Documentation/git-config.txt-urlltbasegtinsteadOf"></a>url.&lt;base&gt;.insteadOf </dt>
+<dd>
+<p>Any URL that starts with this value will be rewritten to
+start, instead, with &lt;base&gt;. In cases where some site serves a
+large number of repositories, and serves them with multiple
+access methods, and some users need to use different access
+methods, this feature allows people to specify any of the
+equivalent URLs and have Git automatically rewrite the URL to
+the best alternative for the particular user, even for a
+never-before-seen repository on the site.  When more than one
+insteadOf strings match a given URL, the longest match is used.</p>
+<div class="paragraph">
+<p>Note that any protocol restrictions will be applied to the rewritten
+URL. If the rewrite changes the URL to use a custom protocol or remote
+helper, you may need to adjust the <code>protocol.*.allow</code> config to permit
+the request.  In particular, protocols you expect to use for submodules
+must be set to <code>always</code> rather than the default of <code>user</code>. See the
+description of <code>protocol.allow</code> above.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-urlltbasegtpushInsteadOf"> <a class="anchor" href="#Documentation/git-config.txt-urlltbasegtpushInsteadOf"></a>url.&lt;base&gt;.pushInsteadOf </dt>
+<dd>
+<p>Any URL that starts with this value will not be pushed to;
+instead, it will be rewritten to start with &lt;base&gt;, and the
+resulting URL will be pushed to. In cases where some site serves
+a large number of repositories, and serves them with multiple
+access methods, some of which do not allow push, this feature
+allows people to specify a pull-only URL and have Git
+automatically use an appropriate URL to push, even for a
+never-before-seen repository on the site.  When more than one
+pushInsteadOf strings match a given URL, the longest match is
+used.  If a remote has an explicit pushurl, Git will ignore this
+setting for that remote.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-username"> <a class="anchor" href="#Documentation/git-config.txt-username"></a>user.name </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-useremail"> <a class="anchor" href="#Documentation/git-config.txt-useremail"></a>user.email </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-authorname"> <a class="anchor" href="#Documentation/git-config.txt-authorname"></a>author.name </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-authoremail"> <a class="anchor" href="#Documentation/git-config.txt-authoremail"></a>author.email </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-committername"> <a class="anchor" href="#Documentation/git-config.txt-committername"></a>committer.name </dt>
+<dt class="hdlist1" id="Documentation/git-config.txt-committeremail"> <a class="anchor" href="#Documentation/git-config.txt-committeremail"></a>committer.email </dt>
+<dd>
+<p>The <code>user.name</code> and <code>user.email</code> variables determine what ends
+up in the <code>author</code> and <code>committer</code> fields of commit
+objects.
+If you need the <code>author</code> or <code>committer</code> to be different, the
+<code>author.name</code>, <code>author.email</code>, <code>committer.name</code>, or
+<code>committer.email</code> variables can be set.
+All of these can be overridden by the <code>GIT_AUTHOR_NAME</code>,
+<code>GIT_AUTHOR_EMAIL</code>, <code>GIT_COMMITTER_NAME</code>,
+<code>GIT_COMMITTER_EMAIL</code>, and <code>EMAIL</code> environment variables.</p>
+<div class="paragraph">
+<p>Note that the <code>name</code> forms of these variables conventionally refer to
+some form of a personal name.  See <a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a> and the
+environment variables section of <a href='{{< relurl "docs/git" >}}'>git[1]</a> for more information on
+these settings and the <code>credential.username</code> option if you&#8217;re looking
+for authentication credentials instead.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-useruseConfigOnly"> <a class="anchor" href="#Documentation/git-config.txt-useruseConfigOnly"></a>user.useConfigOnly </dt>
+<dd>
+<p>Instruct Git to avoid trying to guess defaults for <code>user.email</code>
+and <code>user.name</code>, and instead retrieve the values only from the
+configuration. For example, if you have multiple email addresses
+and would like to use a different one for each repository, then
+with this configuration option set to <code>true</code> in the global config
+along with a name, Git will prompt you to set up an email before
+making new commits in a newly cloned repository.
+Defaults to <code>false</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-usersigningKey"> <a class="anchor" href="#Documentation/git-config.txt-usersigningKey"></a>user.signingKey </dt>
+<dd>
+<p>If <a href='{{< relurl "docs/git-tag" >}}'>git-tag[1]</a> or <a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a> is not selecting the
+key you want it to automatically when creating a signed tag or
+commit, you can override the default selection with this variable.
+This option is passed unchanged to gpg&#8217;s --local-user parameter,
+so you may specify a key using any method that gpg supports.
+If gpg.format is set to <code>ssh</code> this can contain the path to either
+your private ssh key or the public key when ssh-agent is used.
+Alternatively it can contain a public key prefixed with <code>key::</code>
+directly (e.g.: "key::ssh-rsa XXXXXX identifier"). The private key
+needs to be available via ssh-agent. If not set Git will call
+gpg.ssh.defaultKeyCommand (e.g.: "ssh-add -L") and try to use the
+first key available. For backward compatibility, a raw key which
+begins with "ssh-", such as "ssh-rsa XXXXXX identifier", is treated
+as "key::ssh-rsa XXXXXX identifier", but this form is deprecated;
+use the <code>key::</code> form instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-versionsortprereleaseSuffixdeprecated"> <a class="anchor" href="#Documentation/git-config.txt-versionsortprereleaseSuffixdeprecated"></a>versionsort.prereleaseSuffix (deprecated) </dt>
+<dd>
+<p>Deprecated alias for <code>versionsort.suffix</code>.  Ignored if
+<code>versionsort.suffix</code> is set.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-versionsortsuffix"> <a class="anchor" href="#Documentation/git-config.txt-versionsortsuffix"></a>versionsort.suffix </dt>
+<dd>
+<p>Even when version sort is used in <a href='{{< relurl "docs/git-tag" >}}'>git-tag[1]</a>, tagnames
+with the same base version but different suffixes are still sorted
+lexicographically, resulting e.g. in prerelease tags appearing
+after the main release (e.g. "1.0-rc1" after "1.0").  This
+variable can be specified to determine the sorting order of tags
+with different suffixes.</p>
+<div class="paragraph">
+<p>By specifying a single suffix in this variable, any tagname containing
+that suffix will appear before the corresponding main release.  E.g. if
+the variable is set to "-rc", then all "1.0-rcX" tags will appear before
+"1.0".  If specified multiple times, once per suffix, then the order of
+suffixes in the configuration will determine the sorting order of tagnames
+with those suffixes.  E.g. if "-pre" appears before "-rc" in the
+configuration, then all "1.0-preX" tags will be listed before any
+"1.0-rcX" tags.  The placement of the main release tag relative to tags
+with various suffixes can be determined by specifying the empty suffix
+among those other suffixes.  E.g. if the suffixes "-rc", "", "-ck", and
+"-bfs" appear in the configuration in this order, then all "v4.8-rcX" tags
+are listed first, followed by "v4.8", then "v4.8-ckX" and finally
+"v4.8-bfsX".</p>
+</div>
+<div class="paragraph">
+<p>If more than one suffix matches the same tagname, then that tagname will
+be sorted according to the suffix which starts at the earliest position in
+the tagname.  If more than one different matching suffix starts at
+that earliest position, then that tagname will be sorted according to the
+longest of those suffixes.
+The sorting order between different suffixes is undefined if they are
+in multiple config files.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-webbrowser"> <a class="anchor" href="#Documentation/git-config.txt-webbrowser"></a>web.browser </dt>
+<dd>
+<p>Specify a web browser that may be used by some commands.
+Currently only <a href='{{< relurl "docs/git-instaweb" >}}'>git-instaweb[1]</a> and <a href='{{< relurl "docs/git-help" >}}'>git-help[1]</a>
+may use it.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-config.txt-worktreeguessRemote"> <a class="anchor" href="#Documentation/git-config.txt-worktreeguessRemote"></a>worktree.guessRemote </dt>
+<dd>
+<p>If no branch is specified and neither <code>-b</code> nor <code>-B</code> nor
+<code>--detach</code> is used, then <code>git worktree add</code> defaults to
+creating a new branch from HEAD.  If <code>worktree.guessRemote</code> is
+set to true, <code>worktree add</code> tries to find a remote-tracking
+branch whose name uniquely matches the new branch name.  If
+such a branch exists, it is checked out and set as "upstream"
+for the new branch.  If no such match can be found, it falls
+back to creating a new branch from the current HEAD.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_bugs"><a class="anchor" href="#_bugs"></a>BUGS</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>When using the deprecated <code>[section.subsection]</code> syntax, changing a value
+will result in adding a multi-line key instead of a change, if the subsection
+is given with at least one uppercase character. For example when the config
+looks like</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>  [section.subsection]
+    key = value1</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>and running <code>git config section.Subsection.key value2</code> will result in</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>  [section.subsection]
+    key = value1
+    key = value2</pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_git"><a class="anchor" href="#_git"></a>GIT</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Part of the <a href='{{< relurl "docs/git" >}}'>git[1]</a> suite</p>
+</div>
+</div>
+</div>
\ No newline at end of file
diff --git a/external/docs/content/docs/git-count-objects/2.43.0.html b/external/docs/content/docs/git-count-objects/2.43.0.html
index e29c3e0a73..ffda2c2cff 100644
--- a/external/docs/content/docs/git-count-objects/2.43.0.html
+++ b/external/docs/content/docs/git-count-objects/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-count-objects/2.45.2/index.html"
 - "/docs/git-count-objects/2.46.0/index.html"
 - "/docs/git-count-objects/2.46.1/index.html"
+- "/docs/git-count-objects/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-credential-cache--daemon/2.39.0.html b/external/docs/content/docs/git-credential-cache--daemon/2.39.0.html
index 5763d1d8dc..436f90e510 100644
--- a/external/docs/content/docs/git-credential-cache--daemon/2.39.0.html
+++ b/external/docs/content/docs/git-credential-cache--daemon/2.39.0.html
@@ -39,6 +39,7 @@
 - "/docs/git-credential-cache--daemon/2.45.2/index.html"
 - "/docs/git-credential-cache--daemon/2.46.0/index.html"
 - "/docs/git-credential-cache--daemon/2.46.1/index.html"
+- "/docs/git-credential-cache--daemon/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-credential-cache/2.43.0.html b/external/docs/content/docs/git-credential-cache/2.43.0.html
index 90c9bf2d6d..4d08d40ba8 100644
--- a/external/docs/content/docs/git-credential-cache/2.43.0.html
+++ b/external/docs/content/docs/git-credential-cache/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-credential-cache/2.45.2/index.html"
 - "/docs/git-credential-cache/2.46.0/index.html"
 - "/docs/git-credential-cache/2.46.1/index.html"
+- "/docs/git-credential-cache/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-credential-store/2.43.0.html b/external/docs/content/docs/git-credential-store/2.43.0.html
index 2b46defd43..d0919beb6a 100644
--- a/external/docs/content/docs/git-credential-store/2.43.0.html
+++ b/external/docs/content/docs/git-credential-store/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-credential-store/2.45.2/index.html"
 - "/docs/git-credential-store/2.46.0/index.html"
 - "/docs/git-credential-store/2.46.1/index.html"
+- "/docs/git-credential-store/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-credential/2.46.0.html b/external/docs/content/docs/git-credential/2.46.0.html
index 3af7ba870f..8d0b12b683 100644
--- a/external/docs/content/docs/git-credential/2.46.0.html
+++ b/external/docs/content/docs/git-credential/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-credential/2.46.0/index.html"
 - "/docs/git-credential/2.46.1/index.html"
+- "/docs/git-credential/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-cvsexportcommit/2.35.0.html b/external/docs/content/docs/git-cvsexportcommit/2.35.0.html
index 96c60781ee..68d65f3a5f 100644
--- a/external/docs/content/docs/git-cvsexportcommit/2.35.0.html
+++ b/external/docs/content/docs/git-cvsexportcommit/2.35.0.html
@@ -69,6 +69,7 @@
 - "/docs/git-cvsexportcommit/2.45.2/index.html"
 - "/docs/git-cvsexportcommit/2.46.0/index.html"
 - "/docs/git-cvsexportcommit/2.46.1/index.html"
+- "/docs/git-cvsexportcommit/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-cvsimport/2.43.1.html b/external/docs/content/docs/git-cvsimport/2.43.1.html
index 3e2105a614..3c553025b0 100644
--- a/external/docs/content/docs/git-cvsimport/2.43.1.html
+++ b/external/docs/content/docs/git-cvsimport/2.43.1.html
@@ -21,6 +21,7 @@
 - "/docs/git-cvsimport/2.45.2/index.html"
 - "/docs/git-cvsimport/2.46.0/index.html"
 - "/docs/git-cvsimport/2.46.1/index.html"
+- "/docs/git-cvsimport/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-cvsserver/2.44.0.html b/external/docs/content/docs/git-cvsserver/2.44.0.html
index 92de076edf..18f225244b 100644
--- a/external/docs/content/docs/git-cvsserver/2.44.0.html
+++ b/external/docs/content/docs/git-cvsserver/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-cvsserver/2.45.2/index.html"
 - "/docs/git-cvsserver/2.46.0/index.html"
 - "/docs/git-cvsserver/2.46.1/index.html"
+- "/docs/git-cvsserver/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-daemon/2.44.0.html b/external/docs/content/docs/git-daemon/2.44.0.html
index 9298a950b5..181a30ce33 100644
--- a/external/docs/content/docs/git-daemon/2.44.0.html
+++ b/external/docs/content/docs/git-daemon/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-daemon/2.45.2/index.html"
 - "/docs/git-daemon/2.46.0/index.html"
 - "/docs/git-daemon/2.46.1/index.html"
+- "/docs/git-daemon/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-describe/2.42.0.html b/external/docs/content/docs/git-describe/2.42.0.html
index b7a72efde7..05735b90f1 100644
--- a/external/docs/content/docs/git-describe/2.42.0.html
+++ b/external/docs/content/docs/git-describe/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/git-describe/2.45.2/index.html"
 - "/docs/git-describe/2.46.0/index.html"
 - "/docs/git-describe/2.46.1/index.html"
+- "/docs/git-describe/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-diagnose/2.44.0.html b/external/docs/content/docs/git-diagnose/2.44.0.html
index 6844ff04ba..473c1df7f2 100644
--- a/external/docs/content/docs/git-diagnose/2.44.0.html
+++ b/external/docs/content/docs/git-diagnose/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-diagnose/2.45.2/index.html"
 - "/docs/git-diagnose/2.46.0/index.html"
 - "/docs/git-diagnose/2.46.1/index.html"
+- "/docs/git-diagnose/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-diff-files/2.46.0.html b/external/docs/content/docs/git-diff-files/2.46.0.html
index 0dacdb4c17..37d551338f 100644
--- a/external/docs/content/docs/git-diff-files/2.46.0.html
+++ b/external/docs/content/docs/git-diff-files/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-diff-files/2.46.0/index.html"
 - "/docs/git-diff-files/2.46.1/index.html"
+- "/docs/git-diff-files/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-diff-index/2.46.0.html b/external/docs/content/docs/git-diff-index/2.46.0.html
index b75aef2ac4..363913664f 100644
--- a/external/docs/content/docs/git-diff-index/2.46.0.html
+++ b/external/docs/content/docs/git-diff-index/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-diff-index/2.46.0/index.html"
 - "/docs/git-diff-index/2.46.1/index.html"
+- "/docs/git-diff-index/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-diff-tree/2.46.1.html b/external/docs/content/docs/git-diff-tree/2.46.1.html
index 7680c16e3f..099c71bb71 100644
--- a/external/docs/content/docs/git-diff-tree/2.46.1.html
+++ b/external/docs/content/docs/git-diff-tree/2.46.1.html
@@ -9,6 +9,7 @@
 version: 2.46.1
 aliases:
 - "/docs/git-diff-tree/2.46.1/index.html"
+- "/docs/git-diff-tree/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-diff/2.46.0.html b/external/docs/content/docs/git-diff/2.46.0.html
index bc37e033b7..5e525a8570 100644
--- a/external/docs/content/docs/git-diff/2.46.0.html
+++ b/external/docs/content/docs/git-diff/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-diff/2.46.0/index.html"
 - "/docs/git-diff/2.46.1/index.html"
+- "/docs/git-diff/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-difftool/2.45.0.html b/external/docs/content/docs/git-difftool/2.45.0.html
index 8174b7ff01..aa544f1232 100644
--- a/external/docs/content/docs/git-difftool/2.45.0.html
+++ b/external/docs/content/docs/git-difftool/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-difftool/2.45.2/index.html"
 - "/docs/git-difftool/2.46.0/index.html"
 - "/docs/git-difftool/2.46.1/index.html"
+- "/docs/git-difftool/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-fast-export/2.45.0.html b/external/docs/content/docs/git-fast-export/2.45.0.html
index 9392a2e22d..cfa892f9c6 100644
--- a/external/docs/content/docs/git-fast-export/2.45.0.html
+++ b/external/docs/content/docs/git-fast-export/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-fast-export/2.45.2/index.html"
 - "/docs/git-fast-export/2.46.0/index.html"
 - "/docs/git-fast-export/2.46.1/index.html"
+- "/docs/git-fast-export/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-fast-import/2.45.0.html b/external/docs/content/docs/git-fast-import/2.45.0.html
index f96a70a98f..0854aeccb1 100644
--- a/external/docs/content/docs/git-fast-import/2.45.0.html
+++ b/external/docs/content/docs/git-fast-import/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-fast-import/2.45.2/index.html"
 - "/docs/git-fast-import/2.46.0/index.html"
 - "/docs/git-fast-import/2.46.1/index.html"
+- "/docs/git-fast-import/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-fetch-pack/2.43.0.html b/external/docs/content/docs/git-fetch-pack/2.43.0.html
index c46043f3ca..d6cdf2b645 100644
--- a/external/docs/content/docs/git-fetch-pack/2.43.0.html
+++ b/external/docs/content/docs/git-fetch-pack/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-fetch-pack/2.45.2/index.html"
 - "/docs/git-fetch-pack/2.46.0/index.html"
 - "/docs/git-fetch-pack/2.46.1/index.html"
+- "/docs/git-fetch-pack/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-fetch.html b/external/docs/content/docs/git-fetch.html
index 310e8732f1..411555f0cc 100644
--- a/external/docs/content/docs/git-fetch.html
+++ b/external/docs/content/docs/git-fetch.html
@@ -6,8 +6,8 @@
 subsection: manual
 title: Git - git-fetch Documentation
 docname: git-fetch
-version: 2.45.0
-latest-changes: 2.45.0
+version: 2.46.2
+latest-changes: 2.46.2
 aliases:
 - "/docs/git-fetch/index.html"
 ---
@@ -72,8 +72,9 @@ <h2 id="_options"><a class="anchor" href="#_options"></a>OPTIONS</h2>
 <dl>
 <dt class="hdlist1" id="Documentation/git-fetch.txt---no-all"> <a class="anchor" href="#Documentation/git-fetch.txt---no-all"></a>--[no-]all </dt>
 <dd>
-<p>Fetch all remotes. This overrides the configuration variable
-<code>fetch.all</code>.</p>
+<p>Fetch all remotes, except for the ones that has the
+<code>remote.&lt;name&gt;.skipFetchAll</code> configuration variable set.
+This overrides the configuration variable fetch.all`.</p>
 </dd>
 <dt class="hdlist1" id="Documentation/git-fetch.txt--a"> <a class="anchor" href="#Documentation/git-fetch.txt--a"></a>-a </dt>
 <dt class="hdlist1" id="Documentation/git-fetch.txt---append"> <a class="anchor" href="#Documentation/git-fetch.txt---append"></a>--append </dt>
diff --git a/external/docs/content/docs/git-fetch/2.46.2.html b/external/docs/content/docs/git-fetch/2.46.2.html
new file mode 100644
index 0000000000..d7a30debf1
--- /dev/null
+++ b/external/docs/content/docs/git-fetch/2.46.2.html
@@ -0,0 +1,1385 @@
+---
+### DO NOT EDIT! Generated by script/update-docs.rb
+
+category: manual
+section: documentation
+subsection: manual
+title: Git - git-fetch Documentation
+docname: git-fetch
+version: 2.46.2
+aliases:
+- "/docs/git-fetch/2.46.2/index.html"
+---
+<div class="sect1">
+<h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>git-fetch - Download objects and refs from another repository</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_synopsis"><a class="anchor" href="#_synopsis"></a>SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="verseblock">
+<pre class="content"><em>git fetch</em> [&lt;options&gt;] [&lt;repository&gt; [&lt;refspec&gt;&#8230;&#8203;]]
+<em>git fetch</em> [&lt;options&gt;] &lt;group&gt;
+<em>git fetch</em> --multiple [&lt;options&gt;] [(&lt;repository&gt; | &lt;group&gt;)&#8230;&#8203;]
+<em>git fetch</em> --all [&lt;options&gt;]</pre>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description"><a class="anchor" href="#_description"></a>DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Fetch branches and/or tags (collectively, "refs") from one or more
+other repositories, along with the objects necessary to complete their
+histories.  Remote-tracking branches are updated (see the description
+of &lt;refspec&gt; below for ways to control this behavior).</p>
+</div>
+<div class="paragraph">
+<p>By default, any tag that points into the histories being fetched is
+also fetched; the effect is to fetch tags that
+point at branches that you are interested in.  This default behavior
+can be changed by using the --tags or --no-tags options or by
+configuring remote.&lt;name&gt;.tagOpt.  By using a refspec that fetches tags
+explicitly, you can fetch tags that do not point into branches you
+are interested in as well.</p>
+</div>
+<div class="paragraph">
+<p><em>git fetch</em> can fetch from either a single named repository or URL,
+or from several repositories at once if &lt;group&gt; is given and
+there is a remotes.&lt;group&gt; entry in the configuration file.
+(See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>).</p>
+</div>
+<div class="paragraph">
+<p>When no remote is specified, by default the <code>origin</code> remote will be used,
+unless there&#8217;s an upstream branch configured for the current branch.</p>
+</div>
+<div class="paragraph">
+<p>The names of refs that are fetched, together with the object names
+they point at, are written to <code>.git/FETCH_HEAD</code>.  This information
+may be used by scripts or other git commands, such as <a href='{{< relurl "docs/git-pull" >}}'>git-pull[1]</a>.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_options"><a class="anchor" href="#_options"></a>OPTIONS</h2>
+<div class="sectionbody">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---no-all"> <a class="anchor" href="#Documentation/git-fetch.txt---no-all"></a>--[no-]all </dt>
+<dd>
+<p>Fetch all remotes, except for the ones that has the
+<code>remote.&lt;name&gt;.skipFetchAll</code> configuration variable set.
+This overrides the configuration variable fetch.all`.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--a"> <a class="anchor" href="#Documentation/git-fetch.txt--a"></a>-a </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---append"> <a class="anchor" href="#Documentation/git-fetch.txt---append"></a>--append </dt>
+<dd>
+<p>Append ref names and object names of fetched refs to the
+existing contents of <code>.git/FETCH_HEAD</code>.  Without this
+option old data in <code>.git/FETCH_HEAD</code> will be overwritten.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---atomic"> <a class="anchor" href="#Documentation/git-fetch.txt---atomic"></a>--atomic </dt>
+<dd>
+<p>Use an atomic transaction to update local refs. Either all refs are
+updated, or on error, no refs are updated.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---depthltdepthgt"> <a class="anchor" href="#Documentation/git-fetch.txt---depthltdepthgt"></a>--depth=&lt;depth&gt; </dt>
+<dd>
+<p>Limit fetching to the specified number of commits from the tip of
+each remote branch history. If fetching to a <em>shallow</em> repository
+created by <code>git clone</code> with <code>--depth=&lt;depth&gt;</code> option (see
+<a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a>), deepen or shorten the history to the specified
+number of commits. Tags for the deepened commits are not fetched.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---deepenltdepthgt"> <a class="anchor" href="#Documentation/git-fetch.txt---deepenltdepthgt"></a>--deepen=&lt;depth&gt; </dt>
+<dd>
+<p>Similar to --depth, except it specifies the number of commits
+from the current shallow boundary instead of from the tip of
+each remote branch history.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---shallow-sinceltdategt"> <a class="anchor" href="#Documentation/git-fetch.txt---shallow-sinceltdategt"></a>--shallow-since=&lt;date&gt; </dt>
+<dd>
+<p>Deepen or shorten the history of a shallow repository to
+include all reachable commits after &lt;date&gt;.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---shallow-excludeltrevisiongt"> <a class="anchor" href="#Documentation/git-fetch.txt---shallow-excludeltrevisiongt"></a>--shallow-exclude=&lt;revision&gt; </dt>
+<dd>
+<p>Deepen or shorten the history of a shallow repository to
+exclude commits reachable from a specified remote branch or tag.
+This option can be specified multiple times.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---unshallow"> <a class="anchor" href="#Documentation/git-fetch.txt---unshallow"></a>--unshallow </dt>
+<dd>
+<p>If the source repository is complete, convert a shallow
+repository to a complete one, removing all the limitations
+imposed by shallow repositories.</p>
+<div class="paragraph">
+<p>If the source repository is shallow, fetch as much as possible so that
+the current repository has the same history as the source repository.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---update-shallow"> <a class="anchor" href="#Documentation/git-fetch.txt---update-shallow"></a>--update-shallow </dt>
+<dd>
+<p>By default when fetching from a shallow repository,
+<code>git fetch</code> refuses refs that require updating
+.git/shallow. This option updates .git/shallow and accepts such
+refs.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---negotiation-tipltcommitglobgt"> <a class="anchor" href="#Documentation/git-fetch.txt---negotiation-tipltcommitglobgt"></a>--negotiation-tip=&lt;commit|glob&gt; </dt>
+<dd>
+<p>By default, Git will report, to the server, commits reachable
+from all local refs to find common commits in an attempt to
+reduce the size of the to-be-received packfile. If specified,
+Git will only report commits reachable from the given tips.
+This is useful to speed up fetches when the user knows which
+local ref is likely to have commits in common with the
+upstream ref being fetched.</p>
+<div class="paragraph">
+<p>This option may be specified more than once; if so, Git will report
+commits reachable from any of the given commits.</p>
+</div>
+<div class="paragraph">
+<p>The argument to this option may be a glob on ref names, a ref, or the (possibly
+abbreviated) SHA-1 of a commit. Specifying a glob is equivalent to specifying
+this option multiple times, one for each matching ref name.</p>
+</div>
+<div class="paragraph">
+<p>See also the <code>fetch.negotiationAlgorithm</code> and <code>push.negotiate</code>
+configuration variables documented in <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>, and the
+<code>--negotiate-only</code> option below.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---negotiate-only"> <a class="anchor" href="#Documentation/git-fetch.txt---negotiate-only"></a>--negotiate-only </dt>
+<dd>
+<p>Do not fetch anything from the server, and instead print the
+ancestors of the provided <code>--negotiation-tip=*</code> arguments,
+which we have in common with the server.</p>
+<div class="paragraph">
+<p>This is incompatible with <code>--recurse-submodules=[yes|on-demand]</code>.
+Internally this is used to implement the <code>push.negotiate</code> option, see
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---dry-run"> <a class="anchor" href="#Documentation/git-fetch.txt---dry-run"></a>--dry-run </dt>
+<dd>
+<p>Show what would be done, without making any changes.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---porcelain"> <a class="anchor" href="#Documentation/git-fetch.txt---porcelain"></a>--porcelain </dt>
+<dd>
+<p>Print the output to standard output in an easy-to-parse format for
+scripts. See section OUTPUT in <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> for details.</p>
+<div class="paragraph">
+<p>This is incompatible with <code>--recurse-submodules=[yes|on-demand]</code> and takes
+precedence over the <code>fetch.output</code> config option.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---no-write-fetch-head"> <a class="anchor" href="#Documentation/git-fetch.txt---no-write-fetch-head"></a>--[no-]write-fetch-head </dt>
+<dd>
+<p>Write the list of remote refs fetched in the <code>FETCH_HEAD</code>
+file directly under <code>$GIT_DIR</code>.  This is the default.
+Passing <code>--no-write-fetch-head</code> from the command line tells
+Git not to write the file.  Under <code>--dry-run</code> option, the
+file is never written.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--f"> <a class="anchor" href="#Documentation/git-fetch.txt--f"></a>-f </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---force"> <a class="anchor" href="#Documentation/git-fetch.txt---force"></a>--force </dt>
+<dd>
+<p>When <em>git fetch</em> is used with <code>&lt;src&gt;:&lt;dst&gt;</code> refspec, it may
+refuse to update the local branch as discussed
+in the <code>&lt;refspec&gt;</code> part below.
+This option overrides that check.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--k"> <a class="anchor" href="#Documentation/git-fetch.txt--k"></a>-k </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---keep"> <a class="anchor" href="#Documentation/git-fetch.txt---keep"></a>--keep </dt>
+<dd>
+<p>Keep downloaded pack.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---multiple"> <a class="anchor" href="#Documentation/git-fetch.txt---multiple"></a>--multiple </dt>
+<dd>
+<p>Allow several &lt;repository&gt; and &lt;group&gt; arguments to be
+specified. No &lt;refspec&gt;s may be specified.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---no-auto-maintenance"> <a class="anchor" href="#Documentation/git-fetch.txt---no-auto-maintenance"></a>--[no-]auto-maintenance </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---no-auto-gc"> <a class="anchor" href="#Documentation/git-fetch.txt---no-auto-gc"></a>--[no-]auto-gc </dt>
+<dd>
+<p>Run <code>git maintenance run --auto</code> at the end to perform automatic
+repository maintenance if needed. (<code>--[no-]auto-gc</code> is a synonym.)
+This is enabled by default.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---no-write-commit-graph"> <a class="anchor" href="#Documentation/git-fetch.txt---no-write-commit-graph"></a>--[no-]write-commit-graph </dt>
+<dd>
+<p>Write a commit-graph after fetching. This overrides the config
+setting <code>fetch.writeCommitGraph</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---prefetch"> <a class="anchor" href="#Documentation/git-fetch.txt---prefetch"></a>--prefetch </dt>
+<dd>
+<p>Modify the configured refspec to place all refs into the
+<code>refs/prefetch/</code> namespace. See the <code>prefetch</code> task in
+<a href='{{< relurl "docs/git-maintenance" >}}'>git-maintenance[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--p"> <a class="anchor" href="#Documentation/git-fetch.txt--p"></a>-p </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---prune"> <a class="anchor" href="#Documentation/git-fetch.txt---prune"></a>--prune </dt>
+<dd>
+<p>Before fetching, remove any remote-tracking references that no
+longer exist on the remote.  Tags are not subject to pruning
+if they are fetched only because of the default tag
+auto-following or due to a --tags option.  However, if tags
+are fetched due to an explicit refspec (either on the command
+line or in the remote configuration, for example if the remote
+was cloned with the --mirror option), then they are also
+subject to pruning. Supplying <code>--prune-tags</code> is a shorthand for
+providing the tag refspec.</p>
+<div class="paragraph">
+<p>See the PRUNING section below for more details.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--P"> <a class="anchor" href="#Documentation/git-fetch.txt--P"></a>-P </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---prune-tags"> <a class="anchor" href="#Documentation/git-fetch.txt---prune-tags"></a>--prune-tags </dt>
+<dd>
+<p>Before fetching, remove any local tags that no longer exist on
+the remote if <code>--prune</code> is enabled. This option should be used
+more carefully, unlike <code>--prune</code> it will remove any local
+references (local tags) that have been created. This option is
+a shorthand for providing the explicit tag refspec along with
+<code>--prune</code>, see the discussion about that in its documentation.</p>
+<div class="paragraph">
+<p>See the PRUNING section below for more details.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--n"> <a class="anchor" href="#Documentation/git-fetch.txt--n"></a>-n </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---no-tags"> <a class="anchor" href="#Documentation/git-fetch.txt---no-tags"></a>--no-tags </dt>
+<dd>
+<p>By default, tags that point at objects that are downloaded
+from the remote repository are fetched and stored locally.
+This option disables this automatic tag following. The default
+behavior for a remote may be specified with the remote.&lt;name&gt;.tagOpt
+setting. See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---refetch"> <a class="anchor" href="#Documentation/git-fetch.txt---refetch"></a>--refetch </dt>
+<dd>
+<p>Instead of negotiating with the server to avoid transferring commits and
+associated objects that are already present locally, this option fetches
+all objects as a fresh clone would. Use this to reapply a partial clone
+filter from configuration or using <code>--filter=</code> when the filter
+definition has changed. Automatic post-fetch maintenance will perform
+object database pack consolidation to remove any duplicate objects.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---refmapltrefspecgt"> <a class="anchor" href="#Documentation/git-fetch.txt---refmapltrefspecgt"></a>--refmap=&lt;refspec&gt; </dt>
+<dd>
+<p>When fetching refs listed on the command line, use the
+specified refspec (can be given more than once) to map the
+refs to remote-tracking branches, instead of the values of
+<code>remote.*.fetch</code> configuration variables for the remote
+repository.  Providing an empty <code>&lt;refspec&gt;</code> to the
+<code>--refmap</code> option causes Git to ignore the configured
+refspecs and rely entirely on the refspecs supplied as
+command-line arguments. See section on "Configured Remote-tracking
+Branches" for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--t"> <a class="anchor" href="#Documentation/git-fetch.txt--t"></a>-t </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---tags"> <a class="anchor" href="#Documentation/git-fetch.txt---tags"></a>--tags </dt>
+<dd>
+<p>Fetch all tags from the remote (i.e., fetch remote tags
+<code>refs/tags/*</code> into local tags with the same name), in addition
+to whatever else would otherwise be fetched.  Using this
+option alone does not subject tags to pruning, even if --prune
+is used (though tags may be pruned anyway if they are also the
+destination of an explicit refspec; see <code>--prune</code>).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---recurse-submodulesyeson-demandno"> <a class="anchor" href="#Documentation/git-fetch.txt---recurse-submodulesyeson-demandno"></a>--recurse-submodules[=(yes|on-demand|no)] </dt>
+<dd>
+<p>This option controls if and under what conditions new commits of
+submodules should be fetched too. When recursing through submodules,
+<code>git fetch</code> always attempts to fetch "changed" submodules, that is, a
+submodule that has commits that are referenced by a newly fetched
+superproject commit but are missing in the local submodule clone. A
+changed submodule can be fetched as long as it is present locally e.g.
+in <code>$GIT_DIR/modules/</code> (see <a href='{{< relurl "docs/gitsubmodules" >}}'>gitsubmodules[7]</a>); if the upstream
+adds a new submodule, that submodule cannot be fetched until it is
+cloned e.g. by <code>git submodule update</code>.</p>
+<div class="paragraph">
+<p>When set to <em>on-demand</em>, only changed submodules are fetched. When set
+to <em>yes</em>, all populated submodules are fetched and submodules that are
+both unpopulated and changed are fetched. When set to <em>no</em>, submodules
+are never fetched.</p>
+</div>
+<div class="paragraph">
+<p>When unspecified, this uses the value of <code>fetch.recurseSubmodules</code> if it
+is set (see <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>), defaulting to <em>on-demand</em> if unset.
+When this option is used without any value, it defaults to <em>yes</em>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--j"> <a class="anchor" href="#Documentation/git-fetch.txt--j"></a>-j </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---jobsltngt"> <a class="anchor" href="#Documentation/git-fetch.txt---jobsltngt"></a>--jobs=&lt;n&gt; </dt>
+<dd>
+<p>Number of parallel children to be used for all forms of fetching.</p>
+<div class="paragraph">
+<p>If the <code>--multiple</code> option was specified, the different remotes will be fetched
+in parallel. If multiple submodules are fetched, they will be fetched in
+parallel. To control them independently, use the config settings
+<code>fetch.parallel</code> and <code>submodule.fetchJobs</code> (see <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>).</p>
+</div>
+<div class="paragraph">
+<p>Typically, parallel recursive and multi-remote fetches will be faster. By
+default fetches are performed sequentially, not in parallel.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---no-recurse-submodules"> <a class="anchor" href="#Documentation/git-fetch.txt---no-recurse-submodules"></a>--no-recurse-submodules </dt>
+<dd>
+<p>Disable recursive fetching of submodules (this has the same effect as
+using the <code>--recurse-submodules=no</code> option).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---set-upstream"> <a class="anchor" href="#Documentation/git-fetch.txt---set-upstream"></a>--set-upstream </dt>
+<dd>
+<p>If the remote is fetched successfully, add upstream
+(tracking) reference, used by argument-less
+<a href='{{< relurl "docs/git-pull" >}}'>git-pull[1]</a> and other commands. For more information,
+see <code>branch.&lt;name&gt;.merge</code> and <code>branch.&lt;name&gt;.remote</code> in
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---submodule-prefixltpathgt"> <a class="anchor" href="#Documentation/git-fetch.txt---submodule-prefixltpathgt"></a>--submodule-prefix=&lt;path&gt; </dt>
+<dd>
+<p>Prepend &lt;path&gt; to paths printed in informative messages
+such as "Fetching submodule foo".  This option is used
+internally when recursing over submodules.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---recurse-submodules-defaultyeson-demand"> <a class="anchor" href="#Documentation/git-fetch.txt---recurse-submodules-defaultyeson-demand"></a>--recurse-submodules-default=[yes|on-demand] </dt>
+<dd>
+<p>This option is used internally to temporarily provide a
+non-negative default value for the --recurse-submodules
+option.  All other methods of configuring fetch&#8217;s submodule
+recursion (such as settings in <a href='{{< relurl "docs/gitmodules" >}}'>gitmodules[5]</a> and
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>) override this option, as does
+specifying --[no-]recurse-submodules directly.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--u"> <a class="anchor" href="#Documentation/git-fetch.txt--u"></a>-u </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---update-head-ok"> <a class="anchor" href="#Documentation/git-fetch.txt---update-head-ok"></a>--update-head-ok </dt>
+<dd>
+<p>By default <em>git fetch</em> refuses to update the head which
+corresponds to the current branch.  This flag disables the
+check.  This is purely for the internal use for <em>git pull</em>
+to communicate with <em>git fetch</em>, and unless you are
+implementing your own Porcelain you are not supposed to
+use it.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---upload-packltupload-packgt"> <a class="anchor" href="#Documentation/git-fetch.txt---upload-packltupload-packgt"></a>--upload-pack &lt;upload-pack&gt; </dt>
+<dd>
+<p>When given, and the repository to fetch from is handled
+by <em>git fetch-pack</em>, <code>--exec=&lt;upload-pack&gt;</code> is passed to
+the command to specify non-default path for the command
+run on the other end.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--q"> <a class="anchor" href="#Documentation/git-fetch.txt--q"></a>-q </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---quiet"> <a class="anchor" href="#Documentation/git-fetch.txt---quiet"></a>--quiet </dt>
+<dd>
+<p>Pass --quiet to git-fetch-pack and silence any other internally
+used git commands. Progress is not reported to the standard error
+stream.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--v"> <a class="anchor" href="#Documentation/git-fetch.txt--v"></a>-v </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---verbose"> <a class="anchor" href="#Documentation/git-fetch.txt---verbose"></a>--verbose </dt>
+<dd>
+<p>Be verbose.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---progress"> <a class="anchor" href="#Documentation/git-fetch.txt---progress"></a>--progress </dt>
+<dd>
+<p>Progress status is reported on the standard error stream
+by default when it is attached to a terminal, unless -q
+is specified. This flag forces progress status even if the
+standard error stream is not directed to a terminal.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--oltoptiongt"> <a class="anchor" href="#Documentation/git-fetch.txt--oltoptiongt"></a>-o &lt;option&gt; </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---server-optionltoptiongt"> <a class="anchor" href="#Documentation/git-fetch.txt---server-optionltoptiongt"></a>--server-option=&lt;option&gt; </dt>
+<dd>
+<p>Transmit the given string to the server when communicating using
+protocol version 2.  The given string must not contain a NUL or LF
+character.  The server&#8217;s handling of server options, including
+unknown ones, is server-specific.
+When multiple <code>--server-option=&lt;option&gt;</code> are given, they are all
+sent to the other side in the order listed on the command line.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---show-forced-updates"> <a class="anchor" href="#Documentation/git-fetch.txt---show-forced-updates"></a>--show-forced-updates </dt>
+<dd>
+<p>By default, git checks if a branch is force-updated during
+fetch. This can be disabled through fetch.showForcedUpdates, but
+the --show-forced-updates option guarantees this check occurs.
+See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---no-show-forced-updates"> <a class="anchor" href="#Documentation/git-fetch.txt---no-show-forced-updates"></a>--no-show-forced-updates </dt>
+<dd>
+<p>By default, git checks if a branch is force-updated during
+fetch. Pass --no-show-forced-updates or set fetch.showForcedUpdates
+to false to skip this check for performance reasons. If used during
+<em>git-pull</em> the --ff-only option will still check for forced updates
+before attempting a fast-forward update. See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--4"> <a class="anchor" href="#Documentation/git-fetch.txt--4"></a>-4 </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---ipv4"> <a class="anchor" href="#Documentation/git-fetch.txt---ipv4"></a>--ipv4 </dt>
+<dd>
+<p>Use IPv4 addresses only, ignoring IPv6 addresses.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt--6"> <a class="anchor" href="#Documentation/git-fetch.txt--6"></a>-6 </dt>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---ipv6"> <a class="anchor" href="#Documentation/git-fetch.txt---ipv6"></a>--ipv6 </dt>
+<dd>
+<p>Use IPv6 addresses only, ignoring IPv4 addresses.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-ltrepositorygt"> <a class="anchor" href="#Documentation/git-fetch.txt-ltrepositorygt"></a>&lt;repository&gt; </dt>
+<dd>
+<p>The "remote" repository that is the source of a fetch
+or pull operation.  This parameter can be either a URL
+(see the section <a href="#URLS">GIT URLS</a> below) or the name
+of a remote (see the section <a href="#REMOTES">REMOTES</a> below).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-ltgroupgt"> <a class="anchor" href="#Documentation/git-fetch.txt-ltgroupgt"></a>&lt;group&gt; </dt>
+<dd>
+<p>A name referring to a list of repositories as the value
+of remotes.&lt;group&gt; in the configuration file.
+(See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-ltrefspecgt"> <a class="anchor" href="#Documentation/git-fetch.txt-ltrefspecgt"></a>&lt;refspec&gt; </dt>
+<dd>
+<p>Specifies which refs to fetch and which local refs to update.
+When no &lt;refspec&gt;s appear on the command line, the refs to fetch
+are read from <code>remote.&lt;repository&gt;.fetch</code> variables instead
+(see <a href="#CRTB">CONFIGURED REMOTE-TRACKING BRANCHES</a> below).</p>
+<div class="paragraph">
+<p>The format of a &lt;refspec&gt; parameter is an optional plus
+<code>+</code>, followed by the source &lt;src&gt;, followed
+by a colon <code>:</code>, followed by the destination ref &lt;dst&gt;.
+The colon can be omitted when &lt;dst&gt; is empty.  &lt;src&gt; is
+typically a ref, but it can also be a fully spelled hex object
+name.</p>
+</div>
+<div class="paragraph">
+<p>A &lt;refspec&gt; may contain a <code>*</code> in its &lt;src&gt; to indicate a simple pattern
+match. Such a refspec functions like a glob that matches any ref with the
+same prefix. A pattern &lt;refspec&gt; must have a <code>*</code> in both the &lt;src&gt; and
+&lt;dst&gt;. It will map refs to the destination by replacing the <code>*</code> with the
+contents matched from the source.</p>
+</div>
+<div class="paragraph">
+<p>If a refspec is prefixed by <code>^</code>, it will be interpreted as a negative
+refspec. Rather than specifying which refs to fetch or which local refs to
+update, such a refspec will instead specify refs to exclude. A ref will be
+considered to match if it matches at least one positive refspec, and does
+not match any negative refspec. Negative refspecs can be useful to restrict
+the scope of a pattern refspec so that it will not include specific refs.
+Negative refspecs can themselves be pattern refspecs. However, they may only
+contain a &lt;src&gt; and do not specify a &lt;dst&gt;. Fully spelled out hex object
+names are also not supported.</p>
+</div>
+<div class="paragraph">
+<p><code>tag &lt;tag&gt;</code> means the same as <code>refs/tags/&lt;tag&gt;:refs/tags/&lt;tag&gt;</code>;
+it requests fetching everything up to the given tag.</p>
+</div>
+<div class="paragraph">
+<p>The remote ref that matches &lt;src&gt;
+is fetched, and if &lt;dst&gt; is not an empty string, an attempt
+is made to update the local ref that matches it.</p>
+</div>
+<div class="paragraph">
+<p>Whether that update is allowed without <code>--force</code> depends on the ref
+namespace it&#8217;s being fetched to, the type of object being fetched, and
+whether the update is considered to be a fast-forward. Generally, the
+same rules apply for fetching as when pushing, see the <code>&lt;refspec&gt;...</code>
+section of <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a> for what those are. Exceptions to those
+rules particular to <em>git fetch</em> are noted below.</p>
+</div>
+<div class="paragraph">
+<p>Until Git version 2.20, and unlike when pushing with
+<a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>, any updates to <code>refs/tags/*</code> would be accepted
+without <code>+</code> in the refspec (or <code>--force</code>). When fetching, we promiscuously
+considered all tag updates from a remote to be forced fetches.  Since
+Git version 2.20, fetching to update <code>refs/tags/*</code> works the same way
+as when pushing. I.e. any updates will be rejected without <code>+</code> in the
+refspec (or <code>--force</code>).</p>
+</div>
+<div class="paragraph">
+<p>Unlike when pushing with <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>, any updates outside of
+<code>refs/{tags,heads}/*</code> will be accepted without <code>+</code> in the refspec (or
+<code>--force</code>), whether that&#8217;s swapping e.g. a tree object for a blob, or
+a commit for another commit that doesn&#8217;t have the previous commit as
+an ancestor etc.</p>
+</div>
+<div class="paragraph">
+<p>Unlike when pushing with <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>, there is no
+configuration which&#8217;ll amend these rules, and nothing like a
+<code>pre-fetch</code> hook analogous to the <code>pre-receive</code> hook.</p>
+</div>
+<div class="paragraph">
+<p>As with pushing with <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>, all of the rules described
+above about what&#8217;s not allowed as an update can be overridden by
+adding an optional leading <code>+</code> to a refspec (or using the <code>--force</code>
+command line option). The only exception to this is that no amount of
+forcing will make the <code>refs/heads/*</code> namespace accept a non-commit
+object.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+When the remote branch you want to fetch is known to
+be rewound and rebased regularly, it is expected that
+its new tip will not be a descendant of its previous tip
+(as stored in your remote-tracking branch the last time
+you fetched).  You would want
+to use the <code>+</code> sign to indicate non-fast-forward updates
+will be needed for such branches.  There is no way to
+determine or declare that a branch will be made available
+in a repository with this behavior; the pulling user simply
+must know this is the expected usage pattern for a branch.
+</td>
+</tr>
+</table>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt---stdin"> <a class="anchor" href="#Documentation/git-fetch.txt---stdin"></a>--stdin </dt>
+<dd>
+<p>Read refspecs, one per line, from stdin in addition to those provided
+as arguments. The "tag &lt;name&gt;" format is not supported.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_git_urls"><a class="anchor" href="#_git_urls"></a>GIT URLS<a id="URLS"></a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>In general, URLs contain information about the transport protocol, the
+address of the remote server, and the path to the repository.
+Depending on the transport protocol, some of this information may be
+absent.</p>
+</div>
+<div class="paragraph">
+<p>Git supports ssh, git, http, and https protocols (in addition, ftp
+and ftps can be used for fetching, but this is inefficient and
+deprecated; do not use them).</p>
+</div>
+<div class="paragraph">
+<p>The native transport (i.e. git:// URL) does no authentication and
+should be used with caution on unsecured networks.</p>
+</div>
+<div class="paragraph">
+<p>The following syntaxes may be used with them:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>ssh://</code>[<em>&lt;user&gt;</em><code>@</code>]<em>&lt;host&gt;</em>[<code>:</code><em>&lt;port&gt;</em>]<code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+<li>
+<p><code>git://</code><em>&lt;host&gt;</em>[:<em>&lt;port&gt;</em>]<code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+<li>
+<p><code>http</code>[<code>s</code>]<code>://</code><em>&lt;host&gt;</em>[<code>:</code><em>&lt;port&gt;</em>]<code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+<li>
+<p><code>ftp</code>[<code>s</code>]<code>://</code><em>&lt;host&gt;</em>[<code>:</code><em>&lt;port&gt;</em>]<code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>An alternative scp-like syntax may also be used with the ssh protocol:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>[<em>&lt;user&gt;</em><code>@</code>]<em>&lt;host&gt;</em><code>:/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>This syntax is only recognized if there are no slashes before the
+first colon. This helps differentiate a local path that contains a
+colon. For example the local path <code>foo:bar</code> could be specified as an
+absolute path or <code>./foo:bar</code> to avoid being misinterpreted as an ssh
+url.</p>
+</div>
+<div class="paragraph">
+<p>The ssh and git protocols additionally support <code>~</code><em>&lt;username&gt;</em> expansion:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>ssh://</code>[<em>&lt;user&gt;</em><code>@</code>]<em>&lt;host&gt;</em>[<code>:</code><em>&lt;port&gt;</em>]<code>/~</code><em>&lt;user&gt;</em><code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+<li>
+<p><code>git://</code><em>&lt;host&gt;</em>[<code>:</code><em>&lt;port&gt;</em>]<code>/~</code><em>&lt;user&gt;</em><code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+<li>
+<p>[<em>&lt;user&gt;</em><code>@</code>]<em>&lt;host&gt;</em><code>:~</code><em>&lt;user&gt;</em><code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>For local repositories, also supported by Git natively, the following
+syntaxes may be used:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>/path/to/repo.git/</code></p>
+</li>
+<li>
+<p><code><a href="file:///path/to/repo.git/" class="bare">file:///path/to/repo.git/</a></code></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>These two syntaxes are mostly equivalent, except when cloning, when
+the former implies <code>--local</code> option. See <a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a> for
+details.</p>
+</div>
+<div class="paragraph">
+<p><code>git clone</code>, <code>git fetch</code> and <code>git pull</code>, but not <code>git push</code>, will also
+accept a suitable bundle file. See <a href='{{< relurl "docs/git-bundle" >}}'>git-bundle[1]</a>.</p>
+</div>
+<div class="paragraph">
+<p>When Git doesn&#8217;t know how to handle a certain transport protocol, it
+attempts to use the <code>remote-</code><em>&lt;transport&gt;</em> remote helper, if one
+exists. To explicitly request a remote helper, the following syntax
+may be used:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><em>&lt;transport&gt;</em>::<em>&lt;address&gt;</em></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>where <em>&lt;address&gt;</em> may be a path, a server and path, or an arbitrary
+URL-like string recognized by the specific remote helper being
+invoked. See <a href='{{< relurl "docs/gitremote-helpers" >}}'>gitremote-helpers[7]</a> for details.</p>
+</div>
+<div class="paragraph">
+<p>If there are a large number of similarly-named remote repositories and
+you want to use a different format for them (such that the URLs you
+use will be rewritten into URLs that work), you can create a
+configuration section of the form:</p>
+</div>
+<div class="verseblock">
+<pre class="content">	[url "<em>&lt;actual-url-base&gt;</em>"]
+		insteadOf = <em>&lt;other-url-base&gt;</em></pre>
+</div>
+<div class="paragraph">
+<p>For example, with this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	[url "git://git.host.xz/"]
+		insteadOf = host.xz:/path/to/
+		insteadOf = work:</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
+rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</p>
+</div>
+<div class="paragraph">
+<p>If you want to rewrite URLs for push only, you can create a
+configuration section of the form:</p>
+</div>
+<div class="verseblock">
+<pre class="content">	[url "<em>&lt;actual-url-base&gt;</em>"]
+		pushInsteadOf = <em>&lt;other-url-base&gt;</em></pre>
+</div>
+<div class="paragraph">
+<p>For example, with this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	[url "ssh://example.org/"]
+		pushInsteadOf = git://example.org/</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>a URL like "git://example.org/path/to/repo.git" will be rewritten to
+"ssh://example.org/path/to/repo.git" for pushes, but pulls will still
+use the original URL.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_remotes"><a class="anchor" href="#_remotes"></a>REMOTES<a id="REMOTES"></a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The name of one of the following can be used instead
+of a URL as <code>&lt;repository&gt;</code> argument:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>a remote in the Git configuration file: <code>$GIT_DIR/config</code>,</p>
+</li>
+<li>
+<p>a file in the <code>$GIT_DIR/remotes</code> directory, or</p>
+</li>
+<li>
+<p>a file in the <code>$GIT_DIR/branches</code> directory.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>All of these also allow you to omit the refspec from the command line
+because they each contain a refspec which git will use by default.</p>
+</div>
+<div class="sect2">
+<h3 id="_named_remote_in_configuration_file"><a class="anchor" href="#_named_remote_in_configuration_file"></a>Named remote in configuration file</h3>
+<div class="paragraph">
+<p>You can choose to provide the name of a remote which you had previously
+configured using <a href='{{< relurl "docs/git-remote" >}}'>git-remote[1]</a>, <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>
+or even by a manual edit to the <code>$GIT_DIR/config</code> file.  The URL of
+this remote will be used to access the repository.  The refspec
+of this remote will be used by default when you do
+not provide a refspec on the command line.  The entry in the
+config file would appear like this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	[remote "&lt;name&gt;"]
+		url = &lt;URL&gt;
+		pushurl = &lt;pushurl&gt;
+		push = &lt;refspec&gt;
+		fetch = &lt;refspec&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The <code>&lt;pushurl&gt;</code> is used for pushes only. It is optional and defaults
+to <code>&lt;URL&gt;</code>. Pushing to a remote affects all defined pushurls or all
+defined urls if no pushurls are defined. Fetch, however, will only
+fetch from the first defined url if multiple urls are defined.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_named_file_in_git_dirremotes"><a class="anchor" href="#_named_file_in_git_dirremotes"></a>Named file in <code>$GIT_DIR/remotes</code></h3>
+<div class="paragraph">
+<p>You can choose to provide the name of a
+file in <code>$GIT_DIR/remotes</code>.  The URL
+in this file will be used to access the repository.  The refspec
+in this file will be used as default when you do not
+provide a refspec on the command line.  This file should have the
+following format:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	URL: one of the above URL formats
+	Push: &lt;refspec&gt;
+	Pull: &lt;refspec&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p><code>Push:</code> lines are used by <em>git push</em> and
+<code>Pull:</code> lines are used by <em>git pull</em> and <em>git fetch</em>.
+Multiple <code>Push:</code> and <code>Pull:</code> lines may
+be specified for additional branch mappings.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_named_file_in_git_dirbranches"><a class="anchor" href="#_named_file_in_git_dirbranches"></a>Named file in <code>$GIT_DIR/branches</code></h3>
+<div class="paragraph">
+<p>You can choose to provide the name of a
+file in <code>$GIT_DIR/branches</code>.
+The URL in this file will be used to access the repository.
+This file should have the following format:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	&lt;URL&gt;#&lt;head&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p><code>&lt;URL&gt;</code> is required; <code>#&lt;head&gt;</code> is optional.</p>
+</div>
+<div class="paragraph">
+<p>Depending on the operation, git will use one of the following
+refspecs, if you don&#8217;t provide one on the command line.
+<code>&lt;branch&gt;</code> is the name of this file in <code>$GIT_DIR/branches</code> and
+<code>&lt;head&gt;</code> defaults to <code>master</code>.</p>
+</div>
+<div class="paragraph">
+<p>git fetch uses:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	refs/heads/&lt;head&gt;:refs/heads/&lt;branch&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>git push uses:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	HEAD:refs/heads/&lt;head&gt;</pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_configured_remote_tracking_branches"><a class="anchor" href="#_configured_remote_tracking_branches"></a>CONFIGURED REMOTE-TRACKING BRANCHES<a id="CRTB"></a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>You often interact with the same remote repository by
+regularly and repeatedly fetching from it.  In order to keep track
+of the progress of such a remote repository, <code>git fetch</code> allows you
+to configure <code>remote.&lt;repository&gt;.fetch</code> configuration variables.</p>
+</div>
+<div class="paragraph">
+<p>Typically such a variable may look like this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>[remote "origin"]
+	fetch = +refs/heads/*:refs/remotes/origin/*</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>This configuration is used in two ways:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>When <code>git fetch</code> is run without specifying what branches
+and/or tags to fetch on the command line, e.g. <code>git fetch origin</code>
+or <code>git fetch</code>, <code>remote.&lt;repository&gt;.fetch</code> values are used as
+the refspecs&#8212;&#8203;they specify which refs to fetch and which local refs
+to update.  The example above will fetch
+all branches that exist in the <code>origin</code> (i.e. any ref that matches
+the left-hand side of the value, <code>refs/heads/*</code>) and update the
+corresponding remote-tracking branches in the <code>refs/remotes/origin/*</code>
+hierarchy.</p>
+</li>
+<li>
+<p>When <code>git fetch</code> is run with explicit branches and/or tags
+to fetch on the command line, e.g. <code>git fetch origin master</code>, the
+&lt;refspec&gt;s given on the command line determine what are to be
+fetched (e.g. <code>master</code> in the example,
+which is a short-hand for <code>master:</code>, which in turn means
+"fetch the <em>master</em> branch but I do not explicitly say what
+remote-tracking branch to update with it from the command line"),
+and the example command will
+fetch <em>only</em> the <em>master</em> branch.  The <code>remote.&lt;repository&gt;.fetch</code>
+values determine which
+remote-tracking branch, if any, is updated.  When used in this
+way, the <code>remote.&lt;repository&gt;.fetch</code> values do not have any
+effect in deciding <em>what</em> gets fetched (i.e. the values are not
+used as refspecs when the command-line lists refspecs); they are
+only used to decide <em>where</em> the refs that are fetched are stored
+by acting as a mapping.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The latter use of the <code>remote.&lt;repository&gt;.fetch</code> values can be
+overridden by giving the <code>--refmap=&lt;refspec&gt;</code> parameter(s) on the
+command line.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_pruning"><a class="anchor" href="#_pruning"></a>PRUNING</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Git has a default disposition of keeping data unless it&#8217;s explicitly
+thrown away; this extends to holding onto local references to branches
+on remotes that have themselves deleted those branches.</p>
+</div>
+<div class="paragraph">
+<p>If left to accumulate, these stale references might make performance
+worse on big and busy repos that have a lot of branch churn, and
+e.g. make the output of commands like <code>git branch -a --contains
+&lt;commit&gt;</code> needlessly verbose, as well as impacting anything else
+that&#8217;ll work with the complete set of known references.</p>
+</div>
+<div class="paragraph">
+<p>These remote-tracking references can be deleted as a one-off with
+either of:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre># While fetching
+$ git fetch --prune &lt;name&gt;
+
+# Only prune, don't fetch
+$ git remote prune &lt;name&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>To prune references as part of your normal workflow without needing to
+remember to run that, set <code>fetch.prune</code> globally, or
+<code>remote.&lt;name&gt;.prune</code> per-remote in the config. See
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</div>
+<div class="paragraph">
+<p>Here&#8217;s where things get tricky and more specific. The pruning feature
+doesn&#8217;t actually care about branches, instead it&#8217;ll prune local &#8592;&#8594;
+remote-references as a function of the refspec of the remote (see
+<code>&lt;refspec&gt;</code> and <a href="#CRTB">CONFIGURED REMOTE-TRACKING BRANCHES</a> above).</p>
+</div>
+<div class="paragraph">
+<p>Therefore if the refspec for the remote includes
+e.g. <code>refs/tags/*:refs/tags/*</code>, or you manually run e.g. <code>git fetch
+--prune &lt;name&gt; "refs/tags/*:refs/tags/*"</code> it won&#8217;t be stale remote
+tracking branches that are deleted, but any local tag that doesn&#8217;t
+exist on the remote.</p>
+</div>
+<div class="paragraph">
+<p>This might not be what you expect, i.e. you want to prune remote
+<code>&lt;name&gt;</code>, but also explicitly fetch tags from it, so when you fetch
+from it you delete all your local tags, most of which may not have
+come from the <code>&lt;name&gt;</code> remote in the first place.</p>
+</div>
+<div class="paragraph">
+<p>So be careful when using this with a refspec like
+<code>refs/tags/*:refs/tags/*</code>, or any other refspec which might map
+references from multiple remotes to the same local namespace.</p>
+</div>
+<div class="paragraph">
+<p>Since keeping up-to-date with both branches and tags on the remote is
+a common use-case the <code>--prune-tags</code> option can be supplied along with
+<code>--prune</code> to prune local tags that don&#8217;t exist on the remote, and
+force-update those tags that differ. Tag pruning can also be enabled
+with <code>fetch.pruneTags</code> or <code>remote.&lt;name&gt;.pruneTags</code> in the config. See
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</div>
+<div class="paragraph">
+<p>The <code>--prune-tags</code> option is equivalent to having
+<code>refs/tags/*:refs/tags/*</code> declared in the refspecs of the remote. This
+can lead to some seemingly strange interactions:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre># These both fetch tags
+$ git fetch --no-tags origin 'refs/tags/*:refs/tags/*'
+$ git fetch --no-tags --prune-tags origin</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The reason it doesn&#8217;t error out when provided without <code>--prune</code> or its
+config versions is for flexibility of the configured versions, and to
+maintain a 1=1 mapping between what the command line flags do, and
+what the configuration versions do.</p>
+</div>
+<div class="paragraph">
+<p>It&#8217;s reasonable to e.g. configure <code>fetch.pruneTags=true</code> in
+<code>~/.gitconfig</code> to have tags pruned whenever <code>git fetch --prune</code> is
+run, without making every invocation of <code>git fetch</code> without <code>--prune</code>
+an error.</p>
+</div>
+<div class="paragraph">
+<p>Pruning tags with <code>--prune-tags</code> also works when fetching a URL
+instead of a named remote. These will all prune tags not found on
+origin:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>$ git fetch origin --prune --prune-tags
+$ git fetch origin --prune 'refs/tags/*:refs/tags/*'
+$ git fetch &lt;url-of-origin&gt; --prune --prune-tags
+$ git fetch &lt;url-of-origin&gt; --prune 'refs/tags/*:refs/tags/*'</pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_output"><a class="anchor" href="#_output"></a>OUTPUT</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The output of "git fetch" depends on the transport method used; this
+section describes the output when fetching over the Git protocol
+(either locally or via ssh) and Smart HTTP protocol.</p>
+</div>
+<div class="paragraph">
+<p>The status of the fetch is output in tabular form, with each line
+representing the status of a single ref. Each line is of the form:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre> &lt;flag&gt; &lt;summary&gt; &lt;from&gt; -&gt; &lt;to&gt; [&lt;reason&gt;]</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>When using <code>--porcelain</code>, the output format is intended to be
+machine-parseable. In contrast to the human-readable output formats it
+thus prints to standard output instead of standard error. Each line is
+of the form:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>&lt;flag&gt; &lt;old-object-id&gt; &lt;new-object-id&gt; &lt;local-reference&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The status of up-to-date refs is shown only if the --verbose option is
+used.</p>
+</div>
+<div class="paragraph">
+<p>In compact output mode, specified with configuration variable
+fetch.output, if either entire <code>&lt;from&gt;</code> or <code>&lt;to&gt;</code> is found in the
+other string, it will be substituted with <code>*</code> in the other string. For
+example, <code>master -&gt; origin/master</code> becomes <code>master -&gt; origin/*</code>.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-flag"> <a class="anchor" href="#Documentation/git-fetch.txt-flag"></a>flag </dt>
+<dd>
+<p>A single character indicating the status of the ref:</p>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-space"> <a class="anchor" href="#Documentation/git-fetch.txt-space"></a>(space) </dt>
+<dd>
+<p>for a successfully fetched fast-forward;</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-codecode"> <a class="anchor" href="#Documentation/git-fetch.txt-codecode"></a><code>+</code> </dt>
+<dd>
+<p>for a successful forced update;</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-code-code"> <a class="anchor" href="#Documentation/git-fetch.txt-code-code"></a><code>-</code> </dt>
+<dd>
+<p>for a successfully pruned ref;</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-codetcode"> <a class="anchor" href="#Documentation/git-fetch.txt-codetcode"></a><code>t</code> </dt>
+<dd>
+<p>for a successful tag update;</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-codecode-1"> <a class="anchor" href="#Documentation/git-fetch.txt-codecode-1"></a><code>*</code> </dt>
+<dd>
+<p>for a successfully fetched new ref;</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-codecode-1-1"> <a class="anchor" href="#Documentation/git-fetch.txt-codecode-1-1"></a><code>!</code> </dt>
+<dd>
+<p>for a ref that was rejected or failed to update; and</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-codecode-1-1-1"> <a class="anchor" href="#Documentation/git-fetch.txt-codecode-1-1-1"></a><code>=</code> </dt>
+<dd>
+<p>for a ref that was up to date and did not need fetching.</p>
+</dd>
+</dl>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-summary"> <a class="anchor" href="#Documentation/git-fetch.txt-summary"></a>summary </dt>
+<dd>
+<p>For a successfully fetched ref, the summary shows the old and new
+values of the ref in a form suitable for using as an argument to
+<code>git log</code> (this is <code>&lt;old&gt;..&lt;new&gt;</code> in most cases, and
+<code>&lt;old&gt;...&lt;new&gt;</code> for forced non-fast-forward updates).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-from"> <a class="anchor" href="#Documentation/git-fetch.txt-from"></a>from </dt>
+<dd>
+<p>The name of the remote ref being fetched from, minus its
+<code>refs/&lt;type&gt;/</code> prefix. In the case of deletion, the name of
+the remote ref is "(none)".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-to"> <a class="anchor" href="#Documentation/git-fetch.txt-to"></a>to </dt>
+<dd>
+<p>The name of the local ref being updated, minus its
+<code>refs/&lt;type&gt;/</code> prefix.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-reason"> <a class="anchor" href="#Documentation/git-fetch.txt-reason"></a>reason </dt>
+<dd>
+<p>A human-readable explanation. In the case of successfully fetched
+refs, no explanation is needed. For a failed ref, the reason for
+failure is described.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_examples"><a class="anchor" href="#_examples"></a>EXAMPLES</h2>
+<div class="sectionbody">
+<div class="ulist">
+<ul>
+<li>
+<p>Update the remote-tracking branches:</p>
+<div class="listingblock">
+<div class="content">
+<pre>$ git fetch origin</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The above command copies all branches from the remote <code>refs/heads/</code>
+namespace and stores them to the local <code>refs/remotes/origin/</code> namespace,
+unless the <code>remote.&lt;repository&gt;.fetch</code> option is used to specify a
+non-default refspec.</p>
+</div>
+</li>
+<li>
+<p>Using refspecs explicitly:</p>
+<div class="listingblock">
+<div class="content">
+<pre>$ git fetch origin +seen:seen maint:tmp</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>This updates (or creates, as necessary) branches <code>seen</code> and <code>tmp</code> in
+the local repository by fetching from the branches (respectively)
+<code>seen</code> and <code>maint</code> from the remote repository.</p>
+</div>
+<div class="paragraph">
+<p>The <code>seen</code> branch will be updated even if it does not fast-forward,
+because it is prefixed with a plus sign; <code>tmp</code> will not be.</p>
+</div>
+</li>
+<li>
+<p>Peek at a remote&#8217;s branch, without configuring the remote in your local
+repository:</p>
+<div class="listingblock">
+<div class="content">
+<pre>$ git fetch git://git.kernel.org/pub/scm/git/git.git maint
+$ git log FETCH_HEAD</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The first command fetches the <code>maint</code> branch from the repository at
+<code>git://git.kernel.org/pub/scm/git/git.git</code> and the second command uses
+<code>FETCH_HEAD</code> to examine the branch with <a href='{{< relurl "docs/git-log" >}}'>git-log[1]</a>.  The fetched
+objects will eventually be removed by git&#8217;s built-in housekeeping (see
+<a href='{{< relurl "docs/git-gc" >}}'>git-gc[1]</a>).</p>
+</div>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_security"><a class="anchor" href="#_security"></a>SECURITY</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The fetch and push protocols are not designed to prevent one side from
+stealing data from the other repository that was not intended to be
+shared. If you have private data that you need to protect from a malicious
+peer, your best option is to store it in another repository. This applies
+to both clients and servers. In particular, namespaces on a server are not
+effective for read access control; you should only grant read access to a
+namespace to clients that you would trust with read access to the entire
+repository.</p>
+</div>
+<div class="paragraph">
+<p>The known attack vectors are as follows:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>The victim sends "have" lines advertising the IDs of objects it has that
+are not explicitly intended to be shared but can be used to optimize the
+transfer if the peer also has them. The attacker chooses an object ID X
+to steal and sends a ref to X, but isn&#8217;t required to send the content of
+X because the victim already has it. Now the victim believes that the
+attacker has X, and it sends the content of X back to the attacker
+later. (This attack is most straightforward for a client to perform on a
+server, by creating a ref to X in the namespace the client has access
+to and then fetching it. The most likely way for a server to perform it
+on a client is to "merge" X into a public branch and hope that the user
+does additional work on this branch and pushes it back to the server
+without noticing the merge.)</p>
+</li>
+<li>
+<p>As in #1, the attacker chooses an object ID X to steal. The victim sends
+an object Y that the attacker already has, and the attacker falsely
+claims to have X and not Y, so the victim sends Y as a delta against X.
+The delta reveals regions of X that are similar to Y to the attacker.</p>
+</li>
+</ol>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_configuration"><a class="anchor" href="#_configuration"></a>CONFIGURATION</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Everything below this line in this section is selectively included
+from the <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a> documentation. The content is the same
+as what&#8217;s found there:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchrecurseSubmodules"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchrecurseSubmodules"></a>fetch.recurseSubmodules </dt>
+<dd>
+<p>This option controls whether <code>git fetch</code> (and the underlying fetch
+in <code>git pull</code>) will recursively fetch into populated submodules.
+This option can be set either to a boolean value or to <em>on-demand</em>.
+Setting it to a boolean changes the behavior of fetch and pull to
+recurse unconditionally into submodules when set to true or to not
+recurse at all when set to false. When set to <em>on-demand</em>, fetch and
+pull will only recurse into a populated submodule when its
+superproject retrieves a commit that updates the submodule&#8217;s
+reference.
+Defaults to <em>on-demand</em>, or to the value of <em>submodule.recurse</em> if set.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchfsckObjects"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchfsckObjects"></a>fetch.fsckObjects </dt>
+<dd>
+<p>If it is set to true, git-fetch-pack will check all fetched
+objects. See <code>transfer.fsckObjects</code> for what&#8217;s
+checked. Defaults to false. If not set, the value of
+<code>transfer.fsckObjects</code> is used instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchfsckltmsg-idgt"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchfsckltmsg-idgt"></a>fetch.fsck.&lt;msg-id&gt; </dt>
+<dd>
+<p>Acts like <code>fsck.&lt;msg-id&gt;</code>, but is used by
+<a href='{{< relurl "docs/git-fetch-pack" >}}'>git-fetch-pack[1]</a> instead of <a href='{{< relurl "docs/git-fsck" >}}'>git-fsck[1]</a>. See
+the <code>fsck.&lt;msg-id&gt;</code> documentation for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchfsckskipList"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchfsckskipList"></a>fetch.fsck.skipList </dt>
+<dd>
+<p>Acts like <code>fsck.skipList</code>, but is used by
+<a href='{{< relurl "docs/git-fetch-pack" >}}'>git-fetch-pack[1]</a> instead of <a href='{{< relurl "docs/git-fsck" >}}'>git-fsck[1]</a>. See
+the <code>fsck.skipList</code> documentation for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchunpackLimit"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchunpackLimit"></a>fetch.unpackLimit </dt>
+<dd>
+<p>If the number of objects fetched over the Git native
+transfer is below this
+limit, then the objects will be unpacked into loose object
+files. However if the number of received objects equals or
+exceeds this limit then the received pack will be stored as
+a pack, after adding any missing delta bases.  Storing the
+pack from a push can make the push operation complete faster,
+especially on slow filesystems.  If not set, the value of
+<code>transfer.unpackLimit</code> is used instead.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchprune"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchprune"></a>fetch.prune </dt>
+<dd>
+<p>If true, fetch will automatically behave as if the <code>--prune</code>
+option was given on the command line.  See also <code>remote.&lt;name&gt;.prune</code>
+and the PRUNING section of <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchpruneTags"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchpruneTags"></a>fetch.pruneTags </dt>
+<dd>
+<p>If true, fetch will automatically behave as if the
+<code>refs/tags/*:refs/tags/*</code> refspec was provided when pruning,
+if not set already. This allows for setting both this option
+and <code>fetch.prune</code> to maintain a 1=1 mapping to upstream
+refs. See also <code>remote.&lt;name&gt;.pruneTags</code> and the PRUNING
+section of <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchall"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchall"></a>fetch.all </dt>
+<dd>
+<p>If true, fetch will attempt to update all available remotes.
+This behavior can be overridden by passing <code>--no-all</code> or by
+explicitly specifying one or more remote(s) to fetch from.
+Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchoutput"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchoutput"></a>fetch.output </dt>
+<dd>
+<p>Control how ref update status is printed. Valid values are
+<code>full</code> and <code>compact</code>. Default value is <code>full</code>. See the
+OUTPUT section in <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchnegotiationAlgorithm"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchnegotiationAlgorithm"></a>fetch.negotiationAlgorithm </dt>
+<dd>
+<p>Control how information about the commits in the local repository
+is sent when negotiating the contents of the packfile to be sent by
+the server.  Set to "consecutive" to use an algorithm that walks
+over consecutive commits checking each one.  Set to "skipping" to
+use an algorithm that skips commits in an effort to converge
+faster, but may result in a larger-than-necessary packfile; or set
+to "noop" to not send any information at all, which will almost
+certainly result in a larger-than-necessary packfile, but will skip
+the negotiation step.  Set to "default" to override settings made
+previously and use the default behaviour.  The default is normally
+"consecutive", but if <code>feature.experimental</code> is true, then the
+default is "skipping".  Unknown values will cause <em>git fetch</em> to
+error out.</p>
+<div class="paragraph">
+<p>See also the <code>--negotiate-only</code> and <code>--negotiation-tip</code> options to
+<a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchshowForcedUpdates"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchshowForcedUpdates"></a>fetch.showForcedUpdates </dt>
+<dd>
+<p>Set to false to enable <code>--no-show-forced-updates</code> in
+<a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> and <a href='{{< relurl "docs/git-pull" >}}'>git-pull[1]</a> commands.
+Defaults to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchparallel"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchparallel"></a>fetch.parallel </dt>
+<dd>
+<p>Specifies the maximal number of fetch operations to be run in parallel
+at a time (submodules, or remotes when the <code>--multiple</code> option of
+<a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> is in effect).</p>
+<div class="paragraph">
+<p>A value of 0 will give some reasonable default. If unset, it defaults to 1.</p>
+</div>
+<div class="paragraph">
+<p>For submodules, this setting can be overridden using the <code>submodule.fetchJobs</code>
+config setting.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchwriteCommitGraph"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchwriteCommitGraph"></a>fetch.writeCommitGraph </dt>
+<dd>
+<p>Set to true to write a commit-graph after every <code>git fetch</code> command
+that downloads a pack-file from a remote. Using the <code>--split</code> option,
+most executions will create a very small commit-graph file on top of
+the existing commit-graph file(s). Occasionally, these files will
+merge and the write may take longer. Having an updated commit-graph
+file helps performance of many Git commands, including <code>git merge-base</code>,
+<code>git push -f</code>, and <code>git log --graph</code>. Defaults to false.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchbundleURI"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchbundleURI"></a>fetch.bundleURI </dt>
+<dd>
+<p>This value stores a URI for downloading Git object data from a bundle
+URI before performing an incremental fetch from the origin Git server.
+This is similar to how the <code>--bundle-uri</code> option behaves in
+<a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a>. <code>git clone --bundle-uri</code> will set the
+<code>fetch.bundleURI</code> value if the supplied bundle URI contains a bundle
+list that is organized for incremental fetches.</p>
+<div class="paragraph">
+<p>If you modify this value and your repository has a <code>fetch.bundleCreationToken</code>
+value, then remove that <code>fetch.bundleCreationToken</code> value before fetching from
+the new bundle URI.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-fetch.txt-fetchbundleCreationToken"> <a class="anchor" href="#Documentation/git-fetch.txt-fetchbundleCreationToken"></a>fetch.bundleCreationToken </dt>
+<dd>
+<p>When using <code>fetch.bundleURI</code> to fetch incrementally from a bundle
+list that uses the "creationToken" heuristic, this config value
+stores the maximum <code>creationToken</code> value of the downloaded bundles.
+This value is used to prevent downloading bundles in the future
+if the advertised <code>creationToken</code> is not strictly larger than this
+value.</p>
+<div class="paragraph">
+<p>The creation token values are chosen by the provider serving the specific
+bundle URI. If you modify the URI at <code>fetch.bundleURI</code>, then be sure to
+remove the value for the <code>fetch.bundleCreationToken</code> value before fetching.</p>
+</div>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_bugs"><a class="anchor" href="#_bugs"></a>BUGS</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Using --recurse-submodules can only fetch new commits in submodules that are
+present locally e.g. in <code>$GIT_DIR/modules/</code>. If the upstream adds a new
+submodule, that submodule cannot be fetched until it is cloned e.g. by <code>git
+submodule update</code>. This is expected to be fixed in a future Git version.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also"><a class="anchor" href="#_see_also"></a>SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><a href='{{< relurl "docs/git-pull" >}}'>git-pull[1]</a></p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_git"><a class="anchor" href="#_git"></a>GIT</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Part of the <a href='{{< relurl "docs/git" >}}'>git[1]</a> suite</p>
+</div>
+</div>
+</div>
\ No newline at end of file
diff --git a/external/docs/content/docs/git-filter-branch/2.44.0.html b/external/docs/content/docs/git-filter-branch/2.44.0.html
index b4ec32a633..425b6cd6f4 100644
--- a/external/docs/content/docs/git-filter-branch/2.44.0.html
+++ b/external/docs/content/docs/git-filter-branch/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-filter-branch/2.45.2/index.html"
 - "/docs/git-filter-branch/2.46.0/index.html"
 - "/docs/git-filter-branch/2.46.1/index.html"
+- "/docs/git-filter-branch/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-fmt-merge-msg/2.35.0.html b/external/docs/content/docs/git-fmt-merge-msg/2.35.0.html
index c7987bafe3..dc5fbdd847 100644
--- a/external/docs/content/docs/git-fmt-merge-msg/2.35.0.html
+++ b/external/docs/content/docs/git-fmt-merge-msg/2.35.0.html
@@ -69,6 +69,7 @@
 - "/docs/git-fmt-merge-msg/2.45.2/index.html"
 - "/docs/git-fmt-merge-msg/2.46.0/index.html"
 - "/docs/git-fmt-merge-msg/2.46.1/index.html"
+- "/docs/git-fmt-merge-msg/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-for-each-ref/2.45.0.html b/external/docs/content/docs/git-for-each-ref/2.45.0.html
index 2772658bb5..df38370441 100644
--- a/external/docs/content/docs/git-for-each-ref/2.45.0.html
+++ b/external/docs/content/docs/git-for-each-ref/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-for-each-ref/2.45.2/index.html"
 - "/docs/git-for-each-ref/2.46.0/index.html"
 - "/docs/git-for-each-ref/2.46.1/index.html"
+- "/docs/git-for-each-ref/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-for-each-repo/2.46.0.html b/external/docs/content/docs/git-for-each-repo/2.46.0.html
index dcae56eae4..0adc159996 100644
--- a/external/docs/content/docs/git-for-each-repo/2.46.0.html
+++ b/external/docs/content/docs/git-for-each-repo/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-for-each-repo/2.46.0/index.html"
 - "/docs/git-for-each-repo/2.46.1/index.html"
+- "/docs/git-for-each-repo/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-format-patch/2.46.0.html b/external/docs/content/docs/git-format-patch/2.46.0.html
index b776aef18b..647e7434d0 100644
--- a/external/docs/content/docs/git-format-patch/2.46.0.html
+++ b/external/docs/content/docs/git-format-patch/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-format-patch/2.46.0/index.html"
 - "/docs/git-format-patch/2.46.1/index.html"
+- "/docs/git-format-patch/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-fsck-objects/2.0.5.html b/external/docs/content/docs/git-fsck-objects/2.0.5.html
index 28bbe2cb8b..e382f96da8 100644
--- a/external/docs/content/docs/git-fsck-objects/2.0.5.html
+++ b/external/docs/content/docs/git-fsck-objects/2.0.5.html
@@ -196,6 +196,7 @@
 - "/docs/git-fsck-objects/2.45.2/index.html"
 - "/docs/git-fsck-objects/2.46.0/index.html"
 - "/docs/git-fsck-objects/2.46.1/index.html"
+- "/docs/git-fsck-objects/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-fsck/2.45.2.html b/external/docs/content/docs/git-fsck/2.45.2.html
index 6166e82664..91817ba457 100644
--- a/external/docs/content/docs/git-fsck/2.45.2.html
+++ b/external/docs/content/docs/git-fsck/2.45.2.html
@@ -11,6 +11,7 @@
 - "/docs/git-fsck/2.45.2/index.html"
 - "/docs/git-fsck/2.46.0/index.html"
 - "/docs/git-fsck/2.46.1/index.html"
+- "/docs/git-fsck/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-fsmonitor--daemon/2.43.0.html b/external/docs/content/docs/git-fsmonitor--daemon/2.43.0.html
index a52e9bdadc..8fd47c731c 100644
--- a/external/docs/content/docs/git-fsmonitor--daemon/2.43.0.html
+++ b/external/docs/content/docs/git-fsmonitor--daemon/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-fsmonitor--daemon/2.45.2/index.html"
 - "/docs/git-fsmonitor--daemon/2.46.0/index.html"
 - "/docs/git-fsmonitor--daemon/2.46.1/index.html"
+- "/docs/git-fsmonitor--daemon/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-gc/2.43.0.html b/external/docs/content/docs/git-gc/2.43.0.html
index 9ee383477e..d38fbf603a 100644
--- a/external/docs/content/docs/git-gc/2.43.0.html
+++ b/external/docs/content/docs/git-gc/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-gc/2.45.2/index.html"
 - "/docs/git-gc/2.46.0/index.html"
 - "/docs/git-gc/2.46.1/index.html"
+- "/docs/git-gc/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-get-tar-commit-id/2.43.0.html b/external/docs/content/docs/git-get-tar-commit-id/2.43.0.html
index e772ccb199..f809e273c2 100644
--- a/external/docs/content/docs/git-get-tar-commit-id/2.43.0.html
+++ b/external/docs/content/docs/git-get-tar-commit-id/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-get-tar-commit-id/2.45.2/index.html"
 - "/docs/git-get-tar-commit-id/2.46.0/index.html"
 - "/docs/git-get-tar-commit-id/2.46.1/index.html"
+- "/docs/git-get-tar-commit-id/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-grep/2.45.0.html b/external/docs/content/docs/git-grep/2.45.0.html
index 52b712ef37..d10d364e5b 100644
--- a/external/docs/content/docs/git-grep/2.45.0.html
+++ b/external/docs/content/docs/git-grep/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-grep/2.45.2/index.html"
 - "/docs/git-grep/2.46.0/index.html"
 - "/docs/git-grep/2.46.1/index.html"
+- "/docs/git-grep/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-gui/2.46.0.html b/external/docs/content/docs/git-gui/2.46.0.html
index 832207eaa0..7bfddb15d9 100644
--- a/external/docs/content/docs/git-gui/2.46.0.html
+++ b/external/docs/content/docs/git-gui/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-gui/2.46.0/index.html"
 - "/docs/git-gui/2.46.1/index.html"
+- "/docs/git-gui/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-hash-object/2.43.0.html b/external/docs/content/docs/git-hash-object/2.43.0.html
index 8b8fe545eb..2452a0764c 100644
--- a/external/docs/content/docs/git-hash-object/2.43.0.html
+++ b/external/docs/content/docs/git-hash-object/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-hash-object/2.45.2/index.html"
 - "/docs/git-hash-object/2.46.0/index.html"
 - "/docs/git-hash-object/2.46.1/index.html"
+- "/docs/git-hash-object/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-help/2.43.0.html b/external/docs/content/docs/git-help/2.43.0.html
index 8d66bb0386..8a86ecb580 100644
--- a/external/docs/content/docs/git-help/2.43.0.html
+++ b/external/docs/content/docs/git-help/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-help/2.45.2/index.html"
 - "/docs/git-help/2.46.0/index.html"
 - "/docs/git-help/2.46.1/index.html"
+- "/docs/git-help/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-hook/2.43.0.html b/external/docs/content/docs/git-hook/2.43.0.html
index 83a2273816..f6edf01a4e 100644
--- a/external/docs/content/docs/git-hook/2.43.0.html
+++ b/external/docs/content/docs/git-hook/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-hook/2.45.2/index.html"
 - "/docs/git-hook/2.46.0/index.html"
 - "/docs/git-hook/2.46.1/index.html"
+- "/docs/git-hook/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-http-backend/2.43.0.html b/external/docs/content/docs/git-http-backend/2.43.0.html
index f5a384cc3c..3a04cf90ec 100644
--- a/external/docs/content/docs/git-http-backend/2.43.0.html
+++ b/external/docs/content/docs/git-http-backend/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-http-backend/2.45.2/index.html"
 - "/docs/git-http-backend/2.46.0/index.html"
 - "/docs/git-http-backend/2.46.1/index.html"
+- "/docs/git-http-backend/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-http-fetch/2.43.0.html b/external/docs/content/docs/git-http-fetch/2.43.0.html
index 7b59721e12..fb741fa792 100644
--- a/external/docs/content/docs/git-http-fetch/2.43.0.html
+++ b/external/docs/content/docs/git-http-fetch/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-http-fetch/2.45.2/index.html"
 - "/docs/git-http-fetch/2.46.0/index.html"
 - "/docs/git-http-fetch/2.46.1/index.html"
+- "/docs/git-http-fetch/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-http-push/2.43.0.html b/external/docs/content/docs/git-http-push/2.43.0.html
index 8cf0d50d03..aac6b3a520 100644
--- a/external/docs/content/docs/git-http-push/2.43.0.html
+++ b/external/docs/content/docs/git-http-push/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-http-push/2.45.2/index.html"
 - "/docs/git-http-push/2.46.0/index.html"
 - "/docs/git-http-push/2.46.1/index.html"
+- "/docs/git-http-push/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-imap-send/2.43.1.html b/external/docs/content/docs/git-imap-send/2.43.1.html
index 4856b35157..7a959918d1 100644
--- a/external/docs/content/docs/git-imap-send/2.43.1.html
+++ b/external/docs/content/docs/git-imap-send/2.43.1.html
@@ -21,6 +21,7 @@
 - "/docs/git-imap-send/2.45.2/index.html"
 - "/docs/git-imap-send/2.46.0/index.html"
 - "/docs/git-imap-send/2.46.1/index.html"
+- "/docs/git-imap-send/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-index-pack/2.44.0.html b/external/docs/content/docs/git-index-pack/2.44.0.html
index db86325500..e1c35878b8 100644
--- a/external/docs/content/docs/git-index-pack/2.44.0.html
+++ b/external/docs/content/docs/git-index-pack/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-index-pack/2.45.2/index.html"
 - "/docs/git-index-pack/2.46.0/index.html"
 - "/docs/git-index-pack/2.46.1/index.html"
+- "/docs/git-index-pack/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-init-db/2.35.0.html b/external/docs/content/docs/git-init-db/2.35.0.html
index 004dbc4f28..2f36df6751 100644
--- a/external/docs/content/docs/git-init-db/2.35.0.html
+++ b/external/docs/content/docs/git-init-db/2.35.0.html
@@ -69,6 +69,7 @@
 - "/docs/git-init-db/2.45.2/index.html"
 - "/docs/git-init-db/2.46.0/index.html"
 - "/docs/git-init-db/2.46.1/index.html"
+- "/docs/git-init-db/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-init/2.45.0.html b/external/docs/content/docs/git-init/2.45.0.html
index 84581578b3..35e5691e74 100644
--- a/external/docs/content/docs/git-init/2.45.0.html
+++ b/external/docs/content/docs/git-init/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-init/2.45.2/index.html"
 - "/docs/git-init/2.46.0/index.html"
 - "/docs/git-init/2.46.1/index.html"
+- "/docs/git-init/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-instaweb/2.21.0.html b/external/docs/content/docs/git-instaweb/2.21.0.html
index 150d1e3871..05efd72ca3 100644
--- a/external/docs/content/docs/git-instaweb/2.21.0.html
+++ b/external/docs/content/docs/git-instaweb/2.21.0.html
@@ -153,6 +153,7 @@
 - "/docs/git-instaweb/2.45.2/index.html"
 - "/docs/git-instaweb/2.46.0/index.html"
 - "/docs/git-instaweb/2.46.1/index.html"
+- "/docs/git-instaweb/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-interpret-trailers/2.45.0.html b/external/docs/content/docs/git-interpret-trailers/2.45.0.html
index c7090090a1..927cc4fb43 100644
--- a/external/docs/content/docs/git-interpret-trailers/2.45.0.html
+++ b/external/docs/content/docs/git-interpret-trailers/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-interpret-trailers/2.45.2/index.html"
 - "/docs/git-interpret-trailers/2.46.0/index.html"
 - "/docs/git-interpret-trailers/2.46.1/index.html"
+- "/docs/git-interpret-trailers/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-log/2.46.0.html b/external/docs/content/docs/git-log/2.46.0.html
index a6d67d338d..f398f140c1 100644
--- a/external/docs/content/docs/git-log/2.46.0.html
+++ b/external/docs/content/docs/git-log/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-log/2.46.0/index.html"
 - "/docs/git-log/2.46.1/index.html"
+- "/docs/git-log/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-ls-files/2.46.1.html b/external/docs/content/docs/git-ls-files/2.46.1.html
index ef62a10c4c..00eb169edc 100644
--- a/external/docs/content/docs/git-ls-files/2.46.1.html
+++ b/external/docs/content/docs/git-ls-files/2.46.1.html
@@ -9,6 +9,7 @@
 version: 2.46.1
 aliases:
 - "/docs/git-ls-files/2.46.1/index.html"
+- "/docs/git-ls-files/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-ls-remote/2.46.0.html b/external/docs/content/docs/git-ls-remote/2.46.0.html
index bea0fc1980..b1ea53d09e 100644
--- a/external/docs/content/docs/git-ls-remote/2.46.0.html
+++ b/external/docs/content/docs/git-ls-remote/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-ls-remote/2.46.0/index.html"
 - "/docs/git-ls-remote/2.46.1/index.html"
+- "/docs/git-ls-remote/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-ls-tree/2.42.0.html b/external/docs/content/docs/git-ls-tree/2.42.0.html
index dd0a30231d..1104860200 100644
--- a/external/docs/content/docs/git-ls-tree/2.42.0.html
+++ b/external/docs/content/docs/git-ls-tree/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/git-ls-tree/2.45.2/index.html"
 - "/docs/git-ls-tree/2.46.0/index.html"
 - "/docs/git-ls-tree/2.46.1/index.html"
+- "/docs/git-ls-tree/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-mailinfo/2.43.0.html b/external/docs/content/docs/git-mailinfo/2.43.0.html
index 3b9581996f..601e5cf141 100644
--- a/external/docs/content/docs/git-mailinfo/2.43.0.html
+++ b/external/docs/content/docs/git-mailinfo/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-mailinfo/2.45.2/index.html"
 - "/docs/git-mailinfo/2.46.0/index.html"
 - "/docs/git-mailinfo/2.46.1/index.html"
+- "/docs/git-mailinfo/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-mailsplit/2.43.0.html b/external/docs/content/docs/git-mailsplit/2.43.0.html
index f2b23b7e79..7c7a676652 100644
--- a/external/docs/content/docs/git-mailsplit/2.43.0.html
+++ b/external/docs/content/docs/git-mailsplit/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-mailsplit/2.45.2/index.html"
 - "/docs/git-mailsplit/2.46.0/index.html"
 - "/docs/git-mailsplit/2.46.1/index.html"
+- "/docs/git-mailsplit/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-maintenance.html b/external/docs/content/docs/git-maintenance.html
index 3a18d79715..6c320360ed 100644
--- a/external/docs/content/docs/git-maintenance.html
+++ b/external/docs/content/docs/git-maintenance.html
@@ -6,8 +6,8 @@
 subsection: manual
 title: Git - git-maintenance Documentation
 docname: git-maintenance
-version: 2.43.0
-latest-changes: 2.43.0
+version: 2.46.2
+latest-changes: 2.46.2
 aliases:
 - "/docs/git-maintenance/index.html"
 ---
@@ -162,6 +162,10 @@ <h2 id="_tasks"><a class="anchor" href="#_tasks"></a>TASKS</h2>
 it will just become an update to a bunch of remote-tracking branches without
 any object transfer.</p>
 </div>
+<div class="paragraph">
+<p>The <code>remote.&lt;name&gt;.skipFetchAll</code> configuration can be used to
+exclude a particular remote from getting prefetched.</p>
+</div>
 </dd>
 <dt class="hdlist1" id="Documentation/git-maintenance.txt-gc"> <a class="anchor" href="#Documentation/git-maintenance.txt-gc"></a>gc </dt>
 <dd>
diff --git a/external/docs/content/docs/git-maintenance/2.46.2.html b/external/docs/content/docs/git-maintenance/2.46.2.html
new file mode 100644
index 0000000000..70198c7e8b
--- /dev/null
+++ b/external/docs/content/docs/git-maintenance/2.46.2.html
@@ -0,0 +1,617 @@
+---
+### DO NOT EDIT! Generated by script/update-docs.rb
+
+category: manual
+section: documentation
+subsection: manual
+title: Git - git-maintenance Documentation
+docname: git-maintenance
+version: 2.46.2
+aliases:
+- "/docs/git-maintenance/2.46.2/index.html"
+---
+<div class="sect1">
+<h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>git-maintenance - Run tasks to optimize Git repository data</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_synopsis"><a class="anchor" href="#_synopsis"></a>SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="verseblock">
+<pre class="content"><em>git maintenance</em> run [&lt;options&gt;]
+<em>git maintenance</em> start [--scheduler=&lt;scheduler&gt;]
+<em>git maintenance</em> (stop|register|unregister) [&lt;options&gt;]</pre>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description"><a class="anchor" href="#_description"></a>DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Run tasks to optimize Git repository data, speeding up other Git commands
+and reducing storage requirements for the repository.</p>
+</div>
+<div class="paragraph">
+<p>Git commands that add repository data, such as <code>git add</code> or <code>git fetch</code>,
+are optimized for a responsive user experience. These commands do not take
+time to optimize the Git data, since such optimizations scale with the full
+size of the repository while these user commands each perform a relatively
+small action.</p>
+</div>
+<div class="paragraph">
+<p>The <code>git maintenance</code> command provides flexibility for how to optimize the
+Git repository.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_subcommands"><a class="anchor" href="#_subcommands"></a>SUBCOMMANDS</h2>
+<div class="sectionbody">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-run"> <a class="anchor" href="#Documentation/git-maintenance.txt-run"></a>run </dt>
+<dd>
+<p>Run one or more maintenance tasks. If one or more <code>--task</code> options
+are specified, then those tasks are run in that order. Otherwise,
+the tasks are determined by which <code>maintenance.&lt;task&gt;.enabled</code>
+config options are true. By default, only <code>maintenance.gc.enabled</code>
+is true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-start"> <a class="anchor" href="#Documentation/git-maintenance.txt-start"></a>start </dt>
+<dd>
+<p>Start running maintenance on the current repository. This performs
+the same config updates as the <code>register</code> subcommand, then updates
+the background scheduler to run <code>git maintenance run --scheduled</code>
+on an hourly basis.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-stop"> <a class="anchor" href="#Documentation/git-maintenance.txt-stop"></a>stop </dt>
+<dd>
+<p>Halt the background maintenance schedule. The current repository
+is not removed from the list of maintained repositories, in case
+the background maintenance is restarted later.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-register"> <a class="anchor" href="#Documentation/git-maintenance.txt-register"></a>register </dt>
+<dd>
+<p>Initialize Git config values so any scheduled maintenance will start
+running on this repository. This adds the repository to the
+<code>maintenance.repo</code> config variable in the current user&#8217;s global config,
+or the config specified by --config-file option, and enables some
+recommended configuration values for <code>maintenance.&lt;task&gt;.schedule</code>. The
+tasks that are enabled are safe for running in the background without
+disrupting foreground processes.</p>
+<div class="paragraph">
+<p>The <code>register</code> subcommand will also set the <code>maintenance.strategy</code> config
+value to <code>incremental</code>, if this value is not previously set. The
+<code>incremental</code> strategy uses the following schedule for each maintenance
+task:</p>
+</div>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p><code>gc</code>: disabled.</p>
+</li>
+<li>
+<p><code>commit-graph</code>: hourly.</p>
+</li>
+<li>
+<p><code>prefetch</code>: hourly.</p>
+</li>
+<li>
+<p><code>loose-objects</code>: daily.</p>
+</li>
+<li>
+<p><code>incremental-repack</code>: daily.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p><code>git maintenance register</code> will also disable foreground maintenance by
+setting <code>maintenance.auto = false</code> in the current repository. This config
+setting will remain after a <code>git maintenance unregister</code> command.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-unregister"> <a class="anchor" href="#Documentation/git-maintenance.txt-unregister"></a>unregister </dt>
+<dd>
+<p>Remove the current repository from background maintenance. This
+only removes the repository from the configured list. It does not
+stop the background maintenance processes from running.</p>
+<div class="paragraph">
+<p>The <code>unregister</code> subcommand will report an error if the current repository
+is not already registered. Use the <code>--force</code> option to return success even
+when the current repository is not registered.</p>
+</div>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_tasks"><a class="anchor" href="#_tasks"></a>TASKS</h2>
+<div class="sectionbody">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-commit-graph"> <a class="anchor" href="#Documentation/git-maintenance.txt-commit-graph"></a>commit-graph </dt>
+<dd>
+<p>The <code>commit-graph</code> job updates the <code>commit-graph</code> files incrementally,
+then verifies that the written data is correct. The incremental
+write is safe to run alongside concurrent Git processes since it
+will not expire <code>.graph</code> files that were in the previous
+<code>commit-graph-chain</code> file. They will be deleted by a later run based
+on the expiration delay.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-prefetch"> <a class="anchor" href="#Documentation/git-maintenance.txt-prefetch"></a>prefetch </dt>
+<dd>
+<p>The <code>prefetch</code> task updates the object directory with the latest
+objects from all registered remotes. For each remote, a <code>git fetch</code>
+command is run. The configured refspec is modified to place all
+requested refs within <code>refs/prefetch/</code>. Also, tags are not updated.</p>
+<div class="paragraph">
+<p>This is done to avoid disrupting the remote-tracking branches. The end users
+expect these refs to stay unmoved unless they initiate a fetch.  However,
+with the prefetch task, the objects necessary to complete a later real fetch
+would already be obtained, making the real fetch faster.  In the ideal case,
+it will just become an update to a bunch of remote-tracking branches without
+any object transfer.</p>
+</div>
+<div class="paragraph">
+<p>The <code>remote.&lt;name&gt;.skipFetchAll</code> configuration can be used to
+exclude a particular remote from getting prefetched.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-gc"> <a class="anchor" href="#Documentation/git-maintenance.txt-gc"></a>gc </dt>
+<dd>
+<p>Clean up unnecessary files and optimize the local repository. "GC"
+stands for "garbage collection," but this task performs many
+smaller tasks. This task can be expensive for large repositories,
+as it repacks all Git objects into a single pack-file. It can also
+be disruptive in some situations, as it deletes stale data. See
+<a href='{{< relurl "docs/git-gc" >}}'>git-gc[1]</a> for more details on garbage collection in Git.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-loose-objects"> <a class="anchor" href="#Documentation/git-maintenance.txt-loose-objects"></a>loose-objects </dt>
+<dd>
+<p>The <code>loose-objects</code> job cleans up loose objects and places them into
+pack-files. In order to prevent race conditions with concurrent Git
+commands, it follows a two-step process. First, it deletes any loose
+objects that already exist in a pack-file; concurrent Git processes
+will examine the pack-file for the object data instead of the loose
+object. Second, it creates a new pack-file (starting with "loose-")
+containing a batch of loose objects. The batch size is limited to 50
+thousand objects to prevent the job from taking too long on a
+repository with many loose objects. The <code>gc</code> task writes unreachable
+objects as loose objects to be cleaned up by a later step only if
+they are not re-added to a pack-file; for this reason it is not
+advisable to enable both the <code>loose-objects</code> and <code>gc</code> tasks at the
+same time.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-incremental-repack"> <a class="anchor" href="#Documentation/git-maintenance.txt-incremental-repack"></a>incremental-repack </dt>
+<dd>
+<p>The <code>incremental-repack</code> job repacks the object directory
+using the <code>multi-pack-index</code> feature. In order to prevent race
+conditions with concurrent Git commands, it follows a two-step
+process. First, it calls <code>git multi-pack-index expire</code> to delete
+pack-files unreferenced by the <code>multi-pack-index</code> file. Second, it
+calls <code>git multi-pack-index repack</code> to select several small
+pack-files and repack them into a bigger one, and then update the
+<code>multi-pack-index</code> entries that refer to the small pack-files to
+refer to the new pack-file. This prepares those small pack-files
+for deletion upon the next run of <code>git multi-pack-index expire</code>.
+The selection of the small pack-files is such that the expected
+size of the big pack-file is at least the batch size; see the
+<code>--batch-size</code> option for the <code>repack</code> subcommand in
+<a href='{{< relurl "docs/git-multi-pack-index" >}}'>git-multi-pack-index[1]</a>. The default batch-size is zero,
+which is a special case that attempts to repack all pack-files
+into a single pack-file.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-pack-refs"> <a class="anchor" href="#Documentation/git-maintenance.txt-pack-refs"></a>pack-refs </dt>
+<dd>
+<p>The <code>pack-refs</code> task collects the loose reference files and
+collects them into a single file. This speeds up operations that
+need to iterate across many references. See <a href='{{< relurl "docs/git-pack-refs" >}}'>git-pack-refs[1]</a>
+for more information.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_options"><a class="anchor" href="#_options"></a>OPTIONS</h2>
+<div class="sectionbody">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt---auto"> <a class="anchor" href="#Documentation/git-maintenance.txt---auto"></a>--auto </dt>
+<dd>
+<p>When combined with the <code>run</code> subcommand, run maintenance tasks
+only if certain thresholds are met. For example, the <code>gc</code> task
+runs when the number of loose objects exceeds the number stored
+in the <code>gc.auto</code> config setting, or when the number of pack-files
+exceeds the <code>gc.autoPackLimit</code> config setting. Not compatible with
+the <code>--schedule</code> option.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt---schedule"> <a class="anchor" href="#Documentation/git-maintenance.txt---schedule"></a>--schedule </dt>
+<dd>
+<p>When combined with the <code>run</code> subcommand, run maintenance tasks
+only if certain time conditions are met, as specified by the
+<code>maintenance.&lt;task&gt;.schedule</code> config value for each <code>&lt;task&gt;</code>.
+This config value specifies a number of seconds since the last
+time that task ran, according to the <code>maintenance.&lt;task&gt;.lastRun</code>
+config value. The tasks that are tested are those provided by
+the <code>--task=&lt;task&gt;</code> option(s) or those with
+<code>maintenance.&lt;task&gt;.enabled</code> set to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt---quiet"> <a class="anchor" href="#Documentation/git-maintenance.txt---quiet"></a>--quiet </dt>
+<dd>
+<p>Do not report progress or other information over <code>stderr</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt---tasklttaskgt"> <a class="anchor" href="#Documentation/git-maintenance.txt---tasklttaskgt"></a>--task=&lt;task&gt; </dt>
+<dd>
+<p>If this option is specified one or more times, then only run the
+specified tasks in the specified order. If no <code>--task=&lt;task&gt;</code>
+arguments are specified, then only the tasks with
+<code>maintenance.&lt;task&gt;.enabled</code> configured as <code>true</code> are considered.
+See the <em>TASKS</em> section for the list of accepted <code>&lt;task&gt;</code> values.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt---schedulerautocrontabsystemd-timerlaunchctlschtasks"> <a class="anchor" href="#Documentation/git-maintenance.txt---schedulerautocrontabsystemd-timerlaunchctlschtasks"></a>--scheduler=auto|crontab|systemd-timer|launchctl|schtasks </dt>
+<dd>
+<p>When combined with the <code>start</code> subcommand, specify the scheduler
+for running the hourly, daily and weekly executions of
+<code>git maintenance run</code>.
+Possible values for <code>&lt;scheduler&gt;</code> are <code>auto</code>, <code>crontab</code>
+(POSIX), <code>systemd-timer</code> (Linux), <code>launchctl</code> (macOS), and
+<code>schtasks</code> (Windows). When <code>auto</code> is specified, the
+appropriate platform-specific scheduler is used; on Linux,
+<code>systemd-timer</code> is used if available, otherwise
+<code>crontab</code>. Default is <code>auto</code>.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_troubleshooting"><a class="anchor" href="#_troubleshooting"></a>TROUBLESHOOTING</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The <code>git maintenance</code> command is designed to simplify the repository
+maintenance patterns while minimizing user wait time during Git commands.
+A variety of configuration options are available to allow customizing this
+process. The default maintenance options focus on operations that complete
+quickly, even on large repositories.</p>
+</div>
+<div class="paragraph">
+<p>Users may find some cases where scheduled maintenance tasks do not run as
+frequently as intended. Each <code>git maintenance run</code> command takes a lock on
+the repository&#8217;s object database, and this prevents other concurrent
+<code>git maintenance run</code> commands from running on the same repository. Without
+this safeguard, competing processes could leave the repository in an
+unpredictable state.</p>
+</div>
+<div class="paragraph">
+<p>The background maintenance schedule runs <code>git maintenance run</code> processes
+on an hourly basis. Each run executes the "hourly" tasks. At midnight,
+that process also executes the "daily" tasks. At midnight on the first day
+of the week, that process also executes the "weekly" tasks. A single
+process iterates over each registered repository, performing the scheduled
+tasks for that frequency. Depending on the number of registered
+repositories and their sizes, this process may take longer than an hour.
+In this case, multiple <code>git maintenance run</code> commands may run on the same
+repository at the same time, colliding on the object database lock. This
+results in one of the two tasks not running.</p>
+</div>
+<div class="paragraph">
+<p>If you find that some maintenance windows are taking longer than one hour
+to complete, then consider reducing the complexity of your maintenance
+tasks. For example, the <code>gc</code> task is much slower than the
+<code>incremental-repack</code> task. However, this comes at a cost of a slightly
+larger object database. Consider moving more expensive tasks to be run
+less frequently.</p>
+</div>
+<div class="paragraph">
+<p>Expert users may consider scheduling their own maintenance tasks using a
+different schedule than is available through <code>git maintenance start</code> and
+Git configuration options. These users should be aware of the object
+database lock and how concurrent <code>git maintenance run</code> commands behave.
+Further, the <code>git gc</code> command should not be combined with
+<code>git maintenance run</code> commands. <code>git gc</code> modifies the object database
+but does not take the lock in the same way as <code>git maintenance run</code>. If
+possible, use <code>git maintenance run --task=gc</code> instead of <code>git gc</code>.</p>
+</div>
+<div class="paragraph">
+<p>The following sections describe the mechanisms put in place to run
+background maintenance by <code>git maintenance start</code> and how to customize
+them.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_background_maintenance_on_posix_systems"><a class="anchor" href="#_background_maintenance_on_posix_systems"></a>BACKGROUND MAINTENANCE ON POSIX SYSTEMS</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The standard mechanism for scheduling background tasks on POSIX systems
+is cron(8). This tool executes commands based on a given schedule. The
+current list of user-scheduled tasks can be found by running <code>crontab -l</code>.
+The schedule written by <code>git maintenance start</code> is similar to this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre># BEGIN GIT MAINTENANCE SCHEDULE
+# The following schedule was created by Git
+# Any edits made in this region might be
+# replaced in the future by a Git command.
+
+0 1-23 * * * "/&lt;path&gt;/git" --exec-path="/&lt;path&gt;" for-each-repo --config=maintenance.repo maintenance run --schedule=hourly
+0 0 * * 1-6 "/&lt;path&gt;/git" --exec-path="/&lt;path&gt;" for-each-repo --config=maintenance.repo maintenance run --schedule=daily
+0 0 * * 0 "/&lt;path&gt;/git" --exec-path="/&lt;path&gt;" for-each-repo --config=maintenance.repo maintenance run --schedule=weekly
+
+# END GIT MAINTENANCE SCHEDULE</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The comments are used as a region to mark the schedule as written by Git.
+Any modifications within this region will be completely deleted by
+<code>git maintenance stop</code> or overwritten by <code>git maintenance start</code>.</p>
+</div>
+<div class="paragraph">
+<p>The <code>crontab</code> entry specifies the full path of the <code>git</code> executable to
+ensure that the executed <code>git</code> command is the same one with which
+<code>git maintenance start</code> was issued independent of <code>PATH</code>. If the same user
+runs <code>git maintenance start</code> with multiple Git executables, then only the
+latest executable is used.</p>
+</div>
+<div class="paragraph">
+<p>These commands use <code>git for-each-repo --config=maintenance.repo</code> to run
+<code>git maintenance run --schedule=&lt;frequency&gt;</code> on each repository listed in
+the multi-valued <code>maintenance.repo</code> config option. These are typically
+loaded from the user-specific global config. The <code>git maintenance</code> process
+then determines which maintenance tasks are configured to run on each
+repository with each <code>&lt;frequency&gt;</code> using the <code>maintenance.&lt;task&gt;.schedule</code>
+config options. These values are loaded from the global or repository
+config values.</p>
+</div>
+<div class="paragraph">
+<p>If the config values are insufficient to achieve your desired background
+maintenance schedule, then you can create your own schedule. If you run
+<code>crontab -e</code>, then an editor will load with your user-specific <code>cron</code>
+schedule. In that editor, you can add your own schedule lines. You could
+start by adapting the default schedule listed earlier, or you could read
+the crontab(5) documentation for advanced scheduling techniques. Please
+do use the full path and <code>--exec-path</code> techniques from the default
+schedule to ensure you are executing the correct binaries in your
+schedule.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_background_maintenance_on_linux_systemd_systems"><a class="anchor" href="#_background_maintenance_on_linux_systemd_systems"></a>BACKGROUND MAINTENANCE ON LINUX SYSTEMD SYSTEMS</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>While Linux supports <code>cron</code>, depending on the distribution, <code>cron</code> may
+be an optional package not necessarily installed. On modern Linux
+distributions, systemd timers are superseding it.</p>
+</div>
+<div class="paragraph">
+<p>If user systemd timers are available, they will be used as a replacement
+of <code>cron</code>.</p>
+</div>
+<div class="paragraph">
+<p>In this case, <code>git maintenance start</code> will create user systemd timer units
+and start the timers. The current list of user-scheduled tasks can be found
+by running <code>systemctl --user list-timers</code>. The timers written by <code>git
+maintenance start</code> are similar to this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>$ systemctl --user list-timers
+NEXT                         LEFT          LAST                         PASSED     UNIT                         ACTIVATES
+Thu 2021-04-29 19:00:00 CEST 42min left    Thu 2021-04-29 18:00:11 CEST 17min ago  git-maintenance@hourly.timer git-maintenance@hourly.service
+Fri 2021-04-30 00:00:00 CEST 5h 42min left Thu 2021-04-29 00:00:11 CEST 18h ago    git-maintenance@daily.timer  git-maintenance@daily.service
+Mon 2021-05-03 00:00:00 CEST 3 days left   Mon 2021-04-26 00:00:11 CEST 3 days ago git-maintenance@weekly.timer git-maintenance@weekly.service</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>One timer is registered for each <code>--schedule=&lt;frequency&gt;</code> option.</p>
+</div>
+<div class="paragraph">
+<p>The definition of the systemd units can be inspected in the following files:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>~/.config/systemd/user/git-maintenance@.timer
+~/.config/systemd/user/git-maintenance@.service
+~/.config/systemd/user/timers.target.wants/git-maintenance@hourly.timer
+~/.config/systemd/user/timers.target.wants/git-maintenance@daily.timer
+~/.config/systemd/user/timers.target.wants/git-maintenance@weekly.timer</pre>
+</div>
+</div>
+<div class="paragraph">
+<p><code>git maintenance start</code> will overwrite these files and start the timer
+again with <code>systemctl --user</code>, so any customization should be done by
+creating a drop-in file, i.e. a <code>.conf</code> suffixed file in the
+<code>~/.config/systemd/user/git-maintenance@.service.d</code> directory.</p>
+</div>
+<div class="paragraph">
+<p><code>git maintenance stop</code> will stop the user systemd timers and delete
+the above mentioned files.</p>
+</div>
+<div class="paragraph">
+<p>For more details, see <code>systemd.timer(5)</code>.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_background_maintenance_on_macos_systems"><a class="anchor" href="#_background_maintenance_on_macos_systems"></a>BACKGROUND MAINTENANCE ON MACOS SYSTEMS</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>While macOS technically supports <code>cron</code>, using <code>crontab -e</code> requires
+elevated privileges and the executed process does not have a full user
+context. Without a full user context, Git and its credential helpers
+cannot access stored credentials, so some maintenance tasks are not
+functional.</p>
+</div>
+<div class="paragraph">
+<p>Instead, <code>git maintenance start</code> interacts with the <code>launchctl</code> tool,
+which is the recommended way to schedule timed jobs in macOS. Scheduling
+maintenance through <code>git maintenance (start|stop)</code> requires some
+<code>launchctl</code> features available only in macOS 10.11 or later.</p>
+</div>
+<div class="paragraph">
+<p>Your user-specific scheduled tasks are stored as XML-formatted <code>.plist</code>
+files in <code>~/Library/LaunchAgents/</code>. You can see the currently-registered
+tasks using the following command:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>$ ls ~/Library/LaunchAgents/org.git-scm.git*
+org.git-scm.git.daily.plist
+org.git-scm.git.hourly.plist
+org.git-scm.git.weekly.plist</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>One task is registered for each <code>--schedule=&lt;frequency&gt;</code> option. To
+inspect how the XML format describes each schedule, open one of these
+<code>.plist</code> files in an editor and inspect the <code>&lt;array&gt;</code> element following
+the <code>&lt;key&gt;StartCalendarInterval&lt;/key&gt;</code> element.</p>
+</div>
+<div class="paragraph">
+<p><code>git maintenance start</code> will overwrite these files and register the
+tasks again with <code>launchctl</code>, so any customizations should be done by
+creating your own <code>.plist</code> files with distinct names. Similarly, the
+<code>git maintenance stop</code> command will unregister the tasks with <code>launchctl</code>
+and delete the <code>.plist</code> files.</p>
+</div>
+<div class="paragraph">
+<p>To create more advanced customizations to your background tasks, see
+launchctl.plist(5) for more information.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_background_maintenance_on_windows_systems"><a class="anchor" href="#_background_maintenance_on_windows_systems"></a>BACKGROUND MAINTENANCE ON WINDOWS SYSTEMS</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Windows does not support <code>cron</code> and instead has its own system for
+scheduling background tasks. The <code>git maintenance start</code> command uses
+the <code>schtasks</code> command to submit tasks to this system. You can inspect
+all background tasks using the Task Scheduler application. The tasks
+added by Git have names of the form <code>Git Maintenance (&lt;frequency&gt;)</code>.
+The Task Scheduler GUI has ways to inspect these tasks, but you can also
+export the tasks to XML files and view the details there.</p>
+</div>
+<div class="paragraph">
+<p>Note that since Git is a console application, these background tasks
+create a console window visible to the current user. This can be changed
+manually by selecting the "Run whether user is logged in or not" option
+in Task Scheduler. This change requires a password input, which is why
+<code>git maintenance start</code> does not select it by default.</p>
+</div>
+<div class="paragraph">
+<p>If you want to customize the background tasks, please rename the tasks
+so future calls to <code>git maintenance (start|stop)</code> do not overwrite your
+custom tasks.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_configuration"><a class="anchor" href="#_configuration"></a>CONFIGURATION</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Everything below this line in this section is selectively included
+from the <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a> documentation. The content is the same
+as what&#8217;s found there:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-maintenanceauto"> <a class="anchor" href="#Documentation/git-maintenance.txt-maintenanceauto"></a>maintenance.auto </dt>
+<dd>
+<p>This boolean config option controls whether some commands run
+<code>git maintenance run --auto</code> after doing their normal work. Defaults
+to true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-maintenancestrategy"> <a class="anchor" href="#Documentation/git-maintenance.txt-maintenancestrategy"></a>maintenance.strategy </dt>
+<dd>
+<p>This string config option provides a way to specify one of a few
+recommended schedules for background maintenance. This only affects
+which tasks are run during <code>git maintenance run --schedule=X</code>
+commands, provided no <code>--task=&lt;task&gt;</code> arguments are provided.
+Further, if a <code>maintenance.&lt;task&gt;.schedule</code> config value is set,
+then that value is used instead of the one provided by
+<code>maintenance.strategy</code>. The possible strategy strings are:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>none</code>: This default setting implies no tasks are run at any schedule.</p>
+</li>
+<li>
+<p><code>incremental</code>: This setting optimizes for performing small maintenance
+activities that do not delete any data. This does not schedule the <code>gc</code>
+task, but runs the <code>prefetch</code> and <code>commit-graph</code> tasks hourly, the
+<code>loose-objects</code> and <code>incremental-repack</code> tasks daily, and the <code>pack-refs</code>
+task weekly.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-maintenancelttaskgtenabled"> <a class="anchor" href="#Documentation/git-maintenance.txt-maintenancelttaskgtenabled"></a>maintenance.&lt;task&gt;.enabled </dt>
+<dd>
+<p>This boolean config option controls whether the maintenance task
+with name <code>&lt;task&gt;</code> is run when no <code>--task</code> option is specified to
+<code>git maintenance run</code>. These config values are ignored if a
+<code>--task</code> option exists. By default, only <code>maintenance.gc.enabled</code>
+is true.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-maintenancelttaskgtschedule"> <a class="anchor" href="#Documentation/git-maintenance.txt-maintenancelttaskgtschedule"></a>maintenance.&lt;task&gt;.schedule </dt>
+<dd>
+<p>This config option controls whether or not the given <code>&lt;task&gt;</code> runs
+during a <code>git maintenance run --schedule=&lt;frequency&gt;</code> command. The
+value must be one of "hourly", "daily", or "weekly".</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-maintenancecommit-graphauto"> <a class="anchor" href="#Documentation/git-maintenance.txt-maintenancecommit-graphauto"></a>maintenance.commit-graph.auto </dt>
+<dd>
+<p>This integer config option controls how often the <code>commit-graph</code> task
+should be run as part of <code>git maintenance run --auto</code>. If zero, then
+the <code>commit-graph</code> task will not run with the <code>--auto</code> option. A
+negative value will force the task to run every time. Otherwise, a
+positive value implies the command should run when the number of
+reachable commits that are not in the commit-graph file is at least
+the value of <code>maintenance.commit-graph.auto</code>. The default value is
+100.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-maintenanceloose-objectsauto"> <a class="anchor" href="#Documentation/git-maintenance.txt-maintenanceloose-objectsauto"></a>maintenance.loose-objects.auto </dt>
+<dd>
+<p>This integer config option controls how often the <code>loose-objects</code> task
+should be run as part of <code>git maintenance run --auto</code>. If zero, then
+the <code>loose-objects</code> task will not run with the <code>--auto</code> option. A
+negative value will force the task to run every time. Otherwise, a
+positive value implies the command should run when the number of
+loose objects is at least the value of <code>maintenance.loose-objects.auto</code>.
+The default value is 100.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-maintenance.txt-maintenanceincremental-repackauto"> <a class="anchor" href="#Documentation/git-maintenance.txt-maintenanceincremental-repackauto"></a>maintenance.incremental-repack.auto </dt>
+<dd>
+<p>This integer config option controls how often the <code>incremental-repack</code>
+task should be run as part of <code>git maintenance run --auto</code>. If zero,
+then the <code>incremental-repack</code> task will not run with the <code>--auto</code>
+option. A negative value will force the task to run every time.
+Otherwise, a positive value implies the command should run when the
+number of pack-files not in the multi-pack-index is at least the value
+of <code>maintenance.incremental-repack.auto</code>. The default value is 10.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_git"><a class="anchor" href="#_git"></a>GIT</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Part of the <a href='{{< relurl "docs/git" >}}'>git[1]</a> suite</p>
+</div>
+</div>
+</div>
\ No newline at end of file
diff --git a/external/docs/content/docs/git-merge-base/2.43.0.html b/external/docs/content/docs/git-merge-base/2.43.0.html
index 31e965a4b2..2c1b1433bf 100644
--- a/external/docs/content/docs/git-merge-base/2.43.0.html
+++ b/external/docs/content/docs/git-merge-base/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-merge-base/2.45.2/index.html"
 - "/docs/git-merge-base/2.46.0/index.html"
 - "/docs/git-merge-base/2.46.1/index.html"
+- "/docs/git-merge-base/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-merge-file/2.44.0.html b/external/docs/content/docs/git-merge-file/2.44.0.html
index d94b7ab849..aeb72a9125 100644
--- a/external/docs/content/docs/git-merge-file/2.44.0.html
+++ b/external/docs/content/docs/git-merge-file/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-merge-file/2.45.2/index.html"
 - "/docs/git-merge-file/2.46.0/index.html"
 - "/docs/git-merge-file/2.46.1/index.html"
+- "/docs/git-merge-file/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-merge-index/2.35.0.html b/external/docs/content/docs/git-merge-index/2.35.0.html
index 750951a839..8c1e845ae0 100644
--- a/external/docs/content/docs/git-merge-index/2.35.0.html
+++ b/external/docs/content/docs/git-merge-index/2.35.0.html
@@ -69,6 +69,7 @@
 - "/docs/git-merge-index/2.45.2/index.html"
 - "/docs/git-merge-index/2.46.0/index.html"
 - "/docs/git-merge-index/2.46.1/index.html"
+- "/docs/git-merge-index/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-merge-one-file/2.0.5.html b/external/docs/content/docs/git-merge-one-file/2.0.5.html
index ea5cf8e16f..af17b09088 100644
--- a/external/docs/content/docs/git-merge-one-file/2.0.5.html
+++ b/external/docs/content/docs/git-merge-one-file/2.0.5.html
@@ -196,6 +196,7 @@
 - "/docs/git-merge-one-file/2.45.2/index.html"
 - "/docs/git-merge-one-file/2.46.0/index.html"
 - "/docs/git-merge-one-file/2.46.1/index.html"
+- "/docs/git-merge-one-file/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-merge-tree/2.46.0.html b/external/docs/content/docs/git-merge-tree/2.46.0.html
index 169531a9f6..03814896e1 100644
--- a/external/docs/content/docs/git-merge-tree/2.46.0.html
+++ b/external/docs/content/docs/git-merge-tree/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-merge-tree/2.46.0/index.html"
 - "/docs/git-merge-tree/2.46.1/index.html"
+- "/docs/git-merge-tree/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-merge/2.43.1.html b/external/docs/content/docs/git-merge/2.43.1.html
index 62510fa8c9..81c8df381d 100644
--- a/external/docs/content/docs/git-merge/2.43.1.html
+++ b/external/docs/content/docs/git-merge/2.43.1.html
@@ -21,6 +21,7 @@
 - "/docs/git-merge/2.45.2/index.html"
 - "/docs/git-merge/2.46.0/index.html"
 - "/docs/git-merge/2.46.1/index.html"
+- "/docs/git-merge/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-mergetool--lib/2.43.0.html b/external/docs/content/docs/git-mergetool--lib/2.43.0.html
index d7decdefef..3d23d5e9c6 100644
--- a/external/docs/content/docs/git-mergetool--lib/2.43.0.html
+++ b/external/docs/content/docs/git-mergetool--lib/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-mergetool--lib/2.45.2/index.html"
 - "/docs/git-mergetool--lib/2.46.0/index.html"
 - "/docs/git-mergetool--lib/2.46.1/index.html"
+- "/docs/git-mergetool--lib/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-mergetool/2.45.0.html b/external/docs/content/docs/git-mergetool/2.45.0.html
index 19b0a45b70..0140fd5cfa 100644
--- a/external/docs/content/docs/git-mergetool/2.45.0.html
+++ b/external/docs/content/docs/git-mergetool/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-mergetool/2.45.2/index.html"
 - "/docs/git-mergetool/2.46.0/index.html"
 - "/docs/git-mergetool/2.46.1/index.html"
+- "/docs/git-mergetool/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-mktag/2.43.0.html b/external/docs/content/docs/git-mktag/2.43.0.html
index 055c76a406..7f042efb20 100644
--- a/external/docs/content/docs/git-mktag/2.43.0.html
+++ b/external/docs/content/docs/git-mktag/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-mktag/2.45.2/index.html"
 - "/docs/git-mktag/2.46.0/index.html"
 - "/docs/git-mktag/2.46.1/index.html"
+- "/docs/git-mktag/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-mktree/2.43.0.html b/external/docs/content/docs/git-mktree/2.43.0.html
index 51467cacf3..8d4f242f13 100644
--- a/external/docs/content/docs/git-mktree/2.43.0.html
+++ b/external/docs/content/docs/git-mktree/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-mktree/2.45.2/index.html"
 - "/docs/git-mktree/2.46.0/index.html"
 - "/docs/git-mktree/2.46.1/index.html"
+- "/docs/git-mktree/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-multi-pack-index/2.38.2.html b/external/docs/content/docs/git-multi-pack-index/2.38.2.html
index c7c81888e2..183d52ce41 100644
--- a/external/docs/content/docs/git-multi-pack-index/2.38.2.html
+++ b/external/docs/content/docs/git-multi-pack-index/2.38.2.html
@@ -43,6 +43,7 @@
 - "/docs/git-multi-pack-index/2.45.2/index.html"
 - "/docs/git-multi-pack-index/2.46.0/index.html"
 - "/docs/git-multi-pack-index/2.46.1/index.html"
+- "/docs/git-multi-pack-index/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-mv/2.44.0.html b/external/docs/content/docs/git-mv/2.44.0.html
index 1c0e7e9793..71dfaadb0e 100644
--- a/external/docs/content/docs/git-mv/2.44.0.html
+++ b/external/docs/content/docs/git-mv/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-mv/2.45.2/index.html"
 - "/docs/git-mv/2.46.0/index.html"
 - "/docs/git-mv/2.46.1/index.html"
+- "/docs/git-mv/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-name-rev/2.43.0.html b/external/docs/content/docs/git-name-rev/2.43.0.html
index 9681822a55..2551a2b7e7 100644
--- a/external/docs/content/docs/git-name-rev/2.43.0.html
+++ b/external/docs/content/docs/git-name-rev/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-name-rev/2.45.2/index.html"
 - "/docs/git-name-rev/2.46.0/index.html"
 - "/docs/git-name-rev/2.46.1/index.html"
+- "/docs/git-name-rev/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-notes/2.44.0.html b/external/docs/content/docs/git-notes/2.44.0.html
index 8574c4d9f1..da0e559d53 100644
--- a/external/docs/content/docs/git-notes/2.44.0.html
+++ b/external/docs/content/docs/git-notes/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-notes/2.45.2/index.html"
 - "/docs/git-notes/2.46.0/index.html"
 - "/docs/git-notes/2.46.1/index.html"
+- "/docs/git-notes/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-p4/2.37.0.html b/external/docs/content/docs/git-p4/2.37.0.html
index bf0d7ec3f9..198029ed96 100644
--- a/external/docs/content/docs/git-p4/2.37.0.html
+++ b/external/docs/content/docs/git-p4/2.37.0.html
@@ -53,6 +53,7 @@
 - "/docs/git-p4/2.45.2/index.html"
 - "/docs/git-p4/2.46.0/index.html"
 - "/docs/git-p4/2.46.1/index.html"
+- "/docs/git-p4/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-pack-objects/2.43.0.html b/external/docs/content/docs/git-pack-objects/2.43.0.html
index 0409917625..92bf4f0557 100644
--- a/external/docs/content/docs/git-pack-objects/2.43.0.html
+++ b/external/docs/content/docs/git-pack-objects/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-pack-objects/2.45.2/index.html"
 - "/docs/git-pack-objects/2.46.0/index.html"
 - "/docs/git-pack-objects/2.46.1/index.html"
+- "/docs/git-pack-objects/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-pack-redundant/2.41.0.html b/external/docs/content/docs/git-pack-redundant/2.41.0.html
index b168aa519e..dd398345fa 100644
--- a/external/docs/content/docs/git-pack-redundant/2.41.0.html
+++ b/external/docs/content/docs/git-pack-redundant/2.41.0.html
@@ -29,6 +29,7 @@
 - "/docs/git-pack-redundant/2.45.2/index.html"
 - "/docs/git-pack-redundant/2.46.0/index.html"
 - "/docs/git-pack-redundant/2.46.1/index.html"
+- "/docs/git-pack-redundant/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-pack-refs/2.45.0.html b/external/docs/content/docs/git-pack-refs/2.45.0.html
index 602da7a4ca..d138094aaf 100644
--- a/external/docs/content/docs/git-pack-refs/2.45.0.html
+++ b/external/docs/content/docs/git-pack-refs/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-pack-refs/2.45.2/index.html"
 - "/docs/git-pack-refs/2.46.0/index.html"
 - "/docs/git-pack-refs/2.46.1/index.html"
+- "/docs/git-pack-refs/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-patch-id/2.39.0.html b/external/docs/content/docs/git-patch-id/2.39.0.html
index 9fee089109..3f96e53450 100644
--- a/external/docs/content/docs/git-patch-id/2.39.0.html
+++ b/external/docs/content/docs/git-patch-id/2.39.0.html
@@ -39,6 +39,7 @@
 - "/docs/git-patch-id/2.45.2/index.html"
 - "/docs/git-patch-id/2.46.0/index.html"
 - "/docs/git-patch-id/2.46.1/index.html"
+- "/docs/git-patch-id/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-prune-packed/2.43.0.html b/external/docs/content/docs/git-prune-packed/2.43.0.html
index efeb246acb..5a51b8349b 100644
--- a/external/docs/content/docs/git-prune-packed/2.43.0.html
+++ b/external/docs/content/docs/git-prune-packed/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-prune-packed/2.45.2/index.html"
 - "/docs/git-prune-packed/2.46.0/index.html"
 - "/docs/git-prune-packed/2.46.1/index.html"
+- "/docs/git-prune-packed/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-prune/2.43.0.html b/external/docs/content/docs/git-prune/2.43.0.html
index 13d785ece1..f3c75dbd24 100644
--- a/external/docs/content/docs/git-prune/2.43.0.html
+++ b/external/docs/content/docs/git-prune/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-prune/2.45.2/index.html"
 - "/docs/git-prune/2.46.0/index.html"
 - "/docs/git-prune/2.46.1/index.html"
+- "/docs/git-prune/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-pull.html b/external/docs/content/docs/git-pull.html
index fd1b006b5a..f22860114f 100644
--- a/external/docs/content/docs/git-pull.html
+++ b/external/docs/content/docs/git-pull.html
@@ -6,8 +6,8 @@
 subsection: manual
 title: Git - git-pull Documentation
 docname: git-pull
-version: 2.45.0
-latest-changes: 2.45.0
+version: 2.46.2
+latest-changes: 2.46.2
 aliases:
 - "/docs/git-pull/index.html"
 ---
@@ -394,8 +394,9 @@ <h3 id="_options_related_to_fetching"><a class="anchor" href="#_options_related_
 <dl>
 <dt class="hdlist1" id="Documentation/git-pull.txt---no-all"> <a class="anchor" href="#Documentation/git-pull.txt---no-all"></a>--[no-]all </dt>
 <dd>
-<p>Fetch all remotes. This overrides the configuration variable
-<code>fetch.all</code>.</p>
+<p>Fetch all remotes, except for the ones that has the
+<code>remote.&lt;name&gt;.skipFetchAll</code> configuration variable set.
+This overrides the configuration variable fetch.all`.</p>
 </dd>
 <dt class="hdlist1" id="Documentation/git-pull.txt--a"> <a class="anchor" href="#Documentation/git-pull.txt--a"></a>-a </dt>
 <dt class="hdlist1" id="Documentation/git-pull.txt---append"> <a class="anchor" href="#Documentation/git-pull.txt---append"></a>--append </dt>
diff --git a/external/docs/content/docs/git-pull/2.46.2.html b/external/docs/content/docs/git-pull/2.46.2.html
new file mode 100644
index 0000000000..b7b4829347
--- /dev/null
+++ b/external/docs/content/docs/git-pull/2.46.2.html
@@ -0,0 +1,1440 @@
+---
+### DO NOT EDIT! Generated by script/update-docs.rb
+
+category: manual
+section: documentation
+subsection: manual
+title: Git - git-pull Documentation
+docname: git-pull
+version: 2.46.2
+aliases:
+- "/docs/git-pull/2.46.2/index.html"
+---
+<div class="sect1">
+<h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>git-pull - Fetch from and integrate with another repository or a local branch</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_synopsis"><a class="anchor" href="#_synopsis"></a>SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="verseblock">
+<pre class="content"><em>git pull</em> [&lt;options&gt;] [&lt;repository&gt; [&lt;refspec&gt;&#8230;&#8203;]]</pre>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description"><a class="anchor" href="#_description"></a>DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Incorporates changes from a remote repository into the current branch.
+If the current branch is behind the remote, then by default it will
+fast-forward the current branch to match the remote.  If the current
+branch and the remote have diverged, the user needs to specify how to
+reconcile the divergent branches with <code>--rebase</code> or <code>--no-rebase</code> (or
+the corresponding configuration option in <code>pull.rebase</code>).</p>
+</div>
+<div class="paragraph">
+<p>More precisely, <code>git pull</code> runs <code>git fetch</code> with the given parameters
+and then depending on configuration options or command line flags,
+will call either <code>git rebase</code> or <code>git merge</code> to reconcile diverging
+branches.</p>
+</div>
+<div class="paragraph">
+<p>&lt;repository&gt; should be the name of a remote repository as
+passed to <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>.  &lt;refspec&gt; can name an
+arbitrary remote ref (for example, the name of a tag) or even
+a collection of refs with corresponding remote-tracking branches
+(e.g., refs/heads/*:refs/remotes/origin/*),
+but usually it is the name of a branch in the remote repository.</p>
+</div>
+<div class="paragraph">
+<p>Default values for &lt;repository&gt; and &lt;branch&gt; are read from the
+"remote" and "merge" configuration for the current branch
+as set by <a href='{{< relurl "docs/git-branch" >}}'>git-branch[1]</a> <code>--track</code>.</p>
+</div>
+<div class="paragraph">
+<p>Assume the following history exists and the current branch is
+"<code>master</code>":</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	  A---B---C master on origin
+	 /
+    D---E---F---G master
+	^
+	origin/master in your repository</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Then "<code>git pull</code>" will fetch and replay the changes from the remote
+<code>master</code> branch since it diverged from the local <code>master</code> (i.e., <code>E</code>)
+until its current commit (<code>C</code>) on top of <code>master</code> and record the
+result in a new commit along with the names of the two parent commits
+and a log message from the user describing the changes.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	  A---B---C origin/master
+	 /         \
+    D---E---F---G---H master</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>See <a href='{{< relurl "docs/git-merge" >}}'>git-merge[1]</a> for details, including how conflicts
+are presented and handled.</p>
+</div>
+<div class="paragraph">
+<p>In Git 1.7.0 or later, to cancel a conflicting merge, use
+<code>git reset --merge</code>.  <strong>Warning</strong>: In older versions of Git, running <em>git pull</em>
+with uncommitted changes is discouraged: while possible, it leaves you
+in a state that may be hard to back out of in the case of a conflict.</p>
+</div>
+<div class="paragraph">
+<p>If any of the remote changes overlap with local uncommitted changes,
+the merge will be automatically canceled and the work tree untouched.
+It is generally best to get any local changes in working order before
+pulling or stash them away with <a href='{{< relurl "docs/git-stash" >}}'>git-stash[1]</a>.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_options"><a class="anchor" href="#_options"></a>OPTIONS</h2>
+<div class="sectionbody">
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-pull.txt--q"> <a class="anchor" href="#Documentation/git-pull.txt--q"></a>-q </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---quiet"> <a class="anchor" href="#Documentation/git-pull.txt---quiet"></a>--quiet </dt>
+<dd>
+<p>This is passed to both underlying git-fetch to squelch reporting of
+during transfer, and underlying git-merge to squelch output during
+merging.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--v"> <a class="anchor" href="#Documentation/git-pull.txt--v"></a>-v </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---verbose"> <a class="anchor" href="#Documentation/git-pull.txt---verbose"></a>--verbose </dt>
+<dd>
+<p>Pass --verbose to git-fetch and git-merge.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-recurse-submodulesyeson-demandno"> <a class="anchor" href="#Documentation/git-pull.txt---no-recurse-submodulesyeson-demandno"></a>--[no-]recurse-submodules[=(yes|on-demand|no)] </dt>
+<dd>
+<p>This option controls if new commits of populated submodules should
+be fetched, and if the working trees of active submodules should be
+updated, too (see <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>, <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a> and
+<a href='{{< relurl "docs/gitmodules" >}}'>gitmodules[5]</a>).</p>
+<div class="paragraph">
+<p>If the checkout is done via rebase, local submodule commits are rebased as well.</p>
+</div>
+<div class="paragraph">
+<p>If the update is done via merge, the submodule conflicts are resolved and checked out.</p>
+</div>
+</dd>
+</dl>
+</div>
+<div class="sect2">
+<h3 id="_options_related_to_merging"><a class="anchor" href="#_options_related_to_merging"></a>Options related to merging</h3>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-pull.txt---commit"> <a class="anchor" href="#Documentation/git-pull.txt---commit"></a>--commit </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-commit"> <a class="anchor" href="#Documentation/git-pull.txt---no-commit"></a>--no-commit </dt>
+<dd>
+<p>Perform the merge and commit the result. This option can
+be used to override --no-commit.
+Only useful when merging.</p>
+<div class="paragraph">
+<p>With --no-commit perform the merge and stop just before creating
+a merge commit, to give the user a chance to inspect and further
+tweak the merge result before committing.</p>
+</div>
+<div class="paragraph">
+<p>Note that fast-forward updates do not create a merge commit and
+therefore there is no way to stop those merges with --no-commit.
+Thus, if you want to ensure your branch is not changed or updated
+by the merge command, use --no-ff with --no-commit.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---edit"> <a class="anchor" href="#Documentation/git-pull.txt---edit"></a>--edit </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt--e"> <a class="anchor" href="#Documentation/git-pull.txt--e"></a>-e </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-edit"> <a class="anchor" href="#Documentation/git-pull.txt---no-edit"></a>--no-edit </dt>
+<dd>
+<p>Invoke an editor before committing successful mechanical merge to
+further edit the auto-generated merge message, so that the user
+can explain and justify the merge. The <code>--no-edit</code> option can be
+used to accept the auto-generated message (this is generally
+discouraged).</p>
+<div class="paragraph">
+<p>Older scripts may depend on the historical behaviour of not allowing the
+user to edit the merge log message. They will see an editor opened when
+they run <code>git merge</code>. To make it easier to adjust such scripts to the
+updated behaviour, the environment variable <code>GIT_MERGE_AUTOEDIT</code> can be
+set to <code>no</code> at the beginning of them.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---cleanupltmodegt"> <a class="anchor" href="#Documentation/git-pull.txt---cleanupltmodegt"></a>--cleanup=&lt;mode&gt; </dt>
+<dd>
+<p>This option determines how the merge message will be cleaned up before
+committing. See <a href='{{< relurl "docs/git-commit" >}}'>git-commit[1]</a> for more details. In addition, if
+the <em>&lt;mode&gt;</em> is given a value of <code>scissors</code>, scissors will be appended
+to <code>MERGE_MSG</code> before being passed on to the commit machinery in the
+case of a merge conflict.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---ff-only"> <a class="anchor" href="#Documentation/git-pull.txt---ff-only"></a>--ff-only </dt>
+<dd>
+<p>Only update to the new history if there is no divergent local
+history.  This is the default when no method for reconciling
+divergent histories is provided (via the --rebase=* flags).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---ff"> <a class="anchor" href="#Documentation/git-pull.txt---ff"></a>--ff </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-ff"> <a class="anchor" href="#Documentation/git-pull.txt---no-ff"></a>--no-ff </dt>
+<dd>
+<p>When merging rather than rebasing, specifies how a merge is
+handled when the merged-in history is already a descendant of
+the current history.  If merging is requested, <code>--ff</code> is the
+default unless merging an annotated (and possibly signed) tag
+that is not stored in its natural place in the <code>refs/tags/</code>
+hierarchy, in which case <code>--no-ff</code> is assumed.</p>
+<div class="paragraph">
+<p>With <code>--ff</code>, when possible resolve the merge as a fast-forward (only
+update the branch pointer to match the merged branch; do not create a
+merge commit).  When not possible (when the merged-in history is not a
+descendant of the current history), create a merge commit.</p>
+</div>
+<div class="paragraph">
+<p>With <code>--no-ff</code>, create a merge commit in all cases, even when the merge
+could instead be resolved as a fast-forward.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--Sltkeyidgt"> <a class="anchor" href="#Documentation/git-pull.txt--Sltkeyidgt"></a>-S[&lt;keyid&gt;] </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---gpg-signltkeyidgt"> <a class="anchor" href="#Documentation/git-pull.txt---gpg-signltkeyidgt"></a>--gpg-sign[=&lt;keyid&gt;] </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-gpg-sign"> <a class="anchor" href="#Documentation/git-pull.txt---no-gpg-sign"></a>--no-gpg-sign </dt>
+<dd>
+<p>GPG-sign the resulting merge commit. The <code>keyid</code> argument is
+optional and defaults to the committer identity; if specified,
+it must be stuck to the option without a space. <code>--no-gpg-sign</code>
+is useful to countermand both <code>commit.gpgSign</code> configuration variable,
+and earlier <code>--gpg-sign</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---logltngt"> <a class="anchor" href="#Documentation/git-pull.txt---logltngt"></a>--log[=&lt;n&gt;] </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-log"> <a class="anchor" href="#Documentation/git-pull.txt---no-log"></a>--no-log </dt>
+<dd>
+<p>In addition to branch names, populate the log message with
+one-line descriptions from at most &lt;n&gt; actual commits that are being
+merged. See also <a href='{{< relurl "docs/git-fmt-merge-msg" >}}'>git-fmt-merge-msg[1]</a>.
+Only useful when merging.</p>
+<div class="paragraph">
+<p>With --no-log do not list one-line descriptions from the
+actual commits being merged.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---signoff"> <a class="anchor" href="#Documentation/git-pull.txt---signoff"></a>--signoff </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-signoff"> <a class="anchor" href="#Documentation/git-pull.txt---no-signoff"></a>--no-signoff </dt>
+<dd>
+<p>Add a <code>Signed-off-by</code> trailer by the committer at the end of the commit
+log message.  The meaning of a signoff depends on the project
+to which you&#8217;re committing.  For example, it may certify that
+the committer has the rights to submit the work under the
+project&#8217;s license or agrees to some contributor representation,
+such as a Developer Certificate of Origin.
+(See <a href="https://developercertificate.org" class="bare">https://developercertificate.org</a> for the one used by the
+Linux kernel and Git projects.)  Consult the documentation or
+leadership of the project to which you&#8217;re contributing to
+understand how the signoffs are used in that project.</p>
+<div class="paragraph">
+<p>The --no-signoff option can be used to countermand an earlier --signoff
+option on the command line.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---stat"> <a class="anchor" href="#Documentation/git-pull.txt---stat"></a>--stat </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt--n"> <a class="anchor" href="#Documentation/git-pull.txt--n"></a>-n </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-stat"> <a class="anchor" href="#Documentation/git-pull.txt---no-stat"></a>--no-stat </dt>
+<dd>
+<p>Show a diffstat at the end of the merge. The diffstat is also
+controlled by the configuration option merge.stat.</p>
+<div class="paragraph">
+<p>With -n or --no-stat do not show a diffstat at the end of the
+merge.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---squash"> <a class="anchor" href="#Documentation/git-pull.txt---squash"></a>--squash </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-squash"> <a class="anchor" href="#Documentation/git-pull.txt---no-squash"></a>--no-squash </dt>
+<dd>
+<p>Produce the working tree and index state as if a real merge
+happened (except for the merge information), but do not actually
+make a commit, move the <code>HEAD</code>, or record <code>$GIT_DIR/MERGE_HEAD</code>
+(to cause the next <code>git commit</code> command to create a merge
+commit).  This allows you to create a single commit on top of
+the current branch whose effect is the same as merging another
+branch (or more in case of an octopus).</p>
+<div class="paragraph">
+<p>With --no-squash perform the merge and commit the result. This
+option can be used to override --squash.</p>
+</div>
+<div class="paragraph">
+<p>With --squash, --commit is not allowed, and will fail.</p>
+</div>
+<div class="paragraph">
+<p>Only useful when merging.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-verify"> <a class="anchor" href="#Documentation/git-pull.txt---no-verify"></a>--[no-]verify </dt>
+<dd>
+<p>By default, the pre-merge and commit-msg hooks are run.
+When <code>--no-verify</code> is given, these are bypassed.
+See also <a href='{{< relurl "docs/githooks" >}}'>githooks[5]</a>.
+Only useful when merging.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--sltstrategygt"> <a class="anchor" href="#Documentation/git-pull.txt--sltstrategygt"></a>-s &lt;strategy&gt; </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---strategyltstrategygt"> <a class="anchor" href="#Documentation/git-pull.txt---strategyltstrategygt"></a>--strategy=&lt;strategy&gt; </dt>
+<dd>
+<p>Use the given merge strategy; can be supplied more than
+once to specify them in the order they should be tried.
+If there is no <code>-s</code> option, a built-in list of strategies
+is used instead (<code>ort</code> when merging a single head,
+<code>octopus</code> otherwise).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--Xltoptiongt"> <a class="anchor" href="#Documentation/git-pull.txt--Xltoptiongt"></a>-X &lt;option&gt; </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---strategy-optionltoptiongt"> <a class="anchor" href="#Documentation/git-pull.txt---strategy-optionltoptiongt"></a>--strategy-option=&lt;option&gt; </dt>
+<dd>
+<p>Pass merge strategy specific option through to the merge
+strategy.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---verify-signatures"> <a class="anchor" href="#Documentation/git-pull.txt---verify-signatures"></a>--verify-signatures </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-verify-signatures"> <a class="anchor" href="#Documentation/git-pull.txt---no-verify-signatures"></a>--no-verify-signatures </dt>
+<dd>
+<p>Verify that the tip commit of the side branch being merged is
+signed with a valid key, i.e. a key that has a valid uid: in the
+default trust model, this means the signing key has been signed by
+a trusted key.  If the tip commit of the side branch is not signed
+with a valid key, the merge is aborted.</p>
+<div class="paragraph">
+<p>Only useful when merging.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---summary"> <a class="anchor" href="#Documentation/git-pull.txt---summary"></a>--summary </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-summary"> <a class="anchor" href="#Documentation/git-pull.txt---no-summary"></a>--no-summary </dt>
+<dd>
+<p>Synonyms to --stat and --no-stat; these are deprecated and will be
+removed in the future.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---autostash"> <a class="anchor" href="#Documentation/git-pull.txt---autostash"></a>--autostash </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-autostash"> <a class="anchor" href="#Documentation/git-pull.txt---no-autostash"></a>--no-autostash </dt>
+<dd>
+<p>Automatically create a temporary stash entry before the operation
+begins, record it in the ref <code>MERGE_AUTOSTASH</code>
+and apply it after the operation ends.  This means
+that you can run the operation on a dirty worktree.  However, use
+with care: the final stash application after a successful
+merge might result in non-trivial conflicts.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---allow-unrelated-histories"> <a class="anchor" href="#Documentation/git-pull.txt---allow-unrelated-histories"></a>--allow-unrelated-histories </dt>
+<dd>
+<p>By default, <code>git merge</code> command refuses to merge histories
+that do not share a common ancestor.  This option can be
+used to override this safety when merging histories of two
+projects that started their lives independently. As that is
+a very rare occasion, no configuration variable to enable
+this by default exists and will not be added.</p>
+<div class="paragraph">
+<p>Only useful when merging.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--r"> <a class="anchor" href="#Documentation/git-pull.txt--r"></a>-r </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---rebasefalsetruemergesinteractive"> <a class="anchor" href="#Documentation/git-pull.txt---rebasefalsetruemergesinteractive"></a>--rebase[=(false|true|merges|interactive)] </dt>
+<dd>
+<p>When true, rebase the current branch on top of the upstream
+branch after fetching. If there is a remote-tracking branch
+corresponding to the upstream branch and the upstream branch
+was rebased since last fetched, the rebase uses that information
+to avoid rebasing non-local changes.</p>
+<div class="paragraph">
+<p>When set to <code>merges</code>, rebase using <code>git rebase --rebase-merges</code> so that
+the local merge commits are included in the rebase (see
+<a href='{{< relurl "docs/git-rebase" >}}'>git-rebase[1]</a> for details).</p>
+</div>
+<div class="paragraph">
+<p>When false, merge the upstream branch into the current branch.</p>
+</div>
+<div class="paragraph">
+<p>When <code>interactive</code>, enable the interactive mode of rebase.</p>
+</div>
+<div class="paragraph">
+<p>See <code>pull.rebase</code>, <code>branch.&lt;name&gt;.rebase</code> and <code>branch.autoSetupRebase</code> in
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a> if you want to make <code>git pull</code> always use
+<code>--rebase</code> instead of merging.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+This is a potentially <em>dangerous</em> mode of operation.
+It rewrites history, which does not bode well when you
+published that history already.  Do <strong>not</strong> use this option
+unless you have read <a href='{{< relurl "docs/git-rebase" >}}'>git-rebase[1]</a> carefully.
+</td>
+</tr>
+</table>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-rebase"> <a class="anchor" href="#Documentation/git-pull.txt---no-rebase"></a>--no-rebase </dt>
+<dd>
+<p>This is shorthand for --rebase=false.</p>
+</dd>
+</dl>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_options_related_to_fetching"><a class="anchor" href="#_options_related_to_fetching"></a>Options related to fetching</h3>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-all"> <a class="anchor" href="#Documentation/git-pull.txt---no-all"></a>--[no-]all </dt>
+<dd>
+<p>Fetch all remotes, except for the ones that has the
+<code>remote.&lt;name&gt;.skipFetchAll</code> configuration variable set.
+This overrides the configuration variable fetch.all`.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--a"> <a class="anchor" href="#Documentation/git-pull.txt--a"></a>-a </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---append"> <a class="anchor" href="#Documentation/git-pull.txt---append"></a>--append </dt>
+<dd>
+<p>Append ref names and object names of fetched refs to the
+existing contents of <code>.git/FETCH_HEAD</code>.  Without this
+option old data in <code>.git/FETCH_HEAD</code> will be overwritten.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---atomic"> <a class="anchor" href="#Documentation/git-pull.txt---atomic"></a>--atomic </dt>
+<dd>
+<p>Use an atomic transaction to update local refs. Either all refs are
+updated, or on error, no refs are updated.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---depthltdepthgt"> <a class="anchor" href="#Documentation/git-pull.txt---depthltdepthgt"></a>--depth=&lt;depth&gt; </dt>
+<dd>
+<p>Limit fetching to the specified number of commits from the tip of
+each remote branch history. If fetching to a <em>shallow</em> repository
+created by <code>git clone</code> with <code>--depth=&lt;depth&gt;</code> option (see
+<a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a>), deepen or shorten the history to the specified
+number of commits. Tags for the deepened commits are not fetched.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---deepenltdepthgt"> <a class="anchor" href="#Documentation/git-pull.txt---deepenltdepthgt"></a>--deepen=&lt;depth&gt; </dt>
+<dd>
+<p>Similar to --depth, except it specifies the number of commits
+from the current shallow boundary instead of from the tip of
+each remote branch history.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---shallow-sinceltdategt"> <a class="anchor" href="#Documentation/git-pull.txt---shallow-sinceltdategt"></a>--shallow-since=&lt;date&gt; </dt>
+<dd>
+<p>Deepen or shorten the history of a shallow repository to
+include all reachable commits after &lt;date&gt;.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---shallow-excludeltrevisiongt"> <a class="anchor" href="#Documentation/git-pull.txt---shallow-excludeltrevisiongt"></a>--shallow-exclude=&lt;revision&gt; </dt>
+<dd>
+<p>Deepen or shorten the history of a shallow repository to
+exclude commits reachable from a specified remote branch or tag.
+This option can be specified multiple times.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---unshallow"> <a class="anchor" href="#Documentation/git-pull.txt---unshallow"></a>--unshallow </dt>
+<dd>
+<p>If the source repository is complete, convert a shallow
+repository to a complete one, removing all the limitations
+imposed by shallow repositories.</p>
+<div class="paragraph">
+<p>If the source repository is shallow, fetch as much as possible so that
+the current repository has the same history as the source repository.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---update-shallow"> <a class="anchor" href="#Documentation/git-pull.txt---update-shallow"></a>--update-shallow </dt>
+<dd>
+<p>By default when fetching from a shallow repository,
+<code>git fetch</code> refuses refs that require updating
+.git/shallow. This option updates .git/shallow and accepts such
+refs.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---negotiation-tipltcommitglobgt"> <a class="anchor" href="#Documentation/git-pull.txt---negotiation-tipltcommitglobgt"></a>--negotiation-tip=&lt;commit|glob&gt; </dt>
+<dd>
+<p>By default, Git will report, to the server, commits reachable
+from all local refs to find common commits in an attempt to
+reduce the size of the to-be-received packfile. If specified,
+Git will only report commits reachable from the given tips.
+This is useful to speed up fetches when the user knows which
+local ref is likely to have commits in common with the
+upstream ref being fetched.</p>
+<div class="paragraph">
+<p>This option may be specified more than once; if so, Git will report
+commits reachable from any of the given commits.</p>
+</div>
+<div class="paragraph">
+<p>The argument to this option may be a glob on ref names, a ref, or the (possibly
+abbreviated) SHA-1 of a commit. Specifying a glob is equivalent to specifying
+this option multiple times, one for each matching ref name.</p>
+</div>
+<div class="paragraph">
+<p>See also the <code>fetch.negotiationAlgorithm</code> and <code>push.negotiate</code>
+configuration variables documented in <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>, and the
+<code>--negotiate-only</code> option below.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---negotiate-only"> <a class="anchor" href="#Documentation/git-pull.txt---negotiate-only"></a>--negotiate-only </dt>
+<dd>
+<p>Do not fetch anything from the server, and instead print the
+ancestors of the provided <code>--negotiation-tip=*</code> arguments,
+which we have in common with the server.</p>
+<div class="paragraph">
+<p>This is incompatible with <code>--recurse-submodules=[yes|on-demand]</code>.
+Internally this is used to implement the <code>push.negotiate</code> option, see
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---dry-run"> <a class="anchor" href="#Documentation/git-pull.txt---dry-run"></a>--dry-run </dt>
+<dd>
+<p>Show what would be done, without making any changes.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---porcelain"> <a class="anchor" href="#Documentation/git-pull.txt---porcelain"></a>--porcelain </dt>
+<dd>
+<p>Print the output to standard output in an easy-to-parse format for
+scripts. See section OUTPUT in <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a> for details.</p>
+<div class="paragraph">
+<p>This is incompatible with <code>--recurse-submodules=[yes|on-demand]</code> and takes
+precedence over the <code>fetch.output</code> config option.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--f"> <a class="anchor" href="#Documentation/git-pull.txt--f"></a>-f </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---force"> <a class="anchor" href="#Documentation/git-pull.txt---force"></a>--force </dt>
+<dd>
+<p>When <em>git fetch</em> is used with <code>&lt;src&gt;:&lt;dst&gt;</code> refspec, it may
+refuse to update the local branch as discussed
+in the <code>&lt;refspec&gt;</code> part of the <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>
+documentation.
+This option overrides that check.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--k"> <a class="anchor" href="#Documentation/git-pull.txt--k"></a>-k </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---keep"> <a class="anchor" href="#Documentation/git-pull.txt---keep"></a>--keep </dt>
+<dd>
+<p>Keep downloaded pack.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---prefetch"> <a class="anchor" href="#Documentation/git-pull.txt---prefetch"></a>--prefetch </dt>
+<dd>
+<p>Modify the configured refspec to place all refs into the
+<code>refs/prefetch/</code> namespace. See the <code>prefetch</code> task in
+<a href='{{< relurl "docs/git-maintenance" >}}'>git-maintenance[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--p"> <a class="anchor" href="#Documentation/git-pull.txt--p"></a>-p </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---prune"> <a class="anchor" href="#Documentation/git-pull.txt---prune"></a>--prune </dt>
+<dd>
+<p>Before fetching, remove any remote-tracking references that no
+longer exist on the remote.  Tags are not subject to pruning
+if they are fetched only because of the default tag
+auto-following or due to a --tags option.  However, if tags
+are fetched due to an explicit refspec (either on the command
+line or in the remote configuration, for example if the remote
+was cloned with the --mirror option), then they are also
+subject to pruning. Supplying <code>--prune-tags</code> is a shorthand for
+providing the tag refspec.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-tags"> <a class="anchor" href="#Documentation/git-pull.txt---no-tags"></a>--no-tags </dt>
+<dd>
+<p>By default, tags that point at objects that are downloaded
+from the remote repository are fetched and stored locally.
+This option disables this automatic tag following. The default
+behavior for a remote may be specified with the remote.&lt;name&gt;.tagOpt
+setting. See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---refmapltrefspecgt"> <a class="anchor" href="#Documentation/git-pull.txt---refmapltrefspecgt"></a>--refmap=&lt;refspec&gt; </dt>
+<dd>
+<p>When fetching refs listed on the command line, use the
+specified refspec (can be given more than once) to map the
+refs to remote-tracking branches, instead of the values of
+<code>remote.*.fetch</code> configuration variables for the remote
+repository.  Providing an empty <code>&lt;refspec&gt;</code> to the
+<code>--refmap</code> option causes Git to ignore the configured
+refspecs and rely entirely on the refspecs supplied as
+command-line arguments. See section on "Configured Remote-tracking
+Branches" for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--t"> <a class="anchor" href="#Documentation/git-pull.txt--t"></a>-t </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---tags"> <a class="anchor" href="#Documentation/git-pull.txt---tags"></a>--tags </dt>
+<dd>
+<p>Fetch all tags from the remote (i.e., fetch remote tags
+<code>refs/tags/*</code> into local tags with the same name), in addition
+to whatever else would otherwise be fetched.  Using this
+option alone does not subject tags to pruning, even if --prune
+is used (though tags may be pruned anyway if they are also the
+destination of an explicit refspec; see <code>--prune</code>).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--j"> <a class="anchor" href="#Documentation/git-pull.txt--j"></a>-j </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---jobsltngt"> <a class="anchor" href="#Documentation/git-pull.txt---jobsltngt"></a>--jobs=&lt;n&gt; </dt>
+<dd>
+<p>Number of parallel children to be used for all forms of fetching.</p>
+<div class="paragraph">
+<p>If the <code>--multiple</code> option was specified, the different remotes will be fetched
+in parallel. If multiple submodules are fetched, they will be fetched in
+parallel. To control them independently, use the config settings
+<code>fetch.parallel</code> and <code>submodule.fetchJobs</code> (see <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>).</p>
+</div>
+<div class="paragraph">
+<p>Typically, parallel recursive and multi-remote fetches will be faster. By
+default fetches are performed sequentially, not in parallel.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---set-upstream"> <a class="anchor" href="#Documentation/git-pull.txt---set-upstream"></a>--set-upstream </dt>
+<dd>
+<p>If the remote is fetched successfully, add upstream
+(tracking) reference, used by argument-less
+<a href='{{< relurl "docs/git-pull" >}}'>git-pull[1]</a> and other commands. For more information,
+see <code>branch.&lt;name&gt;.merge</code> and <code>branch.&lt;name&gt;.remote</code> in
+<a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---upload-packltupload-packgt"> <a class="anchor" href="#Documentation/git-pull.txt---upload-packltupload-packgt"></a>--upload-pack &lt;upload-pack&gt; </dt>
+<dd>
+<p>When given, and the repository to fetch from is handled
+by <em>git fetch-pack</em>, <code>--exec=&lt;upload-pack&gt;</code> is passed to
+the command to specify non-default path for the command
+run on the other end.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---progress"> <a class="anchor" href="#Documentation/git-pull.txt---progress"></a>--progress </dt>
+<dd>
+<p>Progress status is reported on the standard error stream
+by default when it is attached to a terminal, unless -q
+is specified. This flag forces progress status even if the
+standard error stream is not directed to a terminal.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--oltoptiongt"> <a class="anchor" href="#Documentation/git-pull.txt--oltoptiongt"></a>-o &lt;option&gt; </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---server-optionltoptiongt"> <a class="anchor" href="#Documentation/git-pull.txt---server-optionltoptiongt"></a>--server-option=&lt;option&gt; </dt>
+<dd>
+<p>Transmit the given string to the server when communicating using
+protocol version 2.  The given string must not contain a NUL or LF
+character.  The server&#8217;s handling of server options, including
+unknown ones, is server-specific.
+When multiple <code>--server-option=&lt;option&gt;</code> are given, they are all
+sent to the other side in the order listed on the command line.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---show-forced-updates"> <a class="anchor" href="#Documentation/git-pull.txt---show-forced-updates"></a>--show-forced-updates </dt>
+<dd>
+<p>By default, git checks if a branch is force-updated during
+fetch. This can be disabled through fetch.showForcedUpdates, but
+the --show-forced-updates option guarantees this check occurs.
+See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt---no-show-forced-updates"> <a class="anchor" href="#Documentation/git-pull.txt---no-show-forced-updates"></a>--no-show-forced-updates </dt>
+<dd>
+<p>By default, git checks if a branch is force-updated during
+fetch. Pass --no-show-forced-updates or set fetch.showForcedUpdates
+to false to skip this check for performance reasons. If used during
+<em>git-pull</em> the --ff-only option will still check for forced updates
+before attempting a fast-forward update. See <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--4"> <a class="anchor" href="#Documentation/git-pull.txt--4"></a>-4 </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---ipv4"> <a class="anchor" href="#Documentation/git-pull.txt---ipv4"></a>--ipv4 </dt>
+<dd>
+<p>Use IPv4 addresses only, ignoring IPv6 addresses.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt--6"> <a class="anchor" href="#Documentation/git-pull.txt--6"></a>-6 </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt---ipv6"> <a class="anchor" href="#Documentation/git-pull.txt---ipv6"></a>--ipv6 </dt>
+<dd>
+<p>Use IPv6 addresses only, ignoring IPv4 addresses.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-ltrepositorygt"> <a class="anchor" href="#Documentation/git-pull.txt-ltrepositorygt"></a>&lt;repository&gt; </dt>
+<dd>
+<p>The "remote" repository that is the source of a fetch
+or pull operation.  This parameter can be either a URL
+(see the section <a href="#URLS">GIT URLS</a> below) or the name
+of a remote (see the section <a href="#REMOTES">REMOTES</a> below).</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-ltrefspecgt"> <a class="anchor" href="#Documentation/git-pull.txt-ltrefspecgt"></a>&lt;refspec&gt; </dt>
+<dd>
+<p>Specifies which refs to fetch and which local refs to update.
+When no &lt;refspec&gt;s appear on the command line, the refs to fetch
+are read from <code>remote.&lt;repository&gt;.fetch</code> variables instead
+(see the section "CONFIGURED REMOTE-TRACKING BRANCHES"
+in <a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>).</p>
+<div class="paragraph">
+<p>The format of a &lt;refspec&gt; parameter is an optional plus
+<code>+</code>, followed by the source &lt;src&gt;, followed
+by a colon <code>:</code>, followed by the destination ref &lt;dst&gt;.
+The colon can be omitted when &lt;dst&gt; is empty.  &lt;src&gt; is
+typically a ref, but it can also be a fully spelled hex object
+name.</p>
+</div>
+<div class="paragraph">
+<p>A &lt;refspec&gt; may contain a <code>*</code> in its &lt;src&gt; to indicate a simple pattern
+match. Such a refspec functions like a glob that matches any ref with the
+same prefix. A pattern &lt;refspec&gt; must have a <code>*</code> in both the &lt;src&gt; and
+&lt;dst&gt;. It will map refs to the destination by replacing the <code>*</code> with the
+contents matched from the source.</p>
+</div>
+<div class="paragraph">
+<p>If a refspec is prefixed by <code>^</code>, it will be interpreted as a negative
+refspec. Rather than specifying which refs to fetch or which local refs to
+update, such a refspec will instead specify refs to exclude. A ref will be
+considered to match if it matches at least one positive refspec, and does
+not match any negative refspec. Negative refspecs can be useful to restrict
+the scope of a pattern refspec so that it will not include specific refs.
+Negative refspecs can themselves be pattern refspecs. However, they may only
+contain a &lt;src&gt; and do not specify a &lt;dst&gt;. Fully spelled out hex object
+names are also not supported.</p>
+</div>
+<div class="paragraph">
+<p><code>tag &lt;tag&gt;</code> means the same as <code>refs/tags/&lt;tag&gt;:refs/tags/&lt;tag&gt;</code>;
+it requests fetching everything up to the given tag.</p>
+</div>
+<div class="paragraph">
+<p>The remote ref that matches &lt;src&gt;
+is fetched, and if &lt;dst&gt; is not an empty string, an attempt
+is made to update the local ref that matches it.</p>
+</div>
+<div class="paragraph">
+<p>Whether that update is allowed without <code>--force</code> depends on the ref
+namespace it&#8217;s being fetched to, the type of object being fetched, and
+whether the update is considered to be a fast-forward. Generally, the
+same rules apply for fetching as when pushing, see the <code>&lt;refspec&gt;...</code>
+section of <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a> for what those are. Exceptions to those
+rules particular to <em>git fetch</em> are noted below.</p>
+</div>
+<div class="paragraph">
+<p>Until Git version 2.20, and unlike when pushing with
+<a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>, any updates to <code>refs/tags/*</code> would be accepted
+without <code>+</code> in the refspec (or <code>--force</code>). When fetching, we promiscuously
+considered all tag updates from a remote to be forced fetches.  Since
+Git version 2.20, fetching to update <code>refs/tags/*</code> works the same way
+as when pushing. I.e. any updates will be rejected without <code>+</code> in the
+refspec (or <code>--force</code>).</p>
+</div>
+<div class="paragraph">
+<p>Unlike when pushing with <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>, any updates outside of
+<code>refs/{tags,heads}/*</code> will be accepted without <code>+</code> in the refspec (or
+<code>--force</code>), whether that&#8217;s swapping e.g. a tree object for a blob, or
+a commit for another commit that doesn&#8217;t have the previous commit as
+an ancestor etc.</p>
+</div>
+<div class="paragraph">
+<p>Unlike when pushing with <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>, there is no
+configuration which&#8217;ll amend these rules, and nothing like a
+<code>pre-fetch</code> hook analogous to the <code>pre-receive</code> hook.</p>
+</div>
+<div class="paragraph">
+<p>As with pushing with <a href='{{< relurl "docs/git-push" >}}'>git-push[1]</a>, all of the rules described
+above about what&#8217;s not allowed as an update can be overridden by
+adding an optional leading <code>+</code> to a refspec (or using the <code>--force</code>
+command line option). The only exception to this is that no amount of
+forcing will make the <code>refs/heads/*</code> namespace accept a non-commit
+object.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+When the remote branch you want to fetch is known to
+be rewound and rebased regularly, it is expected that
+its new tip will not be a descendant of its previous tip
+(as stored in your remote-tracking branch the last time
+you fetched).  You would want
+to use the <code>+</code> sign to indicate non-fast-forward updates
+will be needed for such branches.  There is no way to
+determine or declare that a branch will be made available
+in a repository with this behavior; the pulling user simply
+must know this is the expected usage pattern for a branch.
+</td>
+</tr>
+</table>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+There is a difference between listing multiple &lt;refspec&gt;
+directly on <em>git pull</em> command line and having multiple
+<code>remote.&lt;repository&gt;.fetch</code> entries in your configuration
+for a &lt;repository&gt; and running a
+<em>git pull</em> command without any explicit &lt;refspec&gt; parameters.
+&lt;refspec&gt;s listed explicitly on the command line are always
+merged into the current branch after fetching.  In other words,
+if you list more than one remote ref, <em>git pull</em> will create
+an Octopus merge.  On the other hand, if you do not list any
+explicit &lt;refspec&gt; parameter on the command line, <em>git pull</em>
+will fetch all the &lt;refspec&gt;s it finds in the
+<code>remote.&lt;repository&gt;.fetch</code> configuration and merge
+only the first &lt;refspec&gt; found into the current branch.
+This is because making an
+Octopus from remote refs is rarely done, while keeping track
+of multiple remote heads in one-go by fetching more than one
+is often useful.
+</td>
+</tr>
+</table>
+</div>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_git_urls"><a class="anchor" href="#_git_urls"></a>GIT URLS<a id="URLS"></a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>In general, URLs contain information about the transport protocol, the
+address of the remote server, and the path to the repository.
+Depending on the transport protocol, some of this information may be
+absent.</p>
+</div>
+<div class="paragraph">
+<p>Git supports ssh, git, http, and https protocols (in addition, ftp
+and ftps can be used for fetching, but this is inefficient and
+deprecated; do not use them).</p>
+</div>
+<div class="paragraph">
+<p>The native transport (i.e. git:// URL) does no authentication and
+should be used with caution on unsecured networks.</p>
+</div>
+<div class="paragraph">
+<p>The following syntaxes may be used with them:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>ssh://</code>[<em>&lt;user&gt;</em><code>@</code>]<em>&lt;host&gt;</em>[<code>:</code><em>&lt;port&gt;</em>]<code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+<li>
+<p><code>git://</code><em>&lt;host&gt;</em>[:<em>&lt;port&gt;</em>]<code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+<li>
+<p><code>http</code>[<code>s</code>]<code>://</code><em>&lt;host&gt;</em>[<code>:</code><em>&lt;port&gt;</em>]<code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+<li>
+<p><code>ftp</code>[<code>s</code>]<code>://</code><em>&lt;host&gt;</em>[<code>:</code><em>&lt;port&gt;</em>]<code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>An alternative scp-like syntax may also be used with the ssh protocol:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>[<em>&lt;user&gt;</em><code>@</code>]<em>&lt;host&gt;</em><code>:/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>This syntax is only recognized if there are no slashes before the
+first colon. This helps differentiate a local path that contains a
+colon. For example the local path <code>foo:bar</code> could be specified as an
+absolute path or <code>./foo:bar</code> to avoid being misinterpreted as an ssh
+url.</p>
+</div>
+<div class="paragraph">
+<p>The ssh and git protocols additionally support <code>~</code><em>&lt;username&gt;</em> expansion:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>ssh://</code>[<em>&lt;user&gt;</em><code>@</code>]<em>&lt;host&gt;</em>[<code>:</code><em>&lt;port&gt;</em>]<code>/~</code><em>&lt;user&gt;</em><code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+<li>
+<p><code>git://</code><em>&lt;host&gt;</em>[<code>:</code><em>&lt;port&gt;</em>]<code>/~</code><em>&lt;user&gt;</em><code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+<li>
+<p>[<em>&lt;user&gt;</em><code>@</code>]<em>&lt;host&gt;</em><code>:~</code><em>&lt;user&gt;</em><code>/</code><em>&lt;path-to-git-repo&gt;</em></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>For local repositories, also supported by Git natively, the following
+syntaxes may be used:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>/path/to/repo.git/</code></p>
+</li>
+<li>
+<p><code><a href="file:///path/to/repo.git/" class="bare">file:///path/to/repo.git/</a></code></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>These two syntaxes are mostly equivalent, except when cloning, when
+the former implies <code>--local</code> option. See <a href='{{< relurl "docs/git-clone" >}}'>git-clone[1]</a> for
+details.</p>
+</div>
+<div class="paragraph">
+<p><code>git clone</code>, <code>git fetch</code> and <code>git pull</code>, but not <code>git push</code>, will also
+accept a suitable bundle file. See <a href='{{< relurl "docs/git-bundle" >}}'>git-bundle[1]</a>.</p>
+</div>
+<div class="paragraph">
+<p>When Git doesn&#8217;t know how to handle a certain transport protocol, it
+attempts to use the <code>remote-</code><em>&lt;transport&gt;</em> remote helper, if one
+exists. To explicitly request a remote helper, the following syntax
+may be used:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><em>&lt;transport&gt;</em>::<em>&lt;address&gt;</em></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>where <em>&lt;address&gt;</em> may be a path, a server and path, or an arbitrary
+URL-like string recognized by the specific remote helper being
+invoked. See <a href='{{< relurl "docs/gitremote-helpers" >}}'>gitremote-helpers[7]</a> for details.</p>
+</div>
+<div class="paragraph">
+<p>If there are a large number of similarly-named remote repositories and
+you want to use a different format for them (such that the URLs you
+use will be rewritten into URLs that work), you can create a
+configuration section of the form:</p>
+</div>
+<div class="verseblock">
+<pre class="content">	[url "<em>&lt;actual-url-base&gt;</em>"]
+		insteadOf = <em>&lt;other-url-base&gt;</em></pre>
+</div>
+<div class="paragraph">
+<p>For example, with this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	[url "git://git.host.xz/"]
+		insteadOf = host.xz:/path/to/
+		insteadOf = work:</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
+rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</p>
+</div>
+<div class="paragraph">
+<p>If you want to rewrite URLs for push only, you can create a
+configuration section of the form:</p>
+</div>
+<div class="verseblock">
+<pre class="content">	[url "<em>&lt;actual-url-base&gt;</em>"]
+		pushInsteadOf = <em>&lt;other-url-base&gt;</em></pre>
+</div>
+<div class="paragraph">
+<p>For example, with this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	[url "ssh://example.org/"]
+		pushInsteadOf = git://example.org/</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>a URL like "git://example.org/path/to/repo.git" will be rewritten to
+"ssh://example.org/path/to/repo.git" for pushes, but pulls will still
+use the original URL.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_remotes"><a class="anchor" href="#_remotes"></a>REMOTES<a id="REMOTES"></a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The name of one of the following can be used instead
+of a URL as <code>&lt;repository&gt;</code> argument:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>a remote in the Git configuration file: <code>$GIT_DIR/config</code>,</p>
+</li>
+<li>
+<p>a file in the <code>$GIT_DIR/remotes</code> directory, or</p>
+</li>
+<li>
+<p>a file in the <code>$GIT_DIR/branches</code> directory.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>All of these also allow you to omit the refspec from the command line
+because they each contain a refspec which git will use by default.</p>
+</div>
+<div class="sect2">
+<h3 id="_named_remote_in_configuration_file"><a class="anchor" href="#_named_remote_in_configuration_file"></a>Named remote in configuration file</h3>
+<div class="paragraph">
+<p>You can choose to provide the name of a remote which you had previously
+configured using <a href='{{< relurl "docs/git-remote" >}}'>git-remote[1]</a>, <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a>
+or even by a manual edit to the <code>$GIT_DIR/config</code> file.  The URL of
+this remote will be used to access the repository.  The refspec
+of this remote will be used by default when you do
+not provide a refspec on the command line.  The entry in the
+config file would appear like this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	[remote "&lt;name&gt;"]
+		url = &lt;URL&gt;
+		pushurl = &lt;pushurl&gt;
+		push = &lt;refspec&gt;
+		fetch = &lt;refspec&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The <code>&lt;pushurl&gt;</code> is used for pushes only. It is optional and defaults
+to <code>&lt;URL&gt;</code>. Pushing to a remote affects all defined pushurls or all
+defined urls if no pushurls are defined. Fetch, however, will only
+fetch from the first defined url if multiple urls are defined.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_named_file_in_git_dirremotes"><a class="anchor" href="#_named_file_in_git_dirremotes"></a>Named file in <code>$GIT_DIR/remotes</code></h3>
+<div class="paragraph">
+<p>You can choose to provide the name of a
+file in <code>$GIT_DIR/remotes</code>.  The URL
+in this file will be used to access the repository.  The refspec
+in this file will be used as default when you do not
+provide a refspec on the command line.  This file should have the
+following format:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	URL: one of the above URL formats
+	Push: &lt;refspec&gt;
+	Pull: &lt;refspec&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p><code>Push:</code> lines are used by <em>git push</em> and
+<code>Pull:</code> lines are used by <em>git pull</em> and <em>git fetch</em>.
+Multiple <code>Push:</code> and <code>Pull:</code> lines may
+be specified for additional branch mappings.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_named_file_in_git_dirbranches"><a class="anchor" href="#_named_file_in_git_dirbranches"></a>Named file in <code>$GIT_DIR/branches</code></h3>
+<div class="paragraph">
+<p>You can choose to provide the name of a
+file in <code>$GIT_DIR/branches</code>.
+The URL in this file will be used to access the repository.
+This file should have the following format:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	&lt;URL&gt;#&lt;head&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p><code>&lt;URL&gt;</code> is required; <code>#&lt;head&gt;</code> is optional.</p>
+</div>
+<div class="paragraph">
+<p>Depending on the operation, git will use one of the following
+refspecs, if you don&#8217;t provide one on the command line.
+<code>&lt;branch&gt;</code> is the name of this file in <code>$GIT_DIR/branches</code> and
+<code>&lt;head&gt;</code> defaults to <code>master</code>.</p>
+</div>
+<div class="paragraph">
+<p>git fetch uses:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	refs/heads/&lt;head&gt;:refs/heads/&lt;branch&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>git push uses:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>	HEAD:refs/heads/&lt;head&gt;</pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_merge_strategies"><a class="anchor" href="#_merge_strategies"></a>MERGE STRATEGIES</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The merge mechanism (<code>git merge</code> and <code>git pull</code> commands) allows the
+backend <em>merge strategies</em> to be chosen with <code>-s</code> option.  Some strategies
+can also take their own options, which can be passed by giving <code>-X&lt;option&gt;</code>
+arguments to <code>git merge</code> and/or <code>git pull</code>.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-pull.txt-ort"> <a class="anchor" href="#Documentation/git-pull.txt-ort"></a>ort </dt>
+<dd>
+<p>This is the default merge strategy when pulling or merging one
+branch.  This strategy can only resolve two heads using a
+3-way merge algorithm.  When there is more than one common
+ancestor that can be used for 3-way merge, it creates a merged
+tree of the common ancestors and uses that as the reference
+tree for the 3-way merge.  This has been reported to result in
+fewer merge conflicts without causing mismerges by tests done
+on actual merge commits taken from Linux 2.6 kernel
+development history.  Additionally this strategy can detect
+and handle merges involving renames.  It does not make use of
+detected copies.  The name for this algorithm is an acronym
+("Ostensibly Recursive&#8217;s Twin") and came from the fact that it
+was written as a replacement for the previous default
+algorithm, <code>recursive</code>.</p>
+<div class="paragraph">
+<p>The <em>ort</em> strategy can take the following options:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-pull.txt-ours"> <a class="anchor" href="#Documentation/git-pull.txt-ours"></a>ours </dt>
+<dd>
+<p>This option forces conflicting hunks to be auto-resolved cleanly by
+favoring <em>our</em> version.  Changes from the other tree that do not
+conflict with our side are reflected in the merge result.
+For a binary file, the entire contents are taken from our side.</p>
+<div class="paragraph">
+<p>This should not be confused with the <em>ours</em> merge strategy, which does not
+even look at what the other tree contains at all.  It discards everything
+the other tree did, declaring <em>our</em> history contains all that happened in it.</p>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-theirs"> <a class="anchor" href="#Documentation/git-pull.txt-theirs"></a>theirs </dt>
+<dd>
+<p>This is the opposite of <em>ours</em>; note that, unlike <em>ours</em>, there is
+no <em>theirs</em> merge strategy to confuse this merge option with.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-ignore-space-change"> <a class="anchor" href="#Documentation/git-pull.txt-ignore-space-change"></a>ignore-space-change </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt-ignore-all-space"> <a class="anchor" href="#Documentation/git-pull.txt-ignore-all-space"></a>ignore-all-space </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt-ignore-space-at-eol"> <a class="anchor" href="#Documentation/git-pull.txt-ignore-space-at-eol"></a>ignore-space-at-eol </dt>
+<dt class="hdlist1" id="Documentation/git-pull.txt-ignore-cr-at-eol"> <a class="anchor" href="#Documentation/git-pull.txt-ignore-cr-at-eol"></a>ignore-cr-at-eol </dt>
+<dd>
+<p>Treats lines with the indicated type of whitespace change as
+unchanged for the sake of a three-way merge.  Whitespace
+changes mixed with other changes to a line are not ignored.
+See also <a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a> <code>-b</code>, <code>-w</code>,
+<code>--ignore-space-at-eol</code>, and <code>--ignore-cr-at-eol</code>.</p>
+<div class="ulist">
+<ul>
+<li>
+<p>If <em>their</em> version only introduces whitespace changes to a line,
+<em>our</em> version is used;</p>
+</li>
+<li>
+<p>If <em>our</em> version introduces whitespace changes but <em>their</em>
+version includes a substantial change, <em>their</em> version is used;</p>
+</li>
+<li>
+<p>Otherwise, the merge proceeds in the usual way.</p>
+</li>
+</ul>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-renormalize"> <a class="anchor" href="#Documentation/git-pull.txt-renormalize"></a>renormalize </dt>
+<dd>
+<p>This runs a virtual check-out and check-in of all three stages
+of a file when resolving a three-way merge.  This option is
+meant to be used when merging branches with different clean
+filters or end-of-line normalization rules.  See "Merging
+branches with differing checkin/checkout attributes" in
+<a href='{{< relurl "docs/gitattributes" >}}'>gitattributes[5]</a> for details.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-no-renormalize"> <a class="anchor" href="#Documentation/git-pull.txt-no-renormalize"></a>no-renormalize </dt>
+<dd>
+<p>Disables the <code>renormalize</code> option.  This overrides the
+<code>merge.renormalize</code> configuration variable.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-find-renamesltngt"> <a class="anchor" href="#Documentation/git-pull.txt-find-renamesltngt"></a>find-renames[=&lt;n&gt;] </dt>
+<dd>
+<p>Turn on rename detection, optionally setting the similarity
+threshold.  This is the default. This overrides the
+<em>merge.renames</em> configuration variable.
+See also <a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a> <code>--find-renames</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-rename-thresholdltngt"> <a class="anchor" href="#Documentation/git-pull.txt-rename-thresholdltngt"></a>rename-threshold=&lt;n&gt; </dt>
+<dd>
+<p>Deprecated synonym for <code>find-renames=&lt;n&gt;</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-subtreeltpathgt"> <a class="anchor" href="#Documentation/git-pull.txt-subtreeltpathgt"></a>subtree[=&lt;path&gt;] </dt>
+<dd>
+<p>This option is a more advanced form of <em>subtree</em> strategy, where
+the strategy makes a guess on how two trees must be shifted to
+match with each other when merging.  Instead, the specified path
+is prefixed (or stripped from the beginning) to make the shape of
+two trees to match.</p>
+</dd>
+</dl>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-recursive"> <a class="anchor" href="#Documentation/git-pull.txt-recursive"></a>recursive </dt>
+<dd>
+<p>This can only resolve two heads using a 3-way merge
+algorithm.  When there is more than one common
+ancestor that can be used for 3-way merge, it creates a
+merged tree of the common ancestors and uses that as
+the reference tree for the 3-way merge.  This has been
+reported to result in fewer merge conflicts without
+causing mismerges by tests done on actual merge commits
+taken from Linux 2.6 kernel development history.
+Additionally this can detect and handle merges involving
+renames.  It does not make use of detected copies.  This was
+the default strategy for resolving two heads from Git v0.99.9k
+until v2.33.0.</p>
+<div class="paragraph">
+<p>The <em>recursive</em> strategy takes the same options as <em>ort</em>.  However,
+there are three additional options that <em>ort</em> ignores (not documented
+above) that are potentially useful with the <em>recursive</em> strategy:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1" id="Documentation/git-pull.txt-patience"> <a class="anchor" href="#Documentation/git-pull.txt-patience"></a>patience </dt>
+<dd>
+<p>Deprecated synonym for <code>diff-algorithm=patience</code>.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-diff-algorithmpatienceminimalhistogrammyers"> <a class="anchor" href="#Documentation/git-pull.txt-diff-algorithmpatienceminimalhistogrammyers"></a>diff-algorithm=[patience|minimal|histogram|myers] </dt>
+<dd>
+<p>Use a different diff algorithm while merging, which can help
+avoid mismerges that occur due to unimportant matching lines
+(such as braces from distinct functions).  See also
+<a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a> <code>--diff-algorithm</code>.  Note that <code>ort</code>
+specifically uses <code>diff-algorithm=histogram</code>, while <code>recursive</code>
+defaults to the <code>diff.algorithm</code> config setting.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-no-renames"> <a class="anchor" href="#Documentation/git-pull.txt-no-renames"></a>no-renames </dt>
+<dd>
+<p>Turn off rename detection. This overrides the <code>merge.renames</code>
+configuration variable.
+See also <a href='{{< relurl "docs/git-diff" >}}'>git-diff[1]</a> <code>--no-renames</code>.</p>
+</dd>
+</dl>
+</div>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-resolve"> <a class="anchor" href="#Documentation/git-pull.txt-resolve"></a>resolve </dt>
+<dd>
+<p>This can only resolve two heads (i.e. the current branch
+and another branch you pulled from) using a 3-way merge
+algorithm.  It tries to carefully detect criss-cross
+merge ambiguities.  It does not handle renames.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-octopus"> <a class="anchor" href="#Documentation/git-pull.txt-octopus"></a>octopus </dt>
+<dd>
+<p>This resolves cases with more than two heads, but refuses to do
+a complex merge that needs manual resolution.  It is
+primarily meant to be used for bundling topic branch
+heads together.  This is the default merge strategy when
+pulling or merging more than one branch.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-ours-1"> <a class="anchor" href="#Documentation/git-pull.txt-ours-1"></a>ours </dt>
+<dd>
+<p>This resolves any number of heads, but the resulting tree of the
+merge is always that of the current branch head, effectively
+ignoring all changes from all other branches.  It is meant to
+be used to supersede old development history of side
+branches.  Note that this is different from the -Xours option to
+the <em>recursive</em> merge strategy.</p>
+</dd>
+<dt class="hdlist1" id="Documentation/git-pull.txt-subtree"> <a class="anchor" href="#Documentation/git-pull.txt-subtree"></a>subtree </dt>
+<dd>
+<p>This is a modified <code>ort</code> strategy. When merging trees A and
+B, if B corresponds to a subtree of A, B is first adjusted to
+match the tree structure of A, instead of reading the trees at
+the same level. This adjustment is also done to the common
+ancestor tree.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>With the strategies that use 3-way merge (including the default, <em>ort</em>),
+if a change is made on both branches, but later reverted on one of the
+branches, that change will be present in the merged result; some people find
+this behavior confusing.  It occurs because only the heads and the merge base
+are considered when performing a merge, not the individual commits.  The merge
+algorithm therefore considers the reverted change as no change at all, and
+substitutes the changed version instead.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_default_behaviour"><a class="anchor" href="#_default_behaviour"></a>DEFAULT BEHAVIOUR</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Often people use <code>git pull</code> without giving any parameter.
+Traditionally, this has been equivalent to saying <code>git pull
+origin</code>.  However, when configuration <code>branch.&lt;name&gt;.remote</code> is
+present while on branch <code>&lt;name&gt;</code>, that value is used instead of
+<code>origin</code>.</p>
+</div>
+<div class="paragraph">
+<p>In order to determine what URL to use to fetch from, the value
+of the configuration <code>remote.&lt;origin&gt;.url</code> is consulted
+and if there is not any such variable, the value on the <code>URL:</code> line
+in <code>$GIT_DIR/remotes/&lt;origin&gt;</code> is used.</p>
+</div>
+<div class="paragraph">
+<p>In order to determine what remote branches to fetch (and
+optionally store in the remote-tracking branches) when the command is
+run without any refspec parameters on the command line, values
+of the configuration variable <code>remote.&lt;origin&gt;.fetch</code> are
+consulted, and if there aren&#8217;t any, <code>$GIT_DIR/remotes/&lt;origin&gt;</code>
+is consulted and its <code>Pull:</code> lines are used.
+In addition to the refspec formats described in the OPTIONS
+section, you can have a globbing refspec that looks like this:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>refs/heads/*:refs/remotes/origin/*</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>A globbing refspec must have a non-empty RHS (i.e. must store
+what were fetched in remote-tracking branches), and its LHS and RHS
+must end with <code>/*</code>.  The above specifies that all remote
+branches are tracked using remote-tracking branches in
+<code>refs/remotes/origin/</code> hierarchy under the same name.</p>
+</div>
+<div class="paragraph">
+<p>The rule to determine which remote branch to merge after
+fetching is a bit involved, in order not to break backward
+compatibility.</p>
+</div>
+<div class="paragraph">
+<p>If explicit refspecs were given on the command
+line of <code>git pull</code>, they are all merged.</p>
+</div>
+<div class="paragraph">
+<p>When no refspec was given on the command line, then <code>git pull</code>
+uses the refspec from the configuration or
+<code>$GIT_DIR/remotes/&lt;origin&gt;</code>.  In such cases, the following
+rules apply:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>If <code>branch.&lt;name&gt;.merge</code> configuration for the current
+branch <code>&lt;name&gt;</code> exists, that is the name of the branch at the
+remote site that is merged.</p>
+</li>
+<li>
+<p>If the refspec is a globbing one, nothing is merged.</p>
+</li>
+<li>
+<p>Otherwise the remote branch of the first refspec is merged.</p>
+</li>
+</ol>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_examples"><a class="anchor" href="#_examples"></a>EXAMPLES</h2>
+<div class="sectionbody">
+<div class="ulist">
+<ul>
+<li>
+<p>Update the remote-tracking branches for the repository
+you cloned from, then merge one of them into your
+current branch:</p>
+<div class="listingblock">
+<div class="content">
+<pre>$ git pull
+$ git pull origin</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Normally the branch merged in is the HEAD of the remote repository,
+but the choice is determined by the branch.&lt;name&gt;.remote and
+branch.&lt;name&gt;.merge options; see <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a> for details.</p>
+</div>
+</li>
+<li>
+<p>Merge into the current branch the remote branch <code>next</code>:</p>
+<div class="listingblock">
+<div class="content">
+<pre>$ git pull origin next</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>This leaves a copy of <code>next</code> temporarily in FETCH_HEAD, and
+updates the remote-tracking branch <code>origin/next</code>.
+The same can be done by invoking fetch and merge:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>$ git fetch origin
+$ git merge origin/next</pre>
+</div>
+</div>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>If you tried a pull which resulted in complex conflicts and
+would want to start over, you can recover with <em>git reset</em>.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_security"><a class="anchor" href="#_security"></a>SECURITY</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The fetch and push protocols are not designed to prevent one side from
+stealing data from the other repository that was not intended to be
+shared. If you have private data that you need to protect from a malicious
+peer, your best option is to store it in another repository. This applies
+to both clients and servers. In particular, namespaces on a server are not
+effective for read access control; you should only grant read access to a
+namespace to clients that you would trust with read access to the entire
+repository.</p>
+</div>
+<div class="paragraph">
+<p>The known attack vectors are as follows:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>The victim sends "have" lines advertising the IDs of objects it has that
+are not explicitly intended to be shared but can be used to optimize the
+transfer if the peer also has them. The attacker chooses an object ID X
+to steal and sends a ref to X, but isn&#8217;t required to send the content of
+X because the victim already has it. Now the victim believes that the
+attacker has X, and it sends the content of X back to the attacker
+later. (This attack is most straightforward for a client to perform on a
+server, by creating a ref to X in the namespace the client has access
+to and then fetching it. The most likely way for a server to perform it
+on a client is to "merge" X into a public branch and hope that the user
+does additional work on this branch and pushes it back to the server
+without noticing the merge.)</p>
+</li>
+<li>
+<p>As in #1, the attacker chooses an object ID X to steal. The victim sends
+an object Y that the attacker already has, and the attacker falsely
+claims to have X and not Y, so the victim sends Y as a delta against X.
+The delta reveals regions of X that are similar to Y to the attacker.</p>
+</li>
+</ol>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_bugs"><a class="anchor" href="#_bugs"></a>BUGS</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Using --recurse-submodules can only fetch new commits in already checked
+out submodules right now. When e.g. upstream added a new submodule in the
+just fetched commits of the superproject the submodule itself cannot be
+fetched, making it impossible to check out that submodule later without
+having to do a fetch again. This is expected to be fixed in a future Git
+version.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also"><a class="anchor" href="#_see_also"></a>SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><a href='{{< relurl "docs/git-fetch" >}}'>git-fetch[1]</a>, <a href='{{< relurl "docs/git-merge" >}}'>git-merge[1]</a>, <a href='{{< relurl "docs/git-config" >}}'>git-config[1]</a></p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_git"><a class="anchor" href="#_git"></a>GIT</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Part of the <a href='{{< relurl "docs/git" >}}'>git[1]</a> suite</p>
+</div>
+</div>
+</div>
\ No newline at end of file
diff --git a/external/docs/content/docs/git-push/2.45.0.html b/external/docs/content/docs/git-push/2.45.0.html
index de01d0ee57..0b56424f08 100644
--- a/external/docs/content/docs/git-push/2.45.0.html
+++ b/external/docs/content/docs/git-push/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-push/2.45.2/index.html"
 - "/docs/git-push/2.46.0/index.html"
 - "/docs/git-push/2.46.1/index.html"
+- "/docs/git-push/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-quiltimport/2.43.0.html b/external/docs/content/docs/git-quiltimport/2.43.0.html
index 186d648f85..97f856f230 100644
--- a/external/docs/content/docs/git-quiltimport/2.43.0.html
+++ b/external/docs/content/docs/git-quiltimport/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-quiltimport/2.45.2/index.html"
 - "/docs/git-quiltimport/2.46.0/index.html"
 - "/docs/git-quiltimport/2.46.1/index.html"
+- "/docs/git-quiltimport/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-range-diff/2.43.0.html b/external/docs/content/docs/git-range-diff/2.43.0.html
index 282f5c9e06..51c8f8c8f4 100644
--- a/external/docs/content/docs/git-range-diff/2.43.0.html
+++ b/external/docs/content/docs/git-range-diff/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-range-diff/2.45.2/index.html"
 - "/docs/git-range-diff/2.46.0/index.html"
 - "/docs/git-range-diff/2.46.1/index.html"
+- "/docs/git-range-diff/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-read-tree/2.43.0.html b/external/docs/content/docs/git-read-tree/2.43.0.html
index 017efab210..80f5ac37b3 100644
--- a/external/docs/content/docs/git-read-tree/2.43.0.html
+++ b/external/docs/content/docs/git-read-tree/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-read-tree/2.45.2/index.html"
 - "/docs/git-read-tree/2.46.0/index.html"
 - "/docs/git-read-tree/2.46.1/index.html"
+- "/docs/git-read-tree/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-rebase/2.46.1.html b/external/docs/content/docs/git-rebase/2.46.1.html
index 7bf14cbe3e..f8766aee6d 100644
--- a/external/docs/content/docs/git-rebase/2.46.1.html
+++ b/external/docs/content/docs/git-rebase/2.46.1.html
@@ -9,6 +9,7 @@
 version: 2.46.1
 aliases:
 - "/docs/git-rebase/2.46.1/index.html"
+- "/docs/git-rebase/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-receive-pack/2.43.0.html b/external/docs/content/docs/git-receive-pack/2.43.0.html
index b01c0614a1..0616e9a000 100644
--- a/external/docs/content/docs/git-receive-pack/2.43.0.html
+++ b/external/docs/content/docs/git-receive-pack/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-receive-pack/2.45.2/index.html"
 - "/docs/git-receive-pack/2.46.0/index.html"
 - "/docs/git-receive-pack/2.46.1/index.html"
+- "/docs/git-receive-pack/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-reflog/2.45.0.html b/external/docs/content/docs/git-reflog/2.45.0.html
index d91c2333a8..276adb6f11 100644
--- a/external/docs/content/docs/git-reflog/2.45.0.html
+++ b/external/docs/content/docs/git-reflog/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-reflog/2.45.2/index.html"
 - "/docs/git-reflog/2.46.0/index.html"
 - "/docs/git-reflog/2.46.1/index.html"
+- "/docs/git-reflog/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-refs/2.46.0.html b/external/docs/content/docs/git-refs/2.46.0.html
index d033dd7d6d..4995e65507 100644
--- a/external/docs/content/docs/git-refs/2.46.0.html
+++ b/external/docs/content/docs/git-refs/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-refs/2.46.0/index.html"
 - "/docs/git-refs/2.46.1/index.html"
+- "/docs/git-refs/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-remote-ext/2.43.0.html b/external/docs/content/docs/git-remote-ext/2.43.0.html
index 270f7710ea..e6ffec51a1 100644
--- a/external/docs/content/docs/git-remote-ext/2.43.0.html
+++ b/external/docs/content/docs/git-remote-ext/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-remote-ext/2.45.2/index.html"
 - "/docs/git-remote-ext/2.46.0/index.html"
 - "/docs/git-remote-ext/2.46.1/index.html"
+- "/docs/git-remote-ext/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-remote-fd/2.43.0.html b/external/docs/content/docs/git-remote-fd/2.43.0.html
index 207ad956d8..ad0da9c5be 100644
--- a/external/docs/content/docs/git-remote-fd/2.43.0.html
+++ b/external/docs/content/docs/git-remote-fd/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-remote-fd/2.45.2/index.html"
 - "/docs/git-remote-fd/2.46.0/index.html"
 - "/docs/git-remote-fd/2.46.1/index.html"
+- "/docs/git-remote-fd/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-remote/2.45.0.html b/external/docs/content/docs/git-remote/2.45.0.html
index 514a768845..d84e529012 100644
--- a/external/docs/content/docs/git-remote/2.45.0.html
+++ b/external/docs/content/docs/git-remote/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-remote/2.45.2/index.html"
 - "/docs/git-remote/2.46.0/index.html"
 - "/docs/git-remote/2.46.1/index.html"
+- "/docs/git-remote/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-repack/2.43.0.html b/external/docs/content/docs/git-repack/2.43.0.html
index b2b12aa0a7..fb3785f1c2 100644
--- a/external/docs/content/docs/git-repack/2.43.0.html
+++ b/external/docs/content/docs/git-repack/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-repack/2.45.2/index.html"
 - "/docs/git-repack/2.46.0/index.html"
 - "/docs/git-repack/2.46.1/index.html"
+- "/docs/git-repack/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-replace/2.44.0.html b/external/docs/content/docs/git-replace/2.44.0.html
index cba8c5c55a..c6ea0bc0aa 100644
--- a/external/docs/content/docs/git-replace/2.44.0.html
+++ b/external/docs/content/docs/git-replace/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-replace/2.45.2/index.html"
 - "/docs/git-replace/2.46.0/index.html"
 - "/docs/git-replace/2.46.1/index.html"
+- "/docs/git-replace/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-replay/2.45.0.html b/external/docs/content/docs/git-replay/2.45.0.html
index e98e1a8489..64562665b6 100644
--- a/external/docs/content/docs/git-replay/2.45.0.html
+++ b/external/docs/content/docs/git-replay/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-replay/2.45.2/index.html"
 - "/docs/git-replay/2.46.0/index.html"
 - "/docs/git-replay/2.46.1/index.html"
+- "/docs/git-replay/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-request-pull/2.43.0.html b/external/docs/content/docs/git-request-pull/2.43.0.html
index 57b3f7d5b2..e36b1e1364 100644
--- a/external/docs/content/docs/git-request-pull/2.43.0.html
+++ b/external/docs/content/docs/git-request-pull/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-request-pull/2.45.2/index.html"
 - "/docs/git-request-pull/2.46.0/index.html"
 - "/docs/git-request-pull/2.46.1/index.html"
+- "/docs/git-request-pull/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-rerere/2.39.0.html b/external/docs/content/docs/git-rerere/2.39.0.html
index 5780f05b31..3d7ed99fc4 100644
--- a/external/docs/content/docs/git-rerere/2.39.0.html
+++ b/external/docs/content/docs/git-rerere/2.39.0.html
@@ -39,6 +39,7 @@
 - "/docs/git-rerere/2.45.2/index.html"
 - "/docs/git-rerere/2.46.0/index.html"
 - "/docs/git-rerere/2.46.1/index.html"
+- "/docs/git-rerere/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-reset/2.39.3.html b/external/docs/content/docs/git-reset/2.39.3.html
index e754b1fd27..bc82cf7307 100644
--- a/external/docs/content/docs/git-reset/2.39.3.html
+++ b/external/docs/content/docs/git-reset/2.39.3.html
@@ -36,6 +36,7 @@
 - "/docs/git-reset/2.45.2/index.html"
 - "/docs/git-reset/2.46.0/index.html"
 - "/docs/git-reset/2.46.1/index.html"
+- "/docs/git-reset/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-restore/2.43.0.html b/external/docs/content/docs/git-restore/2.43.0.html
index 8a3ca1e1fb..9efe1c353a 100644
--- a/external/docs/content/docs/git-restore/2.43.0.html
+++ b/external/docs/content/docs/git-restore/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-restore/2.45.2/index.html"
 - "/docs/git-restore/2.46.0/index.html"
 - "/docs/git-restore/2.46.1/index.html"
+- "/docs/git-restore/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-rev-list/2.45.0.html b/external/docs/content/docs/git-rev-list/2.45.0.html
index 92be4b12ea..db184d5ac8 100644
--- a/external/docs/content/docs/git-rev-list/2.45.0.html
+++ b/external/docs/content/docs/git-rev-list/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-rev-list/2.45.2/index.html"
 - "/docs/git-rev-list/2.46.0/index.html"
 - "/docs/git-rev-list/2.46.1/index.html"
+- "/docs/git-rev-list/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-rev-parse/2.46.0.html b/external/docs/content/docs/git-rev-parse/2.46.0.html
index 55c0911022..6ddc402591 100644
--- a/external/docs/content/docs/git-rev-parse/2.46.0.html
+++ b/external/docs/content/docs/git-rev-parse/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-rev-parse/2.46.0/index.html"
 - "/docs/git-rev-parse/2.46.1/index.html"
+- "/docs/git-rev-parse/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-revert/2.44.0.html b/external/docs/content/docs/git-revert/2.44.0.html
index aaefcd357d..8f84aa3f0f 100644
--- a/external/docs/content/docs/git-revert/2.44.0.html
+++ b/external/docs/content/docs/git-revert/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-revert/2.45.2/index.html"
 - "/docs/git-revert/2.46.0/index.html"
 - "/docs/git-revert/2.46.1/index.html"
+- "/docs/git-revert/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-rm/2.43.0.html b/external/docs/content/docs/git-rm/2.43.0.html
index e6180c90f7..0cf06a7a36 100644
--- a/external/docs/content/docs/git-rm/2.43.0.html
+++ b/external/docs/content/docs/git-rm/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-rm/2.45.2/index.html"
 - "/docs/git-rm/2.46.0/index.html"
 - "/docs/git-rm/2.46.1/index.html"
+- "/docs/git-rm/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-send-email/2.45.0.html b/external/docs/content/docs/git-send-email/2.45.0.html
index 5785055a15..0678091544 100644
--- a/external/docs/content/docs/git-send-email/2.45.0.html
+++ b/external/docs/content/docs/git-send-email/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-send-email/2.45.2/index.html"
 - "/docs/git-send-email/2.46.0/index.html"
 - "/docs/git-send-email/2.46.1/index.html"
+- "/docs/git-send-email/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-send-pack/2.43.0.html b/external/docs/content/docs/git-send-pack/2.43.0.html
index fe5a6b9165..8638ce6a73 100644
--- a/external/docs/content/docs/git-send-pack/2.43.0.html
+++ b/external/docs/content/docs/git-send-pack/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-send-pack/2.45.2/index.html"
 - "/docs/git-send-pack/2.46.0/index.html"
 - "/docs/git-send-pack/2.46.1/index.html"
+- "/docs/git-send-pack/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-sh-i18n--envsubst/2.0.5.html b/external/docs/content/docs/git-sh-i18n--envsubst/2.0.5.html
index dad9d0ba30..b8424c2eb2 100644
--- a/external/docs/content/docs/git-sh-i18n--envsubst/2.0.5.html
+++ b/external/docs/content/docs/git-sh-i18n--envsubst/2.0.5.html
@@ -196,6 +196,7 @@
 - "/docs/git-sh-i18n--envsubst/2.45.2/index.html"
 - "/docs/git-sh-i18n--envsubst/2.46.0/index.html"
 - "/docs/git-sh-i18n--envsubst/2.46.1/index.html"
+- "/docs/git-sh-i18n--envsubst/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-sh-i18n/2.0.5.html b/external/docs/content/docs/git-sh-i18n/2.0.5.html
index 423b13d5ef..d747a00ea1 100644
--- a/external/docs/content/docs/git-sh-i18n/2.0.5.html
+++ b/external/docs/content/docs/git-sh-i18n/2.0.5.html
@@ -196,6 +196,7 @@
 - "/docs/git-sh-i18n/2.45.2/index.html"
 - "/docs/git-sh-i18n/2.46.0/index.html"
 - "/docs/git-sh-i18n/2.46.1/index.html"
+- "/docs/git-sh-i18n/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-sh-setup/2.43.0.html b/external/docs/content/docs/git-sh-setup/2.43.0.html
index 964cdad441..1f658e78b5 100644
--- a/external/docs/content/docs/git-sh-setup/2.43.0.html
+++ b/external/docs/content/docs/git-sh-setup/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-sh-setup/2.45.2/index.html"
 - "/docs/git-sh-setup/2.46.0/index.html"
 - "/docs/git-sh-setup/2.46.1/index.html"
+- "/docs/git-sh-setup/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-shell/2.18.0.html b/external/docs/content/docs/git-shell/2.18.0.html
index 095209610d..bb0a75986b 100644
--- a/external/docs/content/docs/git-shell/2.18.0.html
+++ b/external/docs/content/docs/git-shell/2.18.0.html
@@ -172,6 +172,7 @@
 - "/docs/git-shell/2.45.2/index.html"
 - "/docs/git-shell/2.46.0/index.html"
 - "/docs/git-shell/2.46.1/index.html"
+- "/docs/git-shell/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-shortlog/2.45.0.html b/external/docs/content/docs/git-shortlog/2.45.0.html
index dfe867e8d3..c0c4280202 100644
--- a/external/docs/content/docs/git-shortlog/2.45.0.html
+++ b/external/docs/content/docs/git-shortlog/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-shortlog/2.45.2/index.html"
 - "/docs/git-shortlog/2.46.0/index.html"
 - "/docs/git-shortlog/2.46.1/index.html"
+- "/docs/git-shortlog/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-show-branch/2.46.0.html b/external/docs/content/docs/git-show-branch/2.46.0.html
index ef89c3df77..7ee9ebe500 100644
--- a/external/docs/content/docs/git-show-branch/2.46.0.html
+++ b/external/docs/content/docs/git-show-branch/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-show-branch/2.46.0/index.html"
 - "/docs/git-show-branch/2.46.1/index.html"
+- "/docs/git-show-branch/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-show-index/2.42.0.html b/external/docs/content/docs/git-show-index/2.42.0.html
index e38dc3e38f..477e46066f 100644
--- a/external/docs/content/docs/git-show-index/2.42.0.html
+++ b/external/docs/content/docs/git-show-index/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/git-show-index/2.45.2/index.html"
 - "/docs/git-show-index/2.46.0/index.html"
 - "/docs/git-show-index/2.46.1/index.html"
+- "/docs/git-show-index/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-show-ref/2.46.0.html b/external/docs/content/docs/git-show-ref/2.46.0.html
index 7f8e57cc59..1f96cb76b7 100644
--- a/external/docs/content/docs/git-show-ref/2.46.0.html
+++ b/external/docs/content/docs/git-show-ref/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-show-ref/2.46.0/index.html"
 - "/docs/git-show-ref/2.46.1/index.html"
+- "/docs/git-show-ref/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-show/2.46.0.html b/external/docs/content/docs/git-show/2.46.0.html
index 70d637e4ed..7c31b42f6c 100644
--- a/external/docs/content/docs/git-show/2.46.0.html
+++ b/external/docs/content/docs/git-show/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-show/2.46.0/index.html"
 - "/docs/git-show/2.46.1/index.html"
+- "/docs/git-show/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-sparse-checkout/2.42.0.html b/external/docs/content/docs/git-sparse-checkout/2.42.0.html
index 86b610760b..561b528e79 100644
--- a/external/docs/content/docs/git-sparse-checkout/2.42.0.html
+++ b/external/docs/content/docs/git-sparse-checkout/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/git-sparse-checkout/2.45.2/index.html"
 - "/docs/git-sparse-checkout/2.46.0/index.html"
 - "/docs/git-sparse-checkout/2.46.1/index.html"
+- "/docs/git-sparse-checkout/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-stage/2.35.0.html b/external/docs/content/docs/git-stage/2.35.0.html
index e474c71e3a..3ef9b6dcfe 100644
--- a/external/docs/content/docs/git-stage/2.35.0.html
+++ b/external/docs/content/docs/git-stage/2.35.0.html
@@ -69,6 +69,7 @@
 - "/docs/git-stage/2.45.2/index.html"
 - "/docs/git-stage/2.46.0/index.html"
 - "/docs/git-stage/2.46.1/index.html"
+- "/docs/git-stage/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-stash/2.43.0.html b/external/docs/content/docs/git-stash/2.43.0.html
index d83e952d87..95b6ea9ea1 100644
--- a/external/docs/content/docs/git-stash/2.43.0.html
+++ b/external/docs/content/docs/git-stash/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-stash/2.45.2/index.html"
 - "/docs/git-stash/2.46.0/index.html"
 - "/docs/git-stash/2.46.1/index.html"
+- "/docs/git-stash/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-status/2.45.0.html b/external/docs/content/docs/git-status/2.45.0.html
index cd89e0f790..f532d1eaf7 100644
--- a/external/docs/content/docs/git-status/2.45.0.html
+++ b/external/docs/content/docs/git-status/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/git-status/2.45.2/index.html"
 - "/docs/git-status/2.46.0/index.html"
 - "/docs/git-status/2.46.1/index.html"
+- "/docs/git-status/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-stripspace/2.43.0.html b/external/docs/content/docs/git-stripspace/2.43.0.html
index a2beb25d90..0d5e4664fb 100644
--- a/external/docs/content/docs/git-stripspace/2.43.0.html
+++ b/external/docs/content/docs/git-stripspace/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-stripspace/2.45.2/index.html"
 - "/docs/git-stripspace/2.46.0/index.html"
 - "/docs/git-stripspace/2.46.1/index.html"
+- "/docs/git-stripspace/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-submodule/2.44.0.html b/external/docs/content/docs/git-submodule/2.44.0.html
index 51f41d0968..da147e334d 100644
--- a/external/docs/content/docs/git-submodule/2.44.0.html
+++ b/external/docs/content/docs/git-submodule/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-submodule/2.45.2/index.html"
 - "/docs/git-submodule/2.46.0/index.html"
 - "/docs/git-submodule/2.46.1/index.html"
+- "/docs/git-submodule/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-svn/2.44.0.html b/external/docs/content/docs/git-svn/2.44.0.html
index d2b1058cb5..133849c32c 100644
--- a/external/docs/content/docs/git-svn/2.44.0.html
+++ b/external/docs/content/docs/git-svn/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-svn/2.45.2/index.html"
 - "/docs/git-svn/2.46.0/index.html"
 - "/docs/git-svn/2.46.1/index.html"
+- "/docs/git-svn/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-switch/2.44.0.html b/external/docs/content/docs/git-switch/2.44.0.html
index 36d1716fae..471ec2c4c5 100644
--- a/external/docs/content/docs/git-switch/2.44.0.html
+++ b/external/docs/content/docs/git-switch/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/git-switch/2.45.2/index.html"
 - "/docs/git-switch/2.46.0/index.html"
 - "/docs/git-switch/2.46.1/index.html"
+- "/docs/git-switch/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-symbolic-ref/2.43.0.html b/external/docs/content/docs/git-symbolic-ref/2.43.0.html
index 614e4252f1..bdde199882 100644
--- a/external/docs/content/docs/git-symbolic-ref/2.43.0.html
+++ b/external/docs/content/docs/git-symbolic-ref/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-symbolic-ref/2.45.2/index.html"
 - "/docs/git-symbolic-ref/2.46.0/index.html"
 - "/docs/git-symbolic-ref/2.46.1/index.html"
+- "/docs/git-symbolic-ref/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-tag/2.46.0.html b/external/docs/content/docs/git-tag/2.46.0.html
index fc0f9c02d3..0df6c58b8d 100644
--- a/external/docs/content/docs/git-tag/2.46.0.html
+++ b/external/docs/content/docs/git-tag/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-tag/2.46.0/index.html"
 - "/docs/git-tag/2.46.1/index.html"
+- "/docs/git-tag/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-tools/2.13.7.html b/external/docs/content/docs/git-tools/2.13.7.html
index a811389a9c..ebd8e98b90 100644
--- a/external/docs/content/docs/git-tools/2.13.7.html
+++ b/external/docs/content/docs/git-tools/2.13.7.html
@@ -183,6 +183,7 @@
 - "/docs/git-tools/2.45.2/index.html"
 - "/docs/git-tools/2.46.0/index.html"
 - "/docs/git-tools/2.46.1/index.html"
+- "/docs/git-tools/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/git-unpack-file/2.0.5.html b/external/docs/content/docs/git-unpack-file/2.0.5.html
index 1662620de3..db9d34c365 100644
--- a/external/docs/content/docs/git-unpack-file/2.0.5.html
+++ b/external/docs/content/docs/git-unpack-file/2.0.5.html
@@ -196,6 +196,7 @@
 - "/docs/git-unpack-file/2.45.2/index.html"
 - "/docs/git-unpack-file/2.46.0/index.html"
 - "/docs/git-unpack-file/2.46.1/index.html"
+- "/docs/git-unpack-file/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-unpack-objects/2.11.4.html b/external/docs/content/docs/git-unpack-objects/2.11.4.html
index dbce14c345..c8419b2900 100644
--- a/external/docs/content/docs/git-unpack-objects/2.11.4.html
+++ b/external/docs/content/docs/git-unpack-objects/2.11.4.html
@@ -185,6 +185,7 @@
 - "/docs/git-unpack-objects/2.45.2/index.html"
 - "/docs/git-unpack-objects/2.46.0/index.html"
 - "/docs/git-unpack-objects/2.46.1/index.html"
+- "/docs/git-unpack-objects/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-update-index/2.46.0.html b/external/docs/content/docs/git-update-index/2.46.0.html
index 6a28ea74e8..44d929b6a0 100644
--- a/external/docs/content/docs/git-update-index/2.46.0.html
+++ b/external/docs/content/docs/git-update-index/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-update-index/2.46.0/index.html"
 - "/docs/git-update-index/2.46.1/index.html"
+- "/docs/git-update-index/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-update-ref/2.46.0.html b/external/docs/content/docs/git-update-ref/2.46.0.html
index f0b025ca78..10a05ef968 100644
--- a/external/docs/content/docs/git-update-ref/2.46.0.html
+++ b/external/docs/content/docs/git-update-ref/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git-update-ref/2.46.0/index.html"
 - "/docs/git-update-ref/2.46.1/index.html"
+- "/docs/git-update-ref/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-update-server-info/2.43.0.html b/external/docs/content/docs/git-update-server-info/2.43.0.html
index 46296f0f92..e732bb7c78 100644
--- a/external/docs/content/docs/git-update-server-info/2.43.0.html
+++ b/external/docs/content/docs/git-update-server-info/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-update-server-info/2.45.2/index.html"
 - "/docs/git-update-server-info/2.46.0/index.html"
 - "/docs/git-update-server-info/2.46.1/index.html"
+- "/docs/git-update-server-info/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-upload-archive/2.39.0.html b/external/docs/content/docs/git-upload-archive/2.39.0.html
index f3164e5b7a..0e0776c8c0 100644
--- a/external/docs/content/docs/git-upload-archive/2.39.0.html
+++ b/external/docs/content/docs/git-upload-archive/2.39.0.html
@@ -39,6 +39,7 @@
 - "/docs/git-upload-archive/2.45.2/index.html"
 - "/docs/git-upload-archive/2.46.0/index.html"
 - "/docs/git-upload-archive/2.46.1/index.html"
+- "/docs/git-upload-archive/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-upload-pack/2.45.1.html b/external/docs/content/docs/git-upload-pack/2.45.1.html
index d234d6743c..3c0e58489d 100644
--- a/external/docs/content/docs/git-upload-pack/2.45.1.html
+++ b/external/docs/content/docs/git-upload-pack/2.45.1.html
@@ -12,6 +12,7 @@
 - "/docs/git-upload-pack/2.45.2/index.html"
 - "/docs/git-upload-pack/2.46.0/index.html"
 - "/docs/git-upload-pack/2.46.1/index.html"
+- "/docs/git-upload-pack/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-var/2.43.0.html b/external/docs/content/docs/git-var/2.43.0.html
index 117dd9b8e3..935ea9a9f2 100644
--- a/external/docs/content/docs/git-var/2.43.0.html
+++ b/external/docs/content/docs/git-var/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-var/2.45.2/index.html"
 - "/docs/git-var/2.46.0/index.html"
 - "/docs/git-var/2.46.1/index.html"
+- "/docs/git-var/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-verify-commit/2.39.0.html b/external/docs/content/docs/git-verify-commit/2.39.0.html
index b31445a6f3..45744e935e 100644
--- a/external/docs/content/docs/git-verify-commit/2.39.0.html
+++ b/external/docs/content/docs/git-verify-commit/2.39.0.html
@@ -39,6 +39,7 @@
 - "/docs/git-verify-commit/2.45.2/index.html"
 - "/docs/git-verify-commit/2.46.0/index.html"
 - "/docs/git-verify-commit/2.46.1/index.html"
+- "/docs/git-verify-commit/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-verify-pack/2.43.0.html b/external/docs/content/docs/git-verify-pack/2.43.0.html
index 63e0bbbb0d..10ca4a2fdb 100644
--- a/external/docs/content/docs/git-verify-pack/2.43.0.html
+++ b/external/docs/content/docs/git-verify-pack/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-verify-pack/2.45.2/index.html"
 - "/docs/git-verify-pack/2.46.0/index.html"
 - "/docs/git-verify-pack/2.46.1/index.html"
+- "/docs/git-verify-pack/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-verify-tag/2.39.0.html b/external/docs/content/docs/git-verify-tag/2.39.0.html
index 9e46a55842..7ff836b605 100644
--- a/external/docs/content/docs/git-verify-tag/2.39.0.html
+++ b/external/docs/content/docs/git-verify-tag/2.39.0.html
@@ -39,6 +39,7 @@
 - "/docs/git-verify-tag/2.45.2/index.html"
 - "/docs/git-verify-tag/2.46.0/index.html"
 - "/docs/git-verify-tag/2.46.1/index.html"
+- "/docs/git-verify-tag/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-version/2.33.1.html b/external/docs/content/docs/git-version/2.33.1.html
index dfe487edf3..e8f841e0df 100644
--- a/external/docs/content/docs/git-version/2.33.1.html
+++ b/external/docs/content/docs/git-version/2.33.1.html
@@ -86,6 +86,7 @@
 - "/docs/git-version/2.45.2/index.html"
 - "/docs/git-version/2.46.0/index.html"
 - "/docs/git-version/2.46.1/index.html"
+- "/docs/git-version/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-web--browse/2.35.0.html b/external/docs/content/docs/git-web--browse/2.35.0.html
index 3b418dad90..a7cf5ddf82 100644
--- a/external/docs/content/docs/git-web--browse/2.35.0.html
+++ b/external/docs/content/docs/git-web--browse/2.35.0.html
@@ -69,6 +69,7 @@
 - "/docs/git-web--browse/2.45.2/index.html"
 - "/docs/git-web--browse/2.46.0/index.html"
 - "/docs/git-web--browse/2.46.1/index.html"
+- "/docs/git-web--browse/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-whatchanged/2.43.0.html b/external/docs/content/docs/git-whatchanged/2.43.0.html
index c1520ca396..e8d74f2523 100644
--- a/external/docs/content/docs/git-whatchanged/2.43.0.html
+++ b/external/docs/content/docs/git-whatchanged/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/git-whatchanged/2.45.2/index.html"
 - "/docs/git-whatchanged/2.46.0/index.html"
 - "/docs/git-whatchanged/2.46.1/index.html"
+- "/docs/git-whatchanged/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-worktree/2.43.1.html b/external/docs/content/docs/git-worktree/2.43.1.html
index afa7bd7f02..65dfb959b3 100644
--- a/external/docs/content/docs/git-worktree/2.43.1.html
+++ b/external/docs/content/docs/git-worktree/2.43.1.html
@@ -21,6 +21,7 @@
 - "/docs/git-worktree/2.45.2/index.html"
 - "/docs/git-worktree/2.46.0/index.html"
 - "/docs/git-worktree/2.46.1/index.html"
+- "/docs/git-worktree/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git-write-tree/2.0.5.html b/external/docs/content/docs/git-write-tree/2.0.5.html
index 8be3b620b6..474af751b3 100644
--- a/external/docs/content/docs/git-write-tree/2.0.5.html
+++ b/external/docs/content/docs/git-write-tree/2.0.5.html
@@ -196,6 +196,7 @@
 - "/docs/git-write-tree/2.45.2/index.html"
 - "/docs/git-write-tree/2.46.0/index.html"
 - "/docs/git-write-tree/2.46.1/index.html"
+- "/docs/git-write-tree/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/git/2.46.0.html b/external/docs/content/docs/git/2.46.0.html
index f1b521845c..8fff5de054 100644
--- a/external/docs/content/docs/git/2.46.0.html
+++ b/external/docs/content/docs/git/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/git/2.46.0/index.html"
 - "/docs/git/2.46.1/index.html"
+- "/docs/git/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitattributes/2.46.0.html b/external/docs/content/docs/gitattributes/2.46.0.html
index 2bcf62199c..4f5f5e7f73 100644
--- a/external/docs/content/docs/gitattributes/2.46.0.html
+++ b/external/docs/content/docs/gitattributes/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/gitattributes/2.46.0/index.html"
 - "/docs/gitattributes/2.46.1/index.html"
+- "/docs/gitattributes/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitcli/2.45.0.html b/external/docs/content/docs/gitcli/2.45.0.html
index 0d66a1e555..b35299b4fa 100644
--- a/external/docs/content/docs/gitcli/2.45.0.html
+++ b/external/docs/content/docs/gitcli/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/gitcli/2.45.2/index.html"
 - "/docs/gitcli/2.46.0/index.html"
 - "/docs/gitcli/2.46.1/index.html"
+- "/docs/gitcli/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitcore-tutorial/2.43.1.html b/external/docs/content/docs/gitcore-tutorial/2.43.1.html
index 2ccbc3af16..4e9952e53e 100644
--- a/external/docs/content/docs/gitcore-tutorial/2.43.1.html
+++ b/external/docs/content/docs/gitcore-tutorial/2.43.1.html
@@ -21,6 +21,7 @@
 - "/docs/gitcore-tutorial/2.45.2/index.html"
 - "/docs/gitcore-tutorial/2.46.0/index.html"
 - "/docs/gitcore-tutorial/2.46.1/index.html"
+- "/docs/gitcore-tutorial/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitcredentials/2.42.0.html b/external/docs/content/docs/gitcredentials/2.42.0.html
index f5ebe2d73e..3b811f27ba 100644
--- a/external/docs/content/docs/gitcredentials/2.42.0.html
+++ b/external/docs/content/docs/gitcredentials/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/gitcredentials/2.45.2/index.html"
 - "/docs/gitcredentials/2.46.0/index.html"
 - "/docs/gitcredentials/2.46.1/index.html"
+- "/docs/gitcredentials/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitcvs-migration/2.12.5.html b/external/docs/content/docs/gitcvs-migration/2.12.5.html
index 84c3054205..1c5a43720f 100644
--- a/external/docs/content/docs/gitcvs-migration/2.12.5.html
+++ b/external/docs/content/docs/gitcvs-migration/2.12.5.html
@@ -184,6 +184,7 @@
 - "/docs/gitcvs-migration/2.45.2/index.html"
 - "/docs/gitcvs-migration/2.46.0/index.html"
 - "/docs/gitcvs-migration/2.46.1/index.html"
+- "/docs/gitcvs-migration/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitdiffcore/2.44.0.html b/external/docs/content/docs/gitdiffcore/2.44.0.html
index 04c47a42ec..9416971a27 100644
--- a/external/docs/content/docs/gitdiffcore/2.44.0.html
+++ b/external/docs/content/docs/gitdiffcore/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/gitdiffcore/2.45.2/index.html"
 - "/docs/gitdiffcore/2.46.0/index.html"
 - "/docs/gitdiffcore/2.46.1/index.html"
+- "/docs/gitdiffcore/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/giteveryday/2.43.0.html b/external/docs/content/docs/giteveryday/2.43.0.html
index 9d658e75a3..cbd8ae17ed 100644
--- a/external/docs/content/docs/giteveryday/2.43.0.html
+++ b/external/docs/content/docs/giteveryday/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/giteveryday/2.45.2/index.html"
 - "/docs/giteveryday/2.46.0/index.html"
 - "/docs/giteveryday/2.46.1/index.html"
+- "/docs/giteveryday/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitfaq/2.46.0.html b/external/docs/content/docs/gitfaq/2.46.0.html
index f1f6d89247..f84d0b93a2 100644
--- a/external/docs/content/docs/gitfaq/2.46.0.html
+++ b/external/docs/content/docs/gitfaq/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/gitfaq/2.46.0/index.html"
 - "/docs/gitfaq/2.46.1/index.html"
+- "/docs/gitfaq/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitformat-bundle/2.43.0.html b/external/docs/content/docs/gitformat-bundle/2.43.0.html
index a7602f5fe5..f52cdd2d66 100644
--- a/external/docs/content/docs/gitformat-bundle/2.43.0.html
+++ b/external/docs/content/docs/gitformat-bundle/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/gitformat-bundle/2.45.2/index.html"
 - "/docs/gitformat-bundle/2.46.0/index.html"
 - "/docs/gitformat-bundle/2.46.1/index.html"
+- "/docs/gitformat-bundle/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitformat-chunk/2.43.0.html b/external/docs/content/docs/gitformat-chunk/2.43.0.html
index df951bdbc4..b2036f6193 100644
--- a/external/docs/content/docs/gitformat-chunk/2.43.0.html
+++ b/external/docs/content/docs/gitformat-chunk/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/gitformat-chunk/2.45.2/index.html"
 - "/docs/gitformat-chunk/2.46.0/index.html"
 - "/docs/gitformat-chunk/2.46.1/index.html"
+- "/docs/gitformat-chunk/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitformat-commit-graph/2.46.0.html b/external/docs/content/docs/gitformat-commit-graph/2.46.0.html
index c0e6717b30..a41ebbbe33 100644
--- a/external/docs/content/docs/gitformat-commit-graph/2.46.0.html
+++ b/external/docs/content/docs/gitformat-commit-graph/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/gitformat-commit-graph/2.46.0/index.html"
 - "/docs/gitformat-commit-graph/2.46.1/index.html"
+- "/docs/gitformat-commit-graph/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitformat-index/2.44.0.html b/external/docs/content/docs/gitformat-index/2.44.0.html
index 48dcb98c87..fb9ba68d34 100644
--- a/external/docs/content/docs/gitformat-index/2.44.0.html
+++ b/external/docs/content/docs/gitformat-index/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/gitformat-index/2.45.2/index.html"
 - "/docs/gitformat-index/2.46.0/index.html"
 - "/docs/gitformat-index/2.46.1/index.html"
+- "/docs/gitformat-index/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitformat-pack/2.44.0.html b/external/docs/content/docs/gitformat-pack/2.44.0.html
index 84f34b45fa..00f47dd8a7 100644
--- a/external/docs/content/docs/gitformat-pack/2.44.0.html
+++ b/external/docs/content/docs/gitformat-pack/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/gitformat-pack/2.45.2/index.html"
 - "/docs/gitformat-pack/2.46.0/index.html"
 - "/docs/gitformat-pack/2.46.1/index.html"
+- "/docs/gitformat-pack/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitformat-signature/2.40.0.html b/external/docs/content/docs/gitformat-signature/2.40.0.html
index d9216de415..cdb0081a54 100644
--- a/external/docs/content/docs/gitformat-signature/2.40.0.html
+++ b/external/docs/content/docs/gitformat-signature/2.40.0.html
@@ -33,6 +33,7 @@
 - "/docs/gitformat-signature/2.45.2/index.html"
 - "/docs/gitformat-signature/2.46.0/index.html"
 - "/docs/gitformat-signature/2.46.1/index.html"
+- "/docs/gitformat-signature/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitglossary/2.46.0.html b/external/docs/content/docs/gitglossary/2.46.0.html
index b715a4a69e..5420c849db 100644
--- a/external/docs/content/docs/gitglossary/2.46.0.html
+++ b/external/docs/content/docs/gitglossary/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/gitglossary/2.46.0/index.html"
 - "/docs/gitglossary/2.46.1/index.html"
+- "/docs/gitglossary/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/githooks/2.46.1.html b/external/docs/content/docs/githooks/2.46.1.html
index 889bf459ce..5afaac6f08 100644
--- a/external/docs/content/docs/githooks/2.46.1.html
+++ b/external/docs/content/docs/githooks/2.46.1.html
@@ -9,6 +9,7 @@
 version: 2.46.1
 aliases:
 - "/docs/githooks/2.46.1/index.html"
+- "/docs/githooks/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitignore/2.42.0.html b/external/docs/content/docs/gitignore/2.42.0.html
index f7dff7d5c4..7e45b014fc 100644
--- a/external/docs/content/docs/gitignore/2.42.0.html
+++ b/external/docs/content/docs/gitignore/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/gitignore/2.45.2/index.html"
 - "/docs/gitignore/2.46.0/index.html"
 - "/docs/gitignore/2.46.1/index.html"
+- "/docs/gitignore/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitk/2.44.0.html b/external/docs/content/docs/gitk/2.44.0.html
index 0d7f325385..ebe44cc46d 100644
--- a/external/docs/content/docs/gitk/2.44.0.html
+++ b/external/docs/content/docs/gitk/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/gitk/2.45.2/index.html"
 - "/docs/gitk/2.46.0/index.html"
 - "/docs/gitk/2.46.1/index.html"
+- "/docs/gitk/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitmailmap/2.32.0.html b/external/docs/content/docs/gitmailmap/2.32.0.html
index 1ae033d581..7a1bff59bd 100644
--- a/external/docs/content/docs/gitmailmap/2.32.0.html
+++ b/external/docs/content/docs/gitmailmap/2.32.0.html
@@ -95,6 +95,7 @@
 - "/docs/gitmailmap/2.45.2/index.html"
 - "/docs/gitmailmap/2.46.0/index.html"
 - "/docs/gitmailmap/2.46.1/index.html"
+- "/docs/gitmailmap/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitmodules/2.42.0.html b/external/docs/content/docs/gitmodules/2.42.0.html
index b74b26a610..4c04aaad68 100644
--- a/external/docs/content/docs/gitmodules/2.42.0.html
+++ b/external/docs/content/docs/gitmodules/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/gitmodules/2.45.2/index.html"
 - "/docs/gitmodules/2.46.0/index.html"
 - "/docs/gitmodules/2.46.1/index.html"
+- "/docs/gitmodules/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitnamespaces/2.32.0.html b/external/docs/content/docs/gitnamespaces/2.32.0.html
index deadfad108..0797608c1d 100644
--- a/external/docs/content/docs/gitnamespaces/2.32.0.html
+++ b/external/docs/content/docs/gitnamespaces/2.32.0.html
@@ -95,6 +95,7 @@
 - "/docs/gitnamespaces/2.45.2/index.html"
 - "/docs/gitnamespaces/2.46.0/index.html"
 - "/docs/gitnamespaces/2.46.1/index.html"
+- "/docs/gitnamespaces/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitpacking/2.46.0.html b/external/docs/content/docs/gitpacking/2.46.0.html
index f3404d18be..bfe99e1a6d 100644
--- a/external/docs/content/docs/gitpacking/2.46.0.html
+++ b/external/docs/content/docs/gitpacking/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/gitpacking/2.46.0/index.html"
 - "/docs/gitpacking/2.46.1/index.html"
+- "/docs/gitpacking/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitprotocol-capabilities/2.44.0.html b/external/docs/content/docs/gitprotocol-capabilities/2.44.0.html
index 71a1f4cb61..abb9d2c010 100644
--- a/external/docs/content/docs/gitprotocol-capabilities/2.44.0.html
+++ b/external/docs/content/docs/gitprotocol-capabilities/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/gitprotocol-capabilities/2.45.2/index.html"
 - "/docs/gitprotocol-capabilities/2.46.0/index.html"
 - "/docs/gitprotocol-capabilities/2.46.1/index.html"
+- "/docs/gitprotocol-capabilities/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitprotocol-common/2.43.0.html b/external/docs/content/docs/gitprotocol-common/2.43.0.html
index 767da922b5..195da11598 100644
--- a/external/docs/content/docs/gitprotocol-common/2.43.0.html
+++ b/external/docs/content/docs/gitprotocol-common/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/gitprotocol-common/2.45.2/index.html"
 - "/docs/gitprotocol-common/2.46.0/index.html"
 - "/docs/gitprotocol-common/2.46.1/index.html"
+- "/docs/gitprotocol-common/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitprotocol-http/2.44.0.html b/external/docs/content/docs/gitprotocol-http/2.44.0.html
index bb28215db3..2d1522ce5d 100644
--- a/external/docs/content/docs/gitprotocol-http/2.44.0.html
+++ b/external/docs/content/docs/gitprotocol-http/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/gitprotocol-http/2.45.2/index.html"
 - "/docs/gitprotocol-http/2.46.0/index.html"
 - "/docs/gitprotocol-http/2.46.1/index.html"
+- "/docs/gitprotocol-http/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitprotocol-pack/2.43.0.html b/external/docs/content/docs/gitprotocol-pack/2.43.0.html
index b1500e91e5..801d606b6e 100644
--- a/external/docs/content/docs/gitprotocol-pack/2.43.0.html
+++ b/external/docs/content/docs/gitprotocol-pack/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/gitprotocol-pack/2.45.2/index.html"
 - "/docs/gitprotocol-pack/2.46.0/index.html"
 - "/docs/gitprotocol-pack/2.46.1/index.html"
+- "/docs/gitprotocol-pack/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitprotocol-v2/2.45.0.html b/external/docs/content/docs/gitprotocol-v2/2.45.0.html
index ac1e6affb8..ce0eb41cbb 100644
--- a/external/docs/content/docs/gitprotocol-v2/2.45.0.html
+++ b/external/docs/content/docs/gitprotocol-v2/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/gitprotocol-v2/2.45.2/index.html"
 - "/docs/gitprotocol-v2/2.46.0/index.html"
 - "/docs/gitprotocol-v2/2.46.1/index.html"
+- "/docs/gitprotocol-v2/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitremote-helpers/2.45.0.html b/external/docs/content/docs/gitremote-helpers/2.45.0.html
index 66402f5a1c..d9f741aa04 100644
--- a/external/docs/content/docs/gitremote-helpers/2.45.0.html
+++ b/external/docs/content/docs/gitremote-helpers/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/gitremote-helpers/2.45.2/index.html"
 - "/docs/gitremote-helpers/2.46.0/index.html"
 - "/docs/gitremote-helpers/2.46.1/index.html"
+- "/docs/gitremote-helpers/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitrepository-layout/2.45.0.html b/external/docs/content/docs/gitrepository-layout/2.45.0.html
index e010b4ef6d..46dda9686b 100644
--- a/external/docs/content/docs/gitrepository-layout/2.45.0.html
+++ b/external/docs/content/docs/gitrepository-layout/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/gitrepository-layout/2.45.2/index.html"
 - "/docs/gitrepository-layout/2.46.0/index.html"
 - "/docs/gitrepository-layout/2.46.1/index.html"
+- "/docs/gitrepository-layout/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitrevisions/2.42.0.html b/external/docs/content/docs/gitrevisions/2.42.0.html
index ed63c565b5..883813544b 100644
--- a/external/docs/content/docs/gitrevisions/2.42.0.html
+++ b/external/docs/content/docs/gitrevisions/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/gitrevisions/2.45.2/index.html"
 - "/docs/gitrevisions/2.46.0/index.html"
 - "/docs/gitrevisions/2.46.1/index.html"
+- "/docs/gitrevisions/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitsubmodules/2.44.0.html b/external/docs/content/docs/gitsubmodules/2.44.0.html
index 1d9bc0228c..1e003804e5 100644
--- a/external/docs/content/docs/gitsubmodules/2.44.0.html
+++ b/external/docs/content/docs/gitsubmodules/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/gitsubmodules/2.45.2/index.html"
 - "/docs/gitsubmodules/2.46.0/index.html"
 - "/docs/gitsubmodules/2.46.1/index.html"
+- "/docs/gitsubmodules/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gittutorial-2/2.23.0.html b/external/docs/content/docs/gittutorial-2/2.23.0.html
index 14376f3375..4729b8d178 100644
--- a/external/docs/content/docs/gittutorial-2/2.23.0.html
+++ b/external/docs/content/docs/gittutorial-2/2.23.0.html
@@ -142,6 +142,7 @@
 - "/docs/gittutorial-2/2.45.2/index.html"
 - "/docs/gittutorial-2/2.46.0/index.html"
 - "/docs/gittutorial-2/2.46.1/index.html"
+- "/docs/gittutorial-2/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gittutorial/2.46.1.html b/external/docs/content/docs/gittutorial/2.46.1.html
index a3450c44ea..31fd9085e0 100644
--- a/external/docs/content/docs/gittutorial/2.46.1.html
+++ b/external/docs/content/docs/gittutorial/2.46.1.html
@@ -9,6 +9,7 @@
 version: 2.46.1
 aliases:
 - "/docs/gittutorial/2.46.1/index.html"
+- "/docs/gittutorial/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitweb.conf/2.44.0.html b/external/docs/content/docs/gitweb.conf/2.44.0.html
index b7b93b726a..9ddd5beb09 100644
--- a/external/docs/content/docs/gitweb.conf/2.44.0.html
+++ b/external/docs/content/docs/gitweb.conf/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/gitweb.conf/2.45.2/index.html"
 - "/docs/gitweb.conf/2.46.0/index.html"
 - "/docs/gitweb.conf/2.46.1/index.html"
+- "/docs/gitweb.conf/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitweb/2.44.0.html b/external/docs/content/docs/gitweb/2.44.0.html
index a8db025d11..6ac44408ff 100644
--- a/external/docs/content/docs/gitweb/2.44.0.html
+++ b/external/docs/content/docs/gitweb/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/gitweb/2.45.2/index.html"
 - "/docs/gitweb/2.46.0/index.html"
 - "/docs/gitweb/2.46.1/index.html"
+- "/docs/gitweb/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/gitworkflows/2.35.0.html b/external/docs/content/docs/gitworkflows/2.35.0.html
index 9abc14f200..5c0680974d 100644
--- a/external/docs/content/docs/gitworkflows/2.35.0.html
+++ b/external/docs/content/docs/gitworkflows/2.35.0.html
@@ -69,6 +69,7 @@
 - "/docs/gitworkflows/2.45.2/index.html"
 - "/docs/gitworkflows/2.46.0/index.html"
 - "/docs/gitworkflows/2.46.1/index.html"
+- "/docs/gitworkflows/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/hash-function-transition/2.40.0.html b/external/docs/content/docs/hash-function-transition/2.40.0.html
index 2cd5f6f41e..4d889f15ec 100644
--- a/external/docs/content/docs/hash-function-transition/2.40.0.html
+++ b/external/docs/content/docs/hash-function-transition/2.40.0.html
@@ -33,6 +33,7 @@
 - "/docs/hash-function-transition/2.45.2/index.html"
 - "/docs/hash-function-transition/2.46.0/index.html"
 - "/docs/hash-function-transition/2.46.1/index.html"
+- "/docs/hash-function-transition/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_objective"><a class="anchor" href="#_objective"></a>Objective</h2>
diff --git a/external/docs/content/docs/long-running-process-protocol/2.38.0.html b/external/docs/content/docs/long-running-process-protocol/2.38.0.html
index 1cae590513..b20077b0dd 100644
--- a/external/docs/content/docs/long-running-process-protocol/2.38.0.html
+++ b/external/docs/content/docs/long-running-process-protocol/2.38.0.html
@@ -45,6 +45,7 @@
 - "/docs/long-running-process-protocol/2.45.2/index.html"
 - "/docs/long-running-process-protocol/2.46.0/index.html"
 - "/docs/long-running-process-protocol/2.46.1/index.html"
+- "/docs/long-running-process-protocol/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/merge-options/2.43.1.html b/external/docs/content/docs/merge-options/2.43.1.html
index eae9bdfd0f..d12f759d78 100644
--- a/external/docs/content/docs/merge-options/2.43.1.html
+++ b/external/docs/content/docs/merge-options/2.43.1.html
@@ -21,6 +21,7 @@
 - "/docs/merge-options/2.45.2/index.html"
 - "/docs/merge-options/2.46.0/index.html"
 - "/docs/merge-options/2.46.1/index.html"
+- "/docs/merge-options/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/merge-strategies/2.34.0.html b/external/docs/content/docs/merge-strategies/2.34.0.html
index 7eefacf6df..cf2790f109 100644
--- a/external/docs/content/docs/merge-strategies/2.34.0.html
+++ b/external/docs/content/docs/merge-strategies/2.34.0.html
@@ -78,6 +78,7 @@
 - "/docs/merge-strategies/2.45.2/index.html"
 - "/docs/merge-strategies/2.46.0/index.html"
 - "/docs/merge-strategies/2.46.1/index.html"
+- "/docs/merge-strategies/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_merge_strategies"><a class="anchor" href="#_merge_strategies"></a>MERGE STRATEGIES</h2>
diff --git a/external/docs/content/docs/multi-pack-index/2.36.0.html b/external/docs/content/docs/multi-pack-index/2.36.0.html
index c86c14bfb0..c1eb852c0e 100644
--- a/external/docs/content/docs/multi-pack-index/2.36.0.html
+++ b/external/docs/content/docs/multi-pack-index/2.36.0.html
@@ -60,6 +60,7 @@
 - "/docs/multi-pack-index/2.45.2/index.html"
 - "/docs/multi-pack-index/2.46.0/index.html"
 - "/docs/multi-pack-index/2.46.1/index.html"
+- "/docs/multi-pack-index/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/pack-heuristics/2.0.5.html b/external/docs/content/docs/pack-heuristics/2.0.5.html
index f5b0b739b4..dc9b45d87c 100644
--- a/external/docs/content/docs/pack-heuristics/2.0.5.html
+++ b/external/docs/content/docs/pack-heuristics/2.0.5.html
@@ -196,6 +196,7 @@
 - "/docs/pack-heuristics/2.45.2/index.html"
 - "/docs/pack-heuristics/2.46.0/index.html"
 - "/docs/pack-heuristics/2.46.1/index.html"
+- "/docs/pack-heuristics/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/packfile-uri/2.38.0.html b/external/docs/content/docs/packfile-uri/2.38.0.html
index 03f21dd13a..d461057513 100644
--- a/external/docs/content/docs/packfile-uri/2.38.0.html
+++ b/external/docs/content/docs/packfile-uri/2.38.0.html
@@ -45,6 +45,7 @@
 - "/docs/packfile-uri/2.45.2/index.html"
 - "/docs/packfile-uri/2.46.0/index.html"
 - "/docs/packfile-uri/2.46.1/index.html"
+- "/docs/packfile-uri/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/parallel-checkout/2.43.0.html b/external/docs/content/docs/parallel-checkout/2.43.0.html
index b0d17ae898..9ae5c88606 100644
--- a/external/docs/content/docs/parallel-checkout/2.43.0.html
+++ b/external/docs/content/docs/parallel-checkout/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/parallel-checkout/2.45.2/index.html"
 - "/docs/parallel-checkout/2.46.0/index.html"
 - "/docs/parallel-checkout/2.46.1/index.html"
+- "/docs/parallel-checkout/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/partial-clone/2.43.0.html b/external/docs/content/docs/partial-clone/2.43.0.html
index 08fad15b42..72d75e8cfb 100644
--- a/external/docs/content/docs/partial-clone/2.43.0.html
+++ b/external/docs/content/docs/partial-clone/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/partial-clone/2.45.2/index.html"
 - "/docs/partial-clone/2.46.0/index.html"
 - "/docs/partial-clone/2.46.1/index.html"
+- "/docs/partial-clone/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/pretty-formats/2.45.0.html b/external/docs/content/docs/pretty-formats/2.45.0.html
index bb5a04a914..0d5cc3e580 100644
--- a/external/docs/content/docs/pretty-formats/2.45.0.html
+++ b/external/docs/content/docs/pretty-formats/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/pretty-formats/2.45.2/index.html"
 - "/docs/pretty-formats/2.46.0/index.html"
 - "/docs/pretty-formats/2.46.1/index.html"
+- "/docs/pretty-formats/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_pretty_formats"><a class="anchor" href="#_pretty_formats"></a>PRETTY FORMATS</h2>
diff --git a/external/docs/content/docs/pretty-options/2.43.0.html b/external/docs/content/docs/pretty-options/2.43.0.html
index c9dbbd3cd9..5b3a2121f5 100644
--- a/external/docs/content/docs/pretty-options/2.43.0.html
+++ b/external/docs/content/docs/pretty-options/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/pretty-options/2.45.2/index.html"
 - "/docs/pretty-options/2.46.0/index.html"
 - "/docs/pretty-options/2.46.1/index.html"
+- "/docs/pretty-options/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/pull-fetch-param/2.43.0.html b/external/docs/content/docs/pull-fetch-param/2.43.0.html
index 8e9a251caf..f1ba3013f8 100644
--- a/external/docs/content/docs/pull-fetch-param/2.43.0.html
+++ b/external/docs/content/docs/pull-fetch-param/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/pull-fetch-param/2.45.2/index.html"
 - "/docs/pull-fetch-param/2.46.0/index.html"
 - "/docs/pull-fetch-param/2.46.1/index.html"
+- "/docs/pull-fetch-param/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/racy-git/2.43.0.html b/external/docs/content/docs/racy-git/2.43.0.html
index 95adf00863..4725794925 100644
--- a/external/docs/content/docs/racy-git/2.43.0.html
+++ b/external/docs/content/docs/racy-git/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/racy-git/2.45.2/index.html"
 - "/docs/racy-git/2.46.0/index.html"
 - "/docs/racy-git/2.46.1/index.html"
+- "/docs/racy-git/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_background"><a class="anchor" href="#_background"></a>Background</h2>
diff --git a/external/docs/content/docs/reftable/2.43.0.html b/external/docs/content/docs/reftable/2.43.0.html
index 75cd56214a..157aba43ac 100644
--- a/external/docs/content/docs/reftable/2.43.0.html
+++ b/external/docs/content/docs/reftable/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/reftable/2.45.2/index.html"
 - "/docs/reftable/2.46.0/index.html"
 - "/docs/reftable/2.46.1/index.html"
+- "/docs/reftable/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_reftable"><a class="anchor" href="#_reftable"></a>reftable</h2>
diff --git a/external/docs/content/docs/remembering-renames/2.42.0.html b/external/docs/content/docs/remembering-renames/2.42.0.html
index fa9f88e2c6..00d43e1d59 100644
--- a/external/docs/content/docs/remembering-renames/2.42.0.html
+++ b/external/docs/content/docs/remembering-renames/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/remembering-renames/2.45.2/index.html"
 - "/docs/remembering-renames/2.46.0/index.html"
 - "/docs/remembering-renames/2.46.1/index.html"
+- "/docs/remembering-renames/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/repository-version/2.45.0.html b/external/docs/content/docs/repository-version/2.45.0.html
index 3f9146e053..4e6e0458d9 100644
--- a/external/docs/content/docs/repository-version/2.45.0.html
+++ b/external/docs/content/docs/repository-version/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/repository-version/2.45.2/index.html"
 - "/docs/repository-version/2.46.0/index.html"
 - "/docs/repository-version/2.46.1/index.html"
+- "/docs/repository-version/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_git_repository_format_versions"><a class="anchor" href="#_git_repository_format_versions"></a>Git Repository Format Versions</h2>
diff --git a/external/docs/content/docs/rerere/2.43.0.html b/external/docs/content/docs/rerere/2.43.0.html
index a0b97f773e..fc25355890 100644
--- a/external/docs/content/docs/rerere/2.43.0.html
+++ b/external/docs/content/docs/rerere/2.43.0.html
@@ -22,6 +22,7 @@
 - "/docs/rerere/2.45.2/index.html"
 - "/docs/rerere/2.46.0/index.html"
 - "/docs/rerere/2.46.1/index.html"
+- "/docs/rerere/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/rev-list-description/2.29.0.html b/external/docs/content/docs/rev-list-description/2.29.0.html
index 801e4250a6..6ea86ee7eb 100644
--- a/external/docs/content/docs/rev-list-description/2.29.0.html
+++ b/external/docs/content/docs/rev-list-description/2.29.0.html
@@ -118,6 +118,7 @@
 - "/docs/rev-list-description/2.45.2/index.html"
 - "/docs/rev-list-description/2.46.0/index.html"
 - "/docs/rev-list-description/2.46.1/index.html"
+- "/docs/rev-list-description/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/rev-list-options/2.45.0.html b/external/docs/content/docs/rev-list-options/2.45.0.html
index 87c613f653..b6bbd5de67 100644
--- a/external/docs/content/docs/rev-list-options/2.45.0.html
+++ b/external/docs/content/docs/rev-list-options/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/rev-list-options/2.45.2/index.html"
 - "/docs/rev-list-options/2.46.0/index.html"
 - "/docs/rev-list-options/2.46.1/index.html"
+- "/docs/rev-list-options/2.46.2/index.html"
 ---
 <div class="sect2">
 <h3 id="_commit_limiting"><a class="anchor" href="#_commit_limiting"></a>Commit Limiting</h3>
diff --git a/external/docs/content/docs/revisions/2.42.0.html b/external/docs/content/docs/revisions/2.42.0.html
index 489c499e3e..4cb20b52e4 100644
--- a/external/docs/content/docs/revisions/2.42.0.html
+++ b/external/docs/content/docs/revisions/2.42.0.html
@@ -26,6 +26,7 @@
 - "/docs/revisions/2.45.2/index.html"
 - "/docs/revisions/2.46.0/index.html"
 - "/docs/revisions/2.46.1/index.html"
+- "/docs/revisions/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_specifying_revisions"><a class="anchor" href="#_specifying_revisions"></a>SPECIFYING REVISIONS</h2>
diff --git a/external/docs/content/docs/scalar/2.42.1.html b/external/docs/content/docs/scalar/2.42.1.html
index d5756aaf30..4ac718f042 100644
--- a/external/docs/content/docs/scalar/2.42.1.html
+++ b/external/docs/content/docs/scalar/2.42.1.html
@@ -25,6 +25,7 @@
 - "/docs/scalar/2.45.2/index.html"
 - "/docs/scalar/2.46.0/index.html"
 - "/docs/scalar/2.46.1/index.html"
+- "/docs/scalar/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_name"><a class="anchor" href="#_name"></a>NAME</h2>
diff --git a/external/docs/content/docs/send-pack-pipeline/2.0.5.html b/external/docs/content/docs/send-pack-pipeline/2.0.5.html
index f5c76a9378..1c292f9805 100644
--- a/external/docs/content/docs/send-pack-pipeline/2.0.5.html
+++ b/external/docs/content/docs/send-pack-pipeline/2.0.5.html
@@ -196,6 +196,7 @@
 - "/docs/send-pack-pipeline/2.45.2/index.html"
 - "/docs/send-pack-pipeline/2.46.0/index.html"
 - "/docs/send-pack-pipeline/2.46.1/index.html"
+- "/docs/send-pack-pipeline/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_overall_operation"><a class="anchor" href="#_overall_operation"></a>Overall operation</h2>
diff --git a/external/docs/content/docs/shallow/2.29.0.html b/external/docs/content/docs/shallow/2.29.0.html
index 17f2253dcd..b6d59e82b0 100644
--- a/external/docs/content/docs/shallow/2.29.0.html
+++ b/external/docs/content/docs/shallow/2.29.0.html
@@ -118,6 +118,7 @@
 - "/docs/shallow/2.45.2/index.html"
 - "/docs/shallow/2.46.0/index.html"
 - "/docs/shallow/2.46.1/index.html"
+- "/docs/shallow/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/sparse-checkout/2.39.0.html b/external/docs/content/docs/sparse-checkout/2.39.0.html
index fe50b97684..b4f6c4fdea 100644
--- a/external/docs/content/docs/sparse-checkout/2.39.0.html
+++ b/external/docs/content/docs/sparse-checkout/2.39.0.html
@@ -39,6 +39,7 @@
 - "/docs/sparse-checkout/2.45.2/index.html"
 - "/docs/sparse-checkout/2.46.0/index.html"
 - "/docs/sparse-checkout/2.46.1/index.html"
+- "/docs/sparse-checkout/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/sparse-index/2.32.0.html b/external/docs/content/docs/sparse-index/2.32.0.html
index 0115d3972a..66ce7cb1eb 100644
--- a/external/docs/content/docs/sparse-index/2.32.0.html
+++ b/external/docs/content/docs/sparse-index/2.32.0.html
@@ -95,6 +95,7 @@
 - "/docs/sparse-index/2.45.2/index.html"
 - "/docs/sparse-index/2.46.0/index.html"
 - "/docs/sparse-index/2.46.1/index.html"
+- "/docs/sparse-index/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/trivial-merge/2.15.4.html b/external/docs/content/docs/trivial-merge/2.15.4.html
index 8f506b2f46..30ca7dbb72 100644
--- a/external/docs/content/docs/trivial-merge/2.15.4.html
+++ b/external/docs/content/docs/trivial-merge/2.15.4.html
@@ -181,6 +181,7 @@
 - "/docs/trivial-merge/2.45.2/index.html"
 - "/docs/trivial-merge/2.46.0/index.html"
 - "/docs/trivial-merge/2.46.1/index.html"
+- "/docs/trivial-merge/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/unit-tests/2.44.0.html b/external/docs/content/docs/unit-tests/2.44.0.html
index 7450ffafd5..2422842032 100644
--- a/external/docs/content/docs/unit-tests/2.44.0.html
+++ b/external/docs/content/docs/unit-tests/2.44.0.html
@@ -16,6 +16,7 @@
 - "/docs/unit-tests/2.45.2/index.html"
 - "/docs/unit-tests/2.46.0/index.html"
 - "/docs/unit-tests/2.46.1/index.html"
+- "/docs/unit-tests/2.46.2/index.html"
 ---
 <div id="preamble">
 <div class="sectionbody">
diff --git a/external/docs/content/docs/user-manual/2.46.0.html b/external/docs/content/docs/user-manual/2.46.0.html
index 38d6791fcc..770f9b6f0e 100644
--- a/external/docs/content/docs/user-manual/2.46.0.html
+++ b/external/docs/content/docs/user-manual/2.46.0.html
@@ -10,6 +10,7 @@
 aliases:
 - "/docs/user-manual/2.46.0/index.html"
 - "/docs/user-manual/2.46.1/index.html"
+- "/docs/user-manual/2.46.2/index.html"
 ---
 <div class="sect1">
 <h2 id="_introduction"><a class="anchor" href="#_introduction"></a>Introduction</h2>
diff --git a/external/docs/content/docs/vimdiff/2.45.0.html b/external/docs/content/docs/vimdiff/2.45.0.html
index 63b93e6a1c..26bedaab49 100644
--- a/external/docs/content/docs/vimdiff/2.45.0.html
+++ b/external/docs/content/docs/vimdiff/2.45.0.html
@@ -13,6 +13,7 @@
 - "/docs/vimdiff/2.45.2/index.html"
 - "/docs/vimdiff/2.46.0/index.html"
 - "/docs/vimdiff/2.46.1/index.html"
+- "/docs/vimdiff/2.46.2/index.html"
 ---
 <div class="sect3">
 <h4 id="_description"><a class="anchor" href="#_description"></a>Description</h4>
diff --git a/external/docs/data/docs.yml b/external/docs/data/docs.yml
index 45852b9e31..be04455c56 100644
--- a/external/docs/data/docs.yml
+++ b/external/docs/data/docs.yml
@@ -940,6 +940,11 @@ versions:
     tree_sha: 4088ad4870da72ba86e62a1bdc2ad9472b26bdb8
     committed: 2024-09-13 22:26:52.000000000 +00:00
     date: '09/13/24'
+  2.46.2:
+    commit_sha: 466b63bd086c499668f5a0ec7f4ff8cdbbe7c32a
+    tree_sha: ddffa72fcc8e3352ca422c57758bbe0cb0b13024
+    committed: 2024-09-23 17:33:01.000000000 +00:00
+    date: '09/23/24'
 pages:
   SubmittingPatches:
     version-map:
@@ -1131,9 +1136,10 @@ pages:
       2.45.2: 45a436c1655e1208c1f91dbb5108910b8ce474f6
       2.46.0: f09516d450bb56a72469e1cd9b3370b8e4f5c9ab
       2.46.1: f09516d450bb56a72469e1cd9b3370b8e4f5c9ab
+      2.46.2: f09516d450bb56a72469e1cd9b3370b8e4f5c9ab
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 6
       removed: 2
@@ -1684,9 +1690,10 @@ pages:
       2.45.2: 3346217c409501c7c231c4f350c80559241f058b
       2.46.0: 3346217c409501c7c231c4f350c80559241f058b
       2.46.1: 3346217c409501c7c231c4f350c80559241f058b
+      2.46.2: 3346217c409501c7c231c4f350c80559241f058b
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -2000,9 +2007,10 @@ pages:
       2.45.2: 41f8b63cb31e1061f2f4a37ce505a2d7fb93d275
       2.46.0: 41f8b63cb31e1061f2f4a37ce505a2d7fb93d275
       2.46.1: 41f8b63cb31e1061f2f4a37ce505a2d7fb93d275
+      2.46.2: 41f8b63cb31e1061f2f4a37ce505a2d7fb93d275
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -2277,9 +2285,10 @@ pages:
       2.45.2: d1c1be0d38264a6b115b6c0f9c09e09bdbfcc240
       2.46.0: 38d392cee3b167bf1e930f344aeb26a735209e38
       2.46.1: 38d392cee3b167bf1e930f344aeb26a735209e38
+      2.46.2: 38d392cee3b167bf1e930f344aeb26a735209e38
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 6
       removed: 2
@@ -2730,8 +2739,12 @@ pages:
       2.45.2: d8900ba46c554ddf7a9967f33b4902fe31fa8863
       2.46.0: d8900ba46c554ddf7a9967f33b4902fe31fa8863
       2.46.1: d8900ba46c554ddf7a9967f33b4902fe31fa8863
-    latest-changes: 2.45.0
+      2.46.2: 8ce83a5e94562ab0e73c88ef4afd41ae6d2296a7
+    latest-changes: 2.46.2
     page-versions:
+    - name: 2.46.2
+      added: 3
+      removed: 2
     - name: 2.45.1 &rarr; 2.46.1
     - name: 2.45.0
       added: 1
@@ -2933,6 +2946,10 @@ pages:
       - 1
       - 1
       - 6
+      d8900ba46c554ddf7a9967f33b4902fe31fa8863..8ce83a5e94562ab0e73c88ef4afd41ae6d2296a7:
+      - 3
+      - 2
+      - 3
   git-add:
     version-map:
       2.0.5: 443cdbe3e0f01b81e1317ec0ed245bb99c7ba7be
@@ -3123,9 +3140,10 @@ pages:
       2.45.2: 077ae0e56575bdd2f38a458c59ac1c43db0c16a4
       2.46.0: 740284a9d3d3278239208cbd7b9c5b3a36f894ff
       2.46.1: 740284a9d3d3278239208cbd7b9c5b3a36f894ff
+      2.46.2: 740284a9d3d3278239208cbd7b9c5b3a36f894ff
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 0
       removed: 6
@@ -3464,9 +3482,10 @@ pages:
       2.45.2: caf7f8f1997389021ed799e59b16db8cc3c9dd12
       2.46.0: 0634ae6310f864614968580e75326a614ec4206d
       2.46.1: 0634ae6310f864614968580e75326a614ec4206d
+      2.46.2: 0634ae6310f864614968580e75326a614ec4206d
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 7
       removed: 1
@@ -3846,9 +3865,10 @@ pages:
       2.45.2: 06c1030c37c0f4b565f172af219ef39418bdc64e
       2.46.0: 06c1030c37c0f4b565f172af219ef39418bdc64e
       2.46.1: 06c1030c37c0f4b565f172af219ef39418bdc64e
+      2.46.2: 06c1030c37c0f4b565f172af219ef39418bdc64e
     latest-changes: 2.41.0
     page-versions:
-    - name: 2.41.1 &rarr; 2.46.1
+    - name: 2.41.1 &rarr; 2.46.2
     - name: 2.41.0
       added: 3
       removed: 5
@@ -4165,9 +4185,10 @@ pages:
       2.45.2: 9f9eccbeea59b27eba153e43dd0fe827579d5032
       2.46.0: 9f9eccbeea59b27eba153e43dd0fe827579d5032
       2.46.1: 9f9eccbeea59b27eba153e43dd0fe827579d5032
+      2.46.2: 9f9eccbeea59b27eba153e43dd0fe827579d5032
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -4469,9 +4490,10 @@ pages:
       2.45.2: 1691563a6ff43e74816f3940095c12fd3e45b36a
       2.46.0: 1691563a6ff43e74816f3940095c12fd3e45b36a
       2.46.1: 1691563a6ff43e74816f3940095c12fd3e45b36a
+      2.46.2: 1691563a6ff43e74816f3940095c12fd3e45b36a
     latest-changes: 2.35.0
     page-versions:
-    - name: 2.35.1 &rarr; 2.46.1
+    - name: 2.35.1 &rarr; 2.46.2
     - name: 2.35.0
       added: 4
       removed: 4
@@ -4694,9 +4716,10 @@ pages:
       2.45.2: 8a3bf1be66b1a003d25765b1cf45ee518510f316
       2.46.0: a0f5baab29d4b6b51ed00efe1358f0a2311de1b7
       2.46.1: a0f5baab29d4b6b51ed00efe1358f0a2311de1b7
+      2.46.2: a0f5baab29d4b6b51ed00efe1358f0a2311de1b7
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 5
       removed: 3
@@ -4951,9 +4974,10 @@ pages:
       2.45.2: fc37ea736c6c8882cd96167b64ff002dfa791904
       2.46.0: fc37ea736c6c8882cd96167b64ff002dfa791904
       2.46.1: fc37ea736c6c8882cd96167b64ff002dfa791904
+      2.46.2: fc37ea736c6c8882cd96167b64ff002dfa791904
     latest-changes: 2.40.0
     page-versions:
-    - name: 2.40.1 &rarr; 2.46.1
+    - name: 2.40.1 &rarr; 2.46.2
     - name: 2.40.0
       added: 2
       removed: 2
@@ -5223,9 +5247,10 @@ pages:
       2.45.2: 6bf61e07cd3893b1697c3c68232d3cca746b3378
       2.46.0: 6bf61e07cd3893b1697c3c68232d3cca746b3378
       2.46.1: 6bf61e07cd3893b1697c3c68232d3cca746b3378
+      2.46.2: 6bf61e07cd3893b1697c3c68232d3cca746b3378
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 2
       removed: 2
@@ -5540,9 +5565,10 @@ pages:
       2.45.2: f7e846b3d278aea8dee3abddd0f8b390553aaa34
       2.46.0: f7e846b3d278aea8dee3abddd0f8b390553aaa34
       2.46.1: f7e846b3d278aea8dee3abddd0f8b390553aaa34
+      2.46.2: f7e846b3d278aea8dee3abddd0f8b390553aaa34
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 1
       removed: 1
@@ -5873,9 +5899,10 @@ pages:
       2.45.2: 8f2b26643f3fdb71985c32e7bc29791b70d7e848
       2.46.0: 8f2b26643f3fdb71985c32e7bc29791b70d7e848
       2.46.1: 8f2b26643f3fdb71985c32e7bc29791b70d7e848
+      2.46.2: 8f2b26643f3fdb71985c32e7bc29791b70d7e848
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 2
       removed: 1
@@ -6316,9 +6343,10 @@ pages:
       2.45.2: 79bf4569ea8b16f9779d58a8c8f333178c05c2ef
       2.46.0: 79bf4569ea8b16f9779d58a8c8f333178c05c2ef
       2.46.1: 79bf4569ea8b16f9779d58a8c8f333178c05c2ef
+      2.46.2: 79bf4569ea8b16f9779d58a8c8f333178c05c2ef
     latest-changes: 2.41.0
     page-versions:
-    - name: 2.41.1 &rarr; 2.46.1
+    - name: 2.41.1 &rarr; 2.46.2
     - name: 2.41.0
       added: 2
       removed: 6
@@ -6589,8 +6617,10 @@ pages:
       2.45.2: ff0b4fc54125e9f3d3361b6e0a4556520a684717
       2.46.0: ff0b4fc54125e9f3d3361b6e0a4556520a684717
       2.46.1: dab836881ad773cc3508b56e192f35abb33a8519
+      2.46.2: dab836881ad773cc3508b56e192f35abb33a8519
     latest-changes: 2.46.1
     page-versions:
+    - name: 2.46.2
     - name: 2.46.1
       added: 3
       removed: 3
@@ -6923,9 +6953,10 @@ pages:
       2.45.2: c1a58acc4bbbd58456605bce7a0bfe2b2e8ed4cc
       2.46.0: c1a58acc4bbbd58456605bce7a0bfe2b2e8ed4cc
       2.46.1: c1a58acc4bbbd58456605bce7a0bfe2b2e8ed4cc
+      2.46.2: c1a58acc4bbbd58456605bce7a0bfe2b2e8ed4cc
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 3
       removed: 3
@@ -7164,9 +7195,10 @@ pages:
       2.45.2: c1b471ae7232698f9e1a401cd917fefc2d268029
       2.46.0: c1b471ae7232698f9e1a401cd917fefc2d268029
       2.46.1: c1b471ae7232698f9e1a401cd917fefc2d268029
+      2.46.2: c1b471ae7232698f9e1a401cd917fefc2d268029
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -7436,9 +7468,10 @@ pages:
       2.45.2: 9569919f3591eacc334c60f8abaf6d5350b843a4
       2.46.0: 9569919f3591eacc334c60f8abaf6d5350b843a4
       2.46.1: 9569919f3591eacc334c60f8abaf6d5350b843a4
+      2.46.2: 9569919f3591eacc334c60f8abaf6d5350b843a4
     latest-changes: 2.31.0
     page-versions:
-    - name: 2.31.1 &rarr; 2.46.1
+    - name: 2.31.1 &rarr; 2.46.2
     - name: 2.31.0
       added: 1
       removed: 7
@@ -7653,9 +7686,10 @@ pages:
       2.45.2: b24f0b6d4d08cd4183a4ad60a3042b450e067bba
       2.46.0: b24f0b6d4d08cd4183a4ad60a3042b450e067bba
       2.46.1: b24f0b6d4d08cd4183a4ad60a3042b450e067bba
+      2.46.2: b24f0b6d4d08cd4183a4ad60a3042b450e067bba
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -7909,9 +7943,10 @@ pages:
       2.45.2: 24f80f7a6cd125b06655a67b405374718cce0922
       2.46.0: 24f80f7a6cd125b06655a67b405374718cce0922
       2.46.1: 24f80f7a6cd125b06655a67b405374718cce0922
+      2.46.2: 24f80f7a6cd125b06655a67b405374718cce0922
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -8126,9 +8161,10 @@ pages:
       2.45.2: '0939c600cb0224a8ebb0173b6a2f9be8cf7d991e'
       2.46.0: '0939c600cb0224a8ebb0173b6a2f9be8cf7d991e'
       2.46.1: '0939c600cb0224a8ebb0173b6a2f9be8cf7d991e'
+      2.46.2: '0939c600cb0224a8ebb0173b6a2f9be8cf7d991e'
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 3
       removed: 1
@@ -8531,9 +8567,10 @@ pages:
       2.45.2: e9484f3085ae45cbcad4fa58e2a72a3fb8edfeb3
       2.46.0: e9484f3085ae45cbcad4fa58e2a72a3fb8edfeb3
       2.46.1: e9484f3085ae45cbcad4fa58e2a72a3fb8edfeb3
+      2.46.2: e9484f3085ae45cbcad4fa58e2a72a3fb8edfeb3
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 6
       removed: 2
@@ -8835,9 +8872,10 @@ pages:
       2.45.2: fca5b29775cc02c100f35be6819e2d1742c37129
       2.46.0: fca5b29775cc02c100f35be6819e2d1742c37129
       2.46.1: fca5b29775cc02c100f35be6819e2d1742c37129
+      2.46.2: fca5b29775cc02c100f35be6819e2d1742c37129
     latest-changes: 2.0.5
     page-versions:
-    - name: 2.1.4 &rarr; 2.46.1
+    - name: 2.1.4 &rarr; 2.46.2
     - name: 2.0.5
       added: 8
       removed: 0
@@ -9035,9 +9073,10 @@ pages:
       2.45.2: e3c67bd3820e6646fd79f04bd04a766740e94ca8
       2.46.0: e3c67bd3820e6646fd79f04bd04a766740e94ca8
       2.46.1: e3c67bd3820e6646fd79f04bd04a766740e94ca8
+      2.46.2: e3c67bd3820e6646fd79f04bd04a766740e94ca8
     latest-changes: 2.0.5
     page-versions:
-    - name: 2.1.4 &rarr; 2.46.1
+    - name: 2.1.4 &rarr; 2.46.2
     - name: 2.0.5
       added: 8
       removed: 0
@@ -9236,9 +9275,10 @@ pages:
       2.45.2: 7d276c2f798e8862e333439e7f71ac9fb2efdbf2
       2.46.0: 7d276c2f798e8862e333439e7f71ac9fb2efdbf2
       2.46.1: 7d276c2f798e8862e333439e7f71ac9fb2efdbf2
+      2.46.2: 7d276c2f798e8862e333439e7f71ac9fb2efdbf2
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 6
       removed: 2
@@ -9532,9 +9572,10 @@ pages:
       2.45.2: 572ccf8dd106f954cb3f7a1eb7f40af6495c5e01
       2.46.0: af0ca6837d96d2e4d80fb942f09bb44bcc45393c
       2.46.1: af0ca6837d96d2e4d80fb942f09bb44bcc45393c
+      2.46.2: af0ca6837d96d2e4d80fb942f09bb44bcc45393c
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 3
       removed: 3
@@ -9957,9 +9998,10 @@ pages:
       2.45.2: 9860bf5aa473abd05872712874e31795c402e550
       2.46.0: 9860bf5aa473abd05872712874e31795c402e550
       2.46.1: 9860bf5aa473abd05872712874e31795c402e550
+      2.46.2: 9860bf5aa473abd05872712874e31795c402e550
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -10198,9 +10240,10 @@ pages:
       2.45.2: 968f0c2e58f5fc3bd4673819349a52fa9e20fe3e
       2.46.0: 968f0c2e58f5fc3bd4673819349a52fa9e20fe3e
       2.46.1: 968f0c2e58f5fc3bd4673819349a52fa9e20fe3e
+      2.46.2: 968f0c2e58f5fc3bd4673819349a52fa9e20fe3e
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 1
       removed: 1
@@ -10495,8 +10538,10 @@ pages:
       2.45.2: 70f4e8be0fa063c24fc5c69ef74a8150693c863c
       2.46.0: 70f4e8be0fa063c24fc5c69ef74a8150693c863c
       2.46.1: 91c678d637b1c463cb2fca1a41214c3fa310c350
+      2.46.2: 91c678d637b1c463cb2fca1a41214c3fa310c350
     latest-changes: 2.46.1
     page-versions:
+    - name: 2.46.2
     - name: 2.46.1
       added: 1
       removed: 1
@@ -10905,8 +10950,12 @@ pages:
       2.45.2: b7d42ee3a96bbfbde11c2bf8f985846c35434d46
       2.46.0: 1c496efb53efb4a95b11f49c9d427dc67a623501
       2.46.1: cceab1eb46385edba371094a95b8d022a652b103
-    latest-changes: 2.46.1
+      2.46.2: b6eb1ed05504fc766aabc581c310057c6a46f010
+    latest-changes: 2.46.2
     page-versions:
+    - name: 2.46.2
+      added: 4
+      removed: 4
     - name: 2.46.1
       added: 3
       removed: 3
@@ -11549,6 +11598,10 @@ pages:
       - 3
       - 3
       - 2
+      cceab1eb46385edba371094a95b8d022a652b103..b6eb1ed05504fc766aabc581c310057c6a46f010:
+      - 4
+      - 4
+      - 0
     languages:
       de: cfc4dde585cd604b17807e748698ba0e59d518ae
       fr: 4a1b240ec9f73ec37b7a78b770932aab9a191cd3
@@ -11744,9 +11797,10 @@ pages:
       2.45.2: 69e470468b5f72bff478dd3c90b9353d48a8b164
       2.46.0: 69e470468b5f72bff478dd3c90b9353d48a8b164
       2.46.1: 69e470468b5f72bff478dd3c90b9353d48a8b164
+      2.46.2: 69e470468b5f72bff478dd3c90b9353d48a8b164
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 3
       removed: 3
@@ -11961,9 +12015,10 @@ pages:
       2.45.2: 0f496296c8f129e8440619fc5cd8d54c4f4f372e
       2.46.0: 0f496296c8f129e8440619fc5cd8d54c4f4f372e
       2.46.1: 0f496296c8f129e8440619fc5cd8d54c4f4f372e
+      2.46.2: 0f496296c8f129e8440619fc5cd8d54c4f4f372e
     latest-changes: 2.39.0
     page-versions:
-    - name: 2.39.1 &rarr; 2.46.1
+    - name: 2.39.1 &rarr; 2.46.2
     - name: 2.39.0
       added: 2
       removed: 2
@@ -12186,9 +12241,10 @@ pages:
       2.45.2: 843721e094e03d93da4e34787d4c2fdf34999847
       2.46.0: 843721e094e03d93da4e34787d4c2fdf34999847
       2.46.1: 843721e094e03d93da4e34787d4c2fdf34999847
+      2.46.2: 843721e094e03d93da4e34787d4c2fdf34999847
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -12435,9 +12491,10 @@ pages:
       2.45.2: e9b29d031cebe068cd1c4ee28f1637edb46a5428
       2.46.0: e9b29d031cebe068cd1c4ee28f1637edb46a5428
       2.46.1: e9b29d031cebe068cd1c4ee28f1637edb46a5428
+      2.46.2: e9b29d031cebe068cd1c4ee28f1637edb46a5428
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -12683,9 +12740,10 @@ pages:
       2.45.2: d3cbad66651b15c3b7a1ef5b80ae71b4c1cc8a82
       2.46.0: d746383dfb0b8fb1199e16a2675c78cfb5e3a1a8
       2.46.1: d746383dfb0b8fb1199e16a2675c78cfb5e3a1a8
+      2.46.2: d746383dfb0b8fb1199e16a2675c78cfb5e3a1a8
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 8
       removed: 0
@@ -12965,9 +13023,10 @@ pages:
       2.45.2: 21e33cfed625a03ebe4b920a91c9d69bd613a4e6
       2.46.0: 21e33cfed625a03ebe4b920a91c9d69bd613a4e6
       2.46.1: 21e33cfed625a03ebe4b920a91c9d69bd613a4e6
+      2.46.2: 21e33cfed625a03ebe4b920a91c9d69bd613a4e6
     latest-changes: 2.35.0
     page-versions:
-    - name: 2.35.1 &rarr; 2.46.1
+    - name: 2.35.1 &rarr; 2.46.2
     - name: 2.35.0
       added: 2
       removed: 2
@@ -13174,9 +13233,10 @@ pages:
       2.45.2: be3b042784bcabd5af20b48fd0261b900cf05133
       2.46.0: be3b042784bcabd5af20b48fd0261b900cf05133
       2.46.1: be3b042784bcabd5af20b48fd0261b900cf05133
+      2.46.2: be3b042784bcabd5af20b48fd0261b900cf05133
     latest-changes: 2.43.1
     page-versions:
-    - name: 2.43.2 &rarr; 2.46.1
+    - name: 2.43.2 &rarr; 2.46.2
     - name: 2.43.1
       added: 2
       removed: 2
@@ -13414,9 +13474,10 @@ pages:
       2.45.2: db0953464f842de32c1aae2cb0f1f1110cec42ab
       2.46.0: db0953464f842de32c1aae2cb0f1f1110cec42ab
       2.46.1: db0953464f842de32c1aae2cb0f1f1110cec42ab
+      2.46.2: db0953464f842de32c1aae2cb0f1f1110cec42ab
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 2
       removed: 2
@@ -13711,9 +13772,10 @@ pages:
       2.45.2: 5507f76621a1487b884677a2e5eab67bf1ab3c55
       2.46.0: 5507f76621a1487b884677a2e5eab67bf1ab3c55
       2.46.1: 5507f76621a1487b884677a2e5eab67bf1ab3c55
+      2.46.2: 5507f76621a1487b884677a2e5eab67bf1ab3c55
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 4
       removed: 4
@@ -13967,9 +14029,10 @@ pages:
       2.45.2: e267feee1b2feaedfa4d34a28aad98cbaeac6d5d
       2.46.0: e267feee1b2feaedfa4d34a28aad98cbaeac6d5d
       2.46.1: e267feee1b2feaedfa4d34a28aad98cbaeac6d5d
+      2.46.2: e267feee1b2feaedfa4d34a28aad98cbaeac6d5d
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 2
       removed: 2
@@ -14247,9 +14310,10 @@ pages:
       2.45.2: f9636ce43e64dd89a460cb17a36152caf40e4272
       2.46.0: 601dce89f5701285953cf5dcef7ae2122a668ee2
       2.46.1: 601dce89f5701285953cf5dcef7ae2122a668ee2
+      2.46.2: 601dce89f5701285953cf5dcef7ae2122a668ee2
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 6
       removed: 2
@@ -14756,9 +14820,10 @@ pages:
       2.45.2: f5edd72d2125a3a3ced8b762a0f175e522670fbb
       2.46.0: 200e31900e0001f5122c9d1a1ade8e3c7720376b
       2.46.1: 200e31900e0001f5122c9d1a1ade8e3c7720376b
+      2.46.2: 200e31900e0001f5122c9d1a1ade8e3c7720376b
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 6
       removed: 2
@@ -15256,8 +15321,10 @@ pages:
       2.45.2: 9ea623b133565120f02b04a2f65c5da5b8a60650
       2.46.0: efe1fd7080b8fdb9ad68485d68cc63be0f6cbcb4
       2.46.1: 404ec08e034c85cd23b07709ab57fe0f43d6d4dd
+      2.46.2: 404ec08e034c85cd23b07709ab57fe0f43d6d4dd
     latest-changes: 2.46.1
     page-versions:
+    - name: 2.46.2
     - name: 2.46.1
       added: 1
       removed: 1
@@ -15812,9 +15879,10 @@ pages:
       2.45.2: 1f51f8c39bac75d095ee638f8d630d5b573dac52
       2.46.0: f32b46e6e765cefb9d9709a762d82fd48e5c2adb
       2.46.1: f32b46e6e765cefb9d9709a762d82fd48e5c2adb
+      2.46.2: f32b46e6e765cefb9d9709a762d82fd48e5c2adb
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 7
       removed: 1
@@ -16337,9 +16405,10 @@ pages:
       2.45.2: 53b71ebbead96e8a3a4637f91d9bdf93cb112cc7
       2.46.0: 53b71ebbead96e8a3a4637f91d9bdf93cb112cc7
       2.46.1: 53b71ebbead96e8a3a4637f91d9bdf93cb112cc7
+      2.46.2: 53b71ebbead96e8a3a4637f91d9bdf93cb112cc7
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 0
       removed: 1
@@ -16618,9 +16687,10 @@ pages:
       2.45.2: b3183479c616e2cc5fc4c153da99cab416bd3009
       2.46.0: b3183479c616e2cc5fc4c153da99cab416bd3009
       2.46.1: b3183479c616e2cc5fc4c153da99cab416bd3009
+      2.46.2: b3183479c616e2cc5fc4c153da99cab416bd3009
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 1
       removed: 1
@@ -16905,9 +16975,10 @@ pages:
       2.45.2: ba38170d35a19194a23d6b2c3d9e9b4b8516afa4
       2.46.0: ba38170d35a19194a23d6b2c3d9e9b4b8516afa4
       2.46.1: ba38170d35a19194a23d6b2c3d9e9b4b8516afa4
+      2.46.2: ba38170d35a19194a23d6b2c3d9e9b4b8516afa4
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 5
       removed: 3
@@ -17334,9 +17405,10 @@ pages:
       2.45.2: dc0619993b810bf1468af259da3363f3be6b71c9
       2.46.0: dc0619993b810bf1468af259da3363f3be6b71c9
       2.46.1: dc0619993b810bf1468af259da3363f3be6b71c9
+      2.46.2: dc0619993b810bf1468af259da3363f3be6b71c9
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -17589,8 +17661,12 @@ pages:
       2.45.2: b947fc4050ac2271b82ef81443cc344497b84829
       2.46.0: b947fc4050ac2271b82ef81443cc344497b84829
       2.46.1: b947fc4050ac2271b82ef81443cc344497b84829
-    latest-changes: 2.45.0
+      2.46.2: a13f478d7cb3fc25a95f0e14cff73cd5203e4b57
+    latest-changes: 2.46.2
     page-versions:
+    - name: 2.46.2
+      added: 3
+      removed: 2
     - name: 2.45.1 &rarr; 2.46.1
     - name: 2.45.0
       added: 4
@@ -17861,6 +17937,10 @@ pages:
       - 4
       - 4
       - 0
+      b947fc4050ac2271b82ef81443cc344497b84829..a13f478d7cb3fc25a95f0e14cff73cd5203e4b57:
+      - 3
+      - 2
+      - 3
     languages:
       fr: e082e04fc5db1c98aae1f9a19678cdbee45c9a6b
       pt_BR: e4d86016cd02b62d85d9aeb31192831e56c4128f
@@ -18055,9 +18135,10 @@ pages:
       2.45.2: 29cbb7e9b76ca46646ba0c22d12d1a1fd2cb1ad7
       2.46.0: 29cbb7e9b76ca46646ba0c22d12d1a1fd2cb1ad7
       2.46.1: 29cbb7e9b76ca46646ba0c22d12d1a1fd2cb1ad7
+      2.46.2: 29cbb7e9b76ca46646ba0c22d12d1a1fd2cb1ad7
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 3
       removed: 3
@@ -18362,9 +18443,10 @@ pages:
       2.45.2: 2099dedb6f39f1fab82df4167d22091a6ac14cbd
       2.46.0: 2099dedb6f39f1fab82df4167d22091a6ac14cbd
       2.46.1: 2099dedb6f39f1fab82df4167d22091a6ac14cbd
+      2.46.2: 2099dedb6f39f1fab82df4167d22091a6ac14cbd
     latest-changes: 2.35.0
     page-versions:
-    - name: 2.35.1 &rarr; 2.46.1
+    - name: 2.35.1 &rarr; 2.46.2
     - name: 2.35.0
       added: 5
       removed: 1
@@ -18611,9 +18693,10 @@ pages:
       2.45.2: b8138fe8e7e4599c5171f84c36c7da60cc5f98d7
       2.46.0: b8138fe8e7e4599c5171f84c36c7da60cc5f98d7
       2.46.1: b8138fe8e7e4599c5171f84c36c7da60cc5f98d7
+      2.46.2: b8138fe8e7e4599c5171f84c36c7da60cc5f98d7
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 4
       removed: 1
@@ -18973,9 +19056,10 @@ pages:
       2.45.2: b90599bd380f96e2e9f34e8caf1d8f6b2262b559
       2.46.0: 7e5335ebc0985bf335d8299c08d799aa448f2920
       2.46.1: 7e5335ebc0985bf335d8299c08d799aa448f2920
+      2.46.2: 7e5335ebc0985bf335d8299c08d799aa448f2920
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 6
       removed: 2
@@ -19503,9 +19587,10 @@ pages:
       2.45.2: 2f75bacdf9c0336458ce7b44afd983ca0b5f956d
       2.46.0: 2f75bacdf9c0336458ce7b44afd983ca0b5f956d
       2.46.1: 2f75bacdf9c0336458ce7b44afd983ca0b5f956d
+      2.46.2: 2f75bacdf9c0336458ce7b44afd983ca0b5f956d
     latest-changes: 2.0.5
     page-versions:
-    - name: 2.1.4 &rarr; 2.46.1
+    - name: 2.1.4 &rarr; 2.46.2
     - name: 2.0.5
       added: 8
       removed: 0
@@ -19705,9 +19790,10 @@ pages:
       2.45.2: 7ee06a67c2140baf9ddc68d88bbc3b6a0453eca3
       2.46.0: 7ee06a67c2140baf9ddc68d88bbc3b6a0453eca3
       2.46.1: 7ee06a67c2140baf9ddc68d88bbc3b6a0453eca3
+      2.46.2: 7ee06a67c2140baf9ddc68d88bbc3b6a0453eca3
     latest-changes: 2.45.2
     page-versions:
-    - name: 2.46.0 &rarr; 2.46.1
+    - name: 2.46.0 &rarr; 2.46.2
     - name: 2.45.2
       added: 0
       removed: 8
@@ -20072,9 +20158,10 @@ pages:
       2.45.2: bf4b078e09f963948c99b2cac8edecab818f7784
       2.46.0: bf4b078e09f963948c99b2cac8edecab818f7784
       2.46.1: bf4b078e09f963948c99b2cac8edecab818f7784
+      2.46.2: bf4b078e09f963948c99b2cac8edecab818f7784
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 8
       removed: 0
@@ -20416,9 +20503,10 @@ pages:
       2.45.2: 33918a057b37f17a84ecd8cfd5fa0bb2aab26054
       2.46.0: 33918a057b37f17a84ecd8cfd5fa0bb2aab26054
       2.46.1: 33918a057b37f17a84ecd8cfd5fa0bb2aab26054
+      2.46.2: 33918a057b37f17a84ecd8cfd5fa0bb2aab26054
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -20633,9 +20721,10 @@ pages:
       2.45.2: dd96902246f6a95e92029c83a7a5194520a2cb6f
       2.46.0: dd96902246f6a95e92029c83a7a5194520a2cb6f
       2.46.1: dd96902246f6a95e92029c83a7a5194520a2cb6f
+      2.46.2: dd96902246f6a95e92029c83a7a5194520a2cb6f
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 5
       removed: 3
@@ -21000,9 +21089,10 @@ pages:
       2.45.2: 2b75ef3d6a88840ade989227cebd6c53fa26d33d
       2.46.0: f0cbd417123f447b2aa226d698dde15bf9c8679a
       2.46.1: f0cbd417123f447b2aa226d698dde15bf9c8679a
+      2.46.2: f0cbd417123f447b2aa226d698dde15bf9c8679a
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 1
       removed: 1
@@ -21241,9 +21331,10 @@ pages:
       2.45.2: d8727c5c4a925c6e4c71b74795349e9a645fedcc
       2.46.0: d8727c5c4a925c6e4c71b74795349e9a645fedcc
       2.46.1: d8727c5c4a925c6e4c71b74795349e9a645fedcc
+      2.46.2: d8727c5c4a925c6e4c71b74795349e9a645fedcc
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -21489,9 +21580,10 @@ pages:
       2.45.2: 94a1e2dd7ba6275b08b8d87a60d1a6d84178dfae
       2.46.0: 94a1e2dd7ba6275b08b8d87a60d1a6d84178dfae
       2.46.1: 94a1e2dd7ba6275b08b8d87a60d1a6d84178dfae
+      2.46.2: 94a1e2dd7ba6275b08b8d87a60d1a6d84178dfae
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -21793,9 +21885,10 @@ pages:
       2.45.2: 35949f6c7459239f14a5c28d16217dcb6bb6882c
       2.46.0: 35949f6c7459239f14a5c28d16217dcb6bb6882c
       2.46.1: 35949f6c7459239f14a5c28d16217dcb6bb6882c
+      2.46.2: 35949f6c7459239f14a5c28d16217dcb6bb6882c
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -22034,9 +22127,10 @@ pages:
       2.45.2: 3186964bf973c270ec7afff229ff0370c98de548
       2.46.0: 3186964bf973c270ec7afff229ff0370c98de548
       2.46.1: 3186964bf973c270ec7afff229ff0370c98de548
+      2.46.2: 3186964bf973c270ec7afff229ff0370c98de548
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -22275,9 +22369,10 @@ pages:
       2.45.2: 0cd14a2642ef81d3ee6d9693206ef3d63ca0cc5a
       2.46.0: 0cd14a2642ef81d3ee6d9693206ef3d63ca0cc5a
       2.46.1: 0cd14a2642ef81d3ee6d9693206ef3d63ca0cc5a
+      2.46.2: 0cd14a2642ef81d3ee6d9693206ef3d63ca0cc5a
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -22508,9 +22603,10 @@ pages:
       2.45.2: 2a22262350510db42ba4f9fd3813a9fa27e9f3cb
       2.46.0: 2a22262350510db42ba4f9fd3813a9fa27e9f3cb
       2.46.1: 2a22262350510db42ba4f9fd3813a9fa27e9f3cb
+      2.46.2: 2a22262350510db42ba4f9fd3813a9fa27e9f3cb
     latest-changes: 2.43.1
     page-versions:
-    - name: 2.43.2 &rarr; 2.46.1
+    - name: 2.43.2 &rarr; 2.46.2
     - name: 2.43.1
       added: 1
       removed: 1
@@ -22779,9 +22875,10 @@ pages:
       2.45.2: 00eb314c1cacf3c8f0c4fe125a3b8f41702d3ee6
       2.46.0: 00eb314c1cacf3c8f0c4fe125a3b8f41702d3ee6
       2.46.1: 00eb314c1cacf3c8f0c4fe125a3b8f41702d3ee6
+      2.46.2: 00eb314c1cacf3c8f0c4fe125a3b8f41702d3ee6
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 6
       removed: 2
@@ -23068,9 +23165,10 @@ pages:
       2.45.2: 5e7a857f08e25bd644ed2d1c13c105937dbcc63a
       2.46.0: 5e7a857f08e25bd644ed2d1c13c105937dbcc63a
       2.46.1: 5e7a857f08e25bd644ed2d1c13c105937dbcc63a
+      2.46.2: 5e7a857f08e25bd644ed2d1c13c105937dbcc63a
     latest-changes: 2.35.0
     page-versions:
-    - name: 2.35.1 &rarr; 2.46.1
+    - name: 2.35.1 &rarr; 2.46.2
     - name: 2.35.0
       added: 1
       removed: 1
@@ -23280,9 +23378,10 @@ pages:
       2.45.2: 01d95ceead651f5607933d420495ece11812f01f
       2.46.0: 01d95ceead651f5607933d420495ece11812f01f
       2.46.1: 01d95ceead651f5607933d420495ece11812f01f
+      2.46.2: 01d95ceead651f5607933d420495ece11812f01f
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 4
       removed: 4
@@ -23607,9 +23706,10 @@ pages:
       2.45.2: ef4540f05095293b720c561485db49220fca0e77
       2.46.0: ef4540f05095293b720c561485db49220fca0e77
       2.46.1: ef4540f05095293b720c561485db49220fca0e77
+      2.46.2: ef4540f05095293b720c561485db49220fca0e77
     latest-changes: 2.21.0
     page-versions:
-    - name: 2.21.1 &rarr; 2.46.1
+    - name: 2.21.1 &rarr; 2.46.2
     - name: 2.21.0
       added: 2
       removed: 1
@@ -23832,9 +23932,10 @@ pages:
       2.45.2: ab203158faff40ab5a2e6d9fda7a855ed300d1f5
       2.46.0: dd05cc3dff234862b5493972d69dae4e1be267d4
       2.46.1: dd05cc3dff234862b5493972d69dae4e1be267d4
+      2.46.2: dd05cc3dff234862b5493972d69dae4e1be267d4
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 6
       removed: 2
@@ -24428,8 +24529,10 @@ pages:
       2.45.2: 46989226c8c1178a91903a03b2ca73298ecaca14
       2.46.0: 46989226c8c1178a91903a03b2ca73298ecaca14
       2.46.1: a4c82967e0d3995c74b0fe4715b0a60ae16b6283
+      2.46.2: a4c82967e0d3995c74b0fe4715b0a60ae16b6283
     latest-changes: 2.46.1
     page-versions:
+    - name: 2.46.2
     - name: 2.46.1
       added: 3
       removed: 3
@@ -24798,9 +24901,10 @@ pages:
       2.45.2: c10da6b10becca4ed5a9b0ed6cd2fd8bb193c70f
       2.46.0: 3a78b32eb402064556f9de21f13db229bf3d2afd
       2.46.1: 3a78b32eb402064556f9de21f13db229bf3d2afd
+      2.46.2: 3a78b32eb402064556f9de21f13db229bf3d2afd
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 5
       removed: 3
@@ -25079,9 +25183,10 @@ pages:
       2.45.2: 82ee02dac9f136a08dfe0c92166eabc69a52a8a8
       2.46.0: 82ee02dac9f136a08dfe0c92166eabc69a52a8a8
       2.46.1: 82ee02dac9f136a08dfe0c92166eabc69a52a8a8
+      2.46.2: 82ee02dac9f136a08dfe0c92166eabc69a52a8a8
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 4
       removed: 4
@@ -25327,9 +25432,10 @@ pages:
       2.45.2: d9566086d5dbb92633db690c14008ff07785346a
       2.46.0: d9566086d5dbb92633db690c14008ff07785346a
       2.46.1: d9566086d5dbb92633db690c14008ff07785346a
+      2.46.2: d9566086d5dbb92633db690c14008ff07785346a
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -25584,9 +25690,10 @@ pages:
       2.45.2: 5fe8a0c7082be9c25f74f7247a857e833980a4d9
       2.46.0: 5fe8a0c7082be9c25f74f7247a857e833980a4d9
       2.46.1: 5fe8a0c7082be9c25f74f7247a857e833980a4d9
+      2.46.2: 5fe8a0c7082be9c25f74f7247a857e833980a4d9
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -25801,9 +25908,10 @@ pages:
       2.45.2: 3e062b11f43e62b3a46a92fe4b5b18fe596f0a77
       2.46.0: 3e062b11f43e62b3a46a92fe4b5b18fe596f0a77
       2.46.1: 3e062b11f43e62b3a46a92fe4b5b18fe596f0a77
+      2.46.2: 3e062b11f43e62b3a46a92fe4b5b18fe596f0a77
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -26057,9 +26165,10 @@ pages:
       2.45.2: cfe7f2bb66b69c257bf52a63f2da4a1b729f801b
       2.46.0: cfe7f2bb66b69c257bf52a63f2da4a1b729f801b
       2.46.1: cfe7f2bb66b69c257bf52a63f2da4a1b729f801b
+      2.46.2: cfe7f2bb66b69c257bf52a63f2da4a1b729f801b
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 6
       removed: 0
@@ -26289,9 +26398,10 @@ pages:
       2.45.2: 523dd2b13cacffb4bc9895b9d4b406f9541a6c87
       2.46.0: 523dd2b13cacffb4bc9895b9d4b406f9541a6c87
       2.46.1: 523dd2b13cacffb4bc9895b9d4b406f9541a6c87
+      2.46.2: 523dd2b13cacffb4bc9895b9d4b406f9541a6c87
     latest-changes: 2.35.0
     page-versions:
-    - name: 2.35.1 &rarr; 2.46.1
+    - name: 2.35.1 &rarr; 2.46.2
     - name: 2.35.0
       added: 1
       removed: 1
@@ -26505,9 +26615,10 @@ pages:
       2.45.2: b4afbaa801709f37927ad5525967847da103e8d1
       2.46.0: b4afbaa801709f37927ad5525967847da103e8d1
       2.46.1: b4afbaa801709f37927ad5525967847da103e8d1
+      2.46.2: b4afbaa801709f37927ad5525967847da103e8d1
     latest-changes: 2.0.5
     page-versions:
-    - name: 2.1.4 &rarr; 2.46.1
+    - name: 2.1.4 &rarr; 2.46.2
     - name: 2.0.5
       added: 8
       removed: 0
@@ -26707,9 +26818,10 @@ pages:
       2.45.2: 027433a8d0fee27a546d2c33d9298babfca2479d
       2.46.0: b77a82cbc36b8c7bf57bc5357b393d7bce449759
       2.46.1: b77a82cbc36b8c7bf57bc5357b393d7bce449759
+      2.46.2: b77a82cbc36b8c7bf57bc5357b393d7bce449759
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 5
       removed: 0
@@ -26964,9 +27076,10 @@ pages:
       2.45.2: 8afda7306cadc8d848149d64e4a91ee7433e575d
       2.46.0: 8afda7306cadc8d848149d64e4a91ee7433e575d
       2.46.1: 8afda7306cadc8d848149d64e4a91ee7433e575d
+      2.46.2: 8afda7306cadc8d848149d64e4a91ee7433e575d
     latest-changes: 2.43.1
     page-versions:
-    - name: 2.43.2 &rarr; 2.46.1
+    - name: 2.43.2 &rarr; 2.46.2
     - name: 2.43.1
       added: 4
       removed: 4
@@ -27416,9 +27529,10 @@ pages:
       2.45.2: 287956d18f2db551f853548183d7fa826059c6f8
       2.46.0: 287956d18f2db551f853548183d7fa826059c6f8
       2.46.1: 287956d18f2db551f853548183d7fa826059c6f8
+      2.46.2: 287956d18f2db551f853548183d7fa826059c6f8
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -27641,9 +27755,10 @@ pages:
       2.45.2: 0e930886b339c9dec28f1c3e2ea665894a386659
       2.46.0: 0e930886b339c9dec28f1c3e2ea665894a386659
       2.46.1: 0e930886b339c9dec28f1c3e2ea665894a386659
+      2.46.2: 0e930886b339c9dec28f1c3e2ea665894a386659
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 5
       removed: 3
@@ -27929,9 +28044,10 @@ pages:
       2.45.2: 96accbe433a821b80ca02cd76862b4d154ae105a
       2.46.0: 96accbe433a821b80ca02cd76862b4d154ae105a
       2.46.1: 96accbe433a821b80ca02cd76862b4d154ae105a
+      2.46.2: 96accbe433a821b80ca02cd76862b4d154ae105a
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 3
       removed: 3
@@ -28170,9 +28286,10 @@ pages:
       2.45.2: 7079c2a886c8b33f77c2c0d47a887674b7f8157b
       2.46.0: 7079c2a886c8b33f77c2c0d47a887674b7f8157b
       2.46.1: 7079c2a886c8b33f77c2c0d47a887674b7f8157b
+      2.46.2: 7079c2a886c8b33f77c2c0d47a887674b7f8157b
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -28403,9 +28520,10 @@ pages:
       2.45.2: bb463d99b5fbb11875d2822aaae60fdb1df9b062
       2.46.0: bb463d99b5fbb11875d2822aaae60fdb1df9b062
       2.46.1: bb463d99b5fbb11875d2822aaae60fdb1df9b062
+      2.46.2: bb463d99b5fbb11875d2822aaae60fdb1df9b062
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 1
       removed: 1
@@ -28637,9 +28755,10 @@ pages:
       2.45.2: 247079cffd5aabcf29e0fc882ae42b5a27712340
       2.46.0: 247079cffd5aabcf29e0fc882ae42b5a27712340
       2.46.1: 247079cffd5aabcf29e0fc882ae42b5a27712340
+      2.46.2: 247079cffd5aabcf29e0fc882ae42b5a27712340
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -28878,9 +28997,10 @@ pages:
       2.45.2: f4a0735c0fc28791052c111b1a94038750c6a629
       2.46.0: f4a0735c0fc28791052c111b1a94038750c6a629
       2.46.1: f4a0735c0fc28791052c111b1a94038750c6a629
+      2.46.2: f4a0735c0fc28791052c111b1a94038750c6a629
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 1
       removed: 1
@@ -29190,9 +29310,10 @@ pages:
       2.45.2: 1a7dfe90bde58ed0a84e0f27ecca8d7dfe01228a
       2.46.0: 1a7dfe90bde58ed0a84e0f27ecca8d7dfe01228a
       2.46.1: 1a7dfe90bde58ed0a84e0f27ecca8d7dfe01228a
+      2.46.2: 1a7dfe90bde58ed0a84e0f27ecca8d7dfe01228a
     latest-changes: 2.37.0
     page-versions:
-    - name: 2.37.1 &rarr; 2.46.1
+    - name: 2.37.1 &rarr; 2.46.2
     - name: 2.37.0
       added: 8
       removed: 0
@@ -29528,9 +29649,10 @@ pages:
       2.45.2: 0154cb0d9770171d0c49ce3e48f7b561e6a4b3e1
       2.46.0: 0154cb0d9770171d0c49ce3e48f7b561e6a4b3e1
       2.46.1: 0154cb0d9770171d0c49ce3e48f7b561e6a4b3e1
+      2.46.2: 0154cb0d9770171d0c49ce3e48f7b561e6a4b3e1
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 3
       removed: 5
@@ -29878,9 +30000,10 @@ pages:
       2.45.2: d3e402c0e1cc92321370a488a3909ba5732af524
       2.46.0: d3e402c0e1cc92321370a488a3909ba5732af524
       2.46.1: d3e402c0e1cc92321370a488a3909ba5732af524
+      2.46.2: d3e402c0e1cc92321370a488a3909ba5732af524
     latest-changes: 2.41.0
     page-versions:
-    - name: 2.41.1 &rarr; 2.46.1
+    - name: 2.41.1 &rarr; 2.46.2
     - name: 2.41.0
       added: 8
       removed: 0
@@ -30103,9 +30226,10 @@ pages:
       2.45.2: 74fb771cd74171c069e28e1ffddfdcd561d1786f
       2.46.0: 74fb771cd74171c069e28e1ffddfdcd561d1786f
       2.46.1: 74fb771cd74171c069e28e1ffddfdcd561d1786f
+      2.46.2: 74fb771cd74171c069e28e1ffddfdcd561d1786f
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 7
       removed: 1
@@ -30413,9 +30537,10 @@ pages:
       2.45.2: 9bab4f5911b70e67d6ad55a6c1e9c3a9da898d5c
       2.46.0: 9bab4f5911b70e67d6ad55a6c1e9c3a9da898d5c
       2.46.1: 9bab4f5911b70e67d6ad55a6c1e9c3a9da898d5c
+      2.46.2: 9bab4f5911b70e67d6ad55a6c1e9c3a9da898d5c
     latest-changes: 2.39.0
     page-versions:
-    - name: 2.39.1 &rarr; 2.46.1
+    - name: 2.39.1 &rarr; 2.46.2
     - name: 2.39.0
       added: 5
       removed: 3
@@ -30645,9 +30770,10 @@ pages:
       2.45.2: c491057d76095353b3825a90ffc82963a16dbe7e
       2.46.0: c491057d76095353b3825a90ffc82963a16dbe7e
       2.46.1: c491057d76095353b3825a90ffc82963a16dbe7e
+      2.46.2: c491057d76095353b3825a90ffc82963a16dbe7e
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -30870,9 +30996,10 @@ pages:
       2.45.2: 8d1f781904a5f1868b0899c1e3c6d420d57062a4
       2.46.0: 8d1f781904a5f1868b0899c1e3c6d420d57062a4
       2.46.1: 8d1f781904a5f1868b0899c1e3c6d420d57062a4
+      2.46.2: 8d1f781904a5f1868b0899c1e3c6d420d57062a4
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -31095,8 +31222,12 @@ pages:
       2.45.2: 8add7054042abccc5050fa60647027280e00f65b
       2.46.0: 8add7054042abccc5050fa60647027280e00f65b
       2.46.1: 8add7054042abccc5050fa60647027280e00f65b
-    latest-changes: 2.45.0
+      2.46.2: d470969260e7a605742fb34733463f6434be4872
+    latest-changes: 2.46.2
     page-versions:
+    - name: 2.46.2
+      added: 3
+      removed: 2
     - name: 2.45.1 &rarr; 2.46.1
     - name: 2.45.0
       added: 4
@@ -31407,6 +31538,10 @@ pages:
       - 4
       - 4
       - 0
+      8add7054042abccc5050fa60647027280e00f65b..d470969260e7a605742fb34733463f6434be4872:
+      - 3
+      - 2
+      - 3
     languages:
       fr: 0b290a71c679a399182094de972ac5ec051aa08e
       pt_BR: c9c789180072cd35af25c5b612425bda22fd5346
@@ -31601,9 +31736,10 @@ pages:
       2.45.2: 24a92c0b37f0c407a4888682d740dbbb4ba76d46
       2.46.0: 24a92c0b37f0c407a4888682d740dbbb4ba76d46
       2.46.1: 24a92c0b37f0c407a4888682d740dbbb4ba76d46
+      2.46.2: 24a92c0b37f0c407a4888682d740dbbb4ba76d46
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 4
       removed: 4
@@ -32047,9 +32183,10 @@ pages:
       2.45.2: a0e37ab85cac3328f6813c05a1e423a6e2c89439
       2.46.0: a0e37ab85cac3328f6813c05a1e423a6e2c89439
       2.46.1: a0e37ab85cac3328f6813c05a1e423a6e2c89439
+      2.46.2: a0e37ab85cac3328f6813c05a1e423a6e2c89439
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -32288,9 +32425,10 @@ pages:
       2.45.2: 1916efce3ad6ba9e04057c1189b2de03333406d9
       2.46.0: 1916efce3ad6ba9e04057c1189b2de03333406d9
       2.46.1: 1916efce3ad6ba9e04057c1189b2de03333406d9
+      2.46.2: 1916efce3ad6ba9e04057c1189b2de03333406d9
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 3
       removed: 3
@@ -32598,8 +32736,10 @@ pages:
       2.45.2: 9774f45dc2411b5bbc9f28f53688f3cdbc9d64be
       2.46.0: 9774f45dc2411b5bbc9f28f53688f3cdbc9d64be
       2.46.1: ab19c78a044ca4de1c17e5c350889d6bd207681c
+      2.46.2: ab19c78a044ca4de1c17e5c350889d6bd207681c
     latest-changes: 2.46.1
     page-versions:
+    - name: 2.46.2
     - name: 2.46.1
       added: 1
       removed: 1
@@ -33154,9 +33294,10 @@ pages:
       2.45.2: d4d8326a6c438fc1b45f813bff7a309caed85a7d
       2.46.0: d4d8326a6c438fc1b45f813bff7a309caed85a7d
       2.46.1: d4d8326a6c438fc1b45f813bff7a309caed85a7d
+      2.46.2: d4d8326a6c438fc1b45f813bff7a309caed85a7d
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -33426,9 +33567,10 @@ pages:
       2.45.2: 83ab78afb13eddc0c109ded83f14251c305437df
       2.46.0: 83ab78afb13eddc0c109ded83f14251c305437df
       2.46.1: 83ab78afb13eddc0c109ded83f14251c305437df
+      2.46.2: 83ab78afb13eddc0c109ded83f14251c305437df
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 3
       removed: 0
@@ -33710,9 +33852,10 @@ pages:
       2.45.2: 61cadb3e5af77953c513f5e23e0f85ee493fb820
       2.46.0: 61cadb3e5af77953c513f5e23e0f85ee493fb820
       2.46.1: 61cadb3e5af77953c513f5e23e0f85ee493fb820
+      2.46.2: 61cadb3e5af77953c513f5e23e0f85ee493fb820
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -33942,9 +34085,10 @@ pages:
       2.45.2: 9d41ace8e22584f332f5d42c52dd6f6b0de38bee
       2.46.0: 9d41ace8e22584f332f5d42c52dd6f6b0de38bee
       2.46.1: 9d41ace8e22584f332f5d42c52dd6f6b0de38bee
+      2.46.2: 9d41ace8e22584f332f5d42c52dd6f6b0de38bee
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -34230,9 +34374,10 @@ pages:
       2.45.2: 106236ca717c0be5169dd7b4b14934c91373f6bc
       2.46.0: 106236ca717c0be5169dd7b4b14934c91373f6bc
       2.46.1: 106236ca717c0be5169dd7b4b14934c91373f6bc
+      2.46.2: 106236ca717c0be5169dd7b4b14934c91373f6bc
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 1
       removed: 1
@@ -34534,9 +34679,10 @@ pages:
       2.45.2: cd01864f13fe7aaed93aec6539e9214a3930e1c7
       2.46.0: cd01864f13fe7aaed93aec6539e9214a3930e1c7
       2.46.1: cd01864f13fe7aaed93aec6539e9214a3930e1c7
+      2.46.2: cd01864f13fe7aaed93aec6539e9214a3930e1c7
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 8
       removed: 0
@@ -34876,9 +35022,10 @@ pages:
       2.45.2: 52b665af515b61e3164ac298ac6a527d19a2d10b
       2.46.0: 52b665af515b61e3164ac298ac6a527d19a2d10b
       2.46.1: 52b665af515b61e3164ac298ac6a527d19a2d10b
+      2.46.2: 52b665af515b61e3164ac298ac6a527d19a2d10b
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 3
       removed: 3
@@ -35123,9 +35270,10 @@ pages:
       2.45.2: 9526440f6f639faf3d769c52e27484cddfe784d3
       2.46.0: 9526440f6f639faf3d769c52e27484cddfe784d3
       2.46.1: 9526440f6f639faf3d769c52e27484cddfe784d3
+      2.46.2: 9526440f6f639faf3d769c52e27484cddfe784d3
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -35355,9 +35503,10 @@ pages:
       2.45.2: 7de9d7cd34899cf5821f1ed276c2e9cea31bc888
       2.46.0: 7de9d7cd34899cf5821f1ed276c2e9cea31bc888
       2.46.1: 7de9d7cd34899cf5821f1ed276c2e9cea31bc888
+      2.46.2: 7de9d7cd34899cf5821f1ed276c2e9cea31bc888
     latest-changes: 2.39.0
     page-versions:
-    - name: 2.39.1 &rarr; 2.46.1
+    - name: 2.39.1 &rarr; 2.46.2
     - name: 2.39.0
       added: 1
       removed: 1
@@ -35603,9 +35752,10 @@ pages:
       2.45.2: a1b9d918d36224fa346f0534c4f374e4015225b5
       2.46.0: a1b9d918d36224fa346f0534c4f374e4015225b5
       2.46.1: a1b9d918d36224fa346f0534c4f374e4015225b5
+      2.46.2: a1b9d918d36224fa346f0534c4f374e4015225b5
     latest-changes: 2.39.3
     page-versions:
-    - name: 2.39.4 &rarr; 2.46.1
+    - name: 2.39.4 &rarr; 2.46.2
     - name: 2.39.3
       added: 2
       removed: 1
@@ -35898,9 +36048,10 @@ pages:
       2.45.2: b847579e69d4ea2a369d5bccfad0b5e5f2884e28
       2.46.0: b847579e69d4ea2a369d5bccfad0b5e5f2884e28
       2.46.1: b847579e69d4ea2a369d5bccfad0b5e5f2884e28
+      2.46.2: b847579e69d4ea2a369d5bccfad0b5e5f2884e28
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 5
       removed: 3
@@ -36441,9 +36592,10 @@ pages:
       2.45.2: 22c95bb4a06ede6c3b7c9870d1c9d2d4a00be32f
       2.46.0: ad2e1b2217c6adf64fbe9c62cef3a1767aa9cf86
       2.46.1: ad2e1b2217c6adf64fbe9c62cef3a1767aa9cf86
+      2.46.2: ad2e1b2217c6adf64fbe9c62cef3a1767aa9cf86
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 7
       removed: 1
@@ -36880,9 +37032,10 @@ pages:
       2.45.2: 18e1fc3d5b9c0a729515171fd50ad9dfa988ac55
       2.46.0: 18e1fc3d5b9c0a729515171fd50ad9dfa988ac55
       2.46.1: 18e1fc3d5b9c0a729515171fd50ad9dfa988ac55
+      2.46.2: 18e1fc3d5b9c0a729515171fd50ad9dfa988ac55
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 2
       removed: 2
@@ -37175,9 +37328,10 @@ pages:
       2.45.2: 92a24f988293d638a83243edc563bca5d817e313
       2.46.0: 92a24f988293d638a83243edc563bca5d817e313
       2.46.1: 92a24f988293d638a83243edc563bca5d817e313
+      2.46.2: 92a24f988293d638a83243edc563bca5d817e313
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -37430,9 +37584,10 @@ pages:
       2.45.2: ae8ec07c67eaa44ff95a43f3b6a345542c99cc52
       2.46.0: ae8ec07c67eaa44ff95a43f3b6a345542c99cc52
       2.46.1: ae8ec07c67eaa44ff95a43f3b6a345542c99cc52
+      2.46.2: ae8ec07c67eaa44ff95a43f3b6a345542c99cc52
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 4
       removed: 4
@@ -37854,9 +38009,10 @@ pages:
       2.45.2: 200e6ec7093794ff832653267f587e3b9b809e23
       2.46.0: 200e6ec7093794ff832653267f587e3b9b809e23
       2.46.1: 200e6ec7093794ff832653267f587e3b9b809e23
+      2.46.2: 200e6ec7093794ff832653267f587e3b9b809e23
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -38133,9 +38289,10 @@ pages:
       2.45.2: 95d86d71a3967fdf0cdb94ca56c1ed443ee7ab1d
       2.46.0: 95d86d71a3967fdf0cdb94ca56c1ed443ee7ab1d
       2.46.1: 95d86d71a3967fdf0cdb94ca56c1ed443ee7ab1d
+      2.46.2: 95d86d71a3967fdf0cdb94ca56c1ed443ee7ab1d
     latest-changes: 2.0.5
     page-versions:
-    - name: 2.1.4 &rarr; 2.46.1
+    - name: 2.1.4 &rarr; 2.46.2
     - name: 2.0.5
       added: 8
       removed: 0
@@ -38332,9 +38489,10 @@ pages:
       2.45.2: faf2fae41df4692d3a4ec0c0a7d15a3def078481
       2.46.0: faf2fae41df4692d3a4ec0c0a7d15a3def078481
       2.46.1: faf2fae41df4692d3a4ec0c0a7d15a3def078481
+      2.46.2: faf2fae41df4692d3a4ec0c0a7d15a3def078481
     latest-changes: 2.0.5
     page-versions:
-    - name: 2.1.4 &rarr; 2.46.1
+    - name: 2.1.4 &rarr; 2.46.2
     - name: 2.0.5
       added: 8
       removed: 0
@@ -38531,9 +38689,10 @@ pages:
       2.45.2: f656e99d17fcfbb613587f1c514bb042293b56d0
       2.46.0: f656e99d17fcfbb613587f1c514bb042293b56d0
       2.46.1: f656e99d17fcfbb613587f1c514bb042293b56d0
+      2.46.2: f656e99d17fcfbb613587f1c514bb042293b56d0
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -38747,9 +38906,10 @@ pages:
       2.45.2: 5e4ba7e6467a5bff033603d1c36e108aaad5c2cb
       2.46.0: 5e4ba7e6467a5bff033603d1c36e108aaad5c2cb
       2.46.1: 5e4ba7e6467a5bff033603d1c36e108aaad5c2cb
+      2.46.2: 5e4ba7e6467a5bff033603d1c36e108aaad5c2cb
     latest-changes: 2.18.0
     page-versions:
-    - name: 2.18.1 &rarr; 2.46.1
+    - name: 2.18.1 &rarr; 2.46.2
     - name: 2.18.0
       added: 2
       removed: 2
@@ -38970,9 +39130,10 @@ pages:
       2.45.2: 94326746dd3f65444925c054c11a1d9ea80b076b
       2.46.0: 94326746dd3f65444925c054c11a1d9ea80b076b
       2.46.1: 94326746dd3f65444925c054c11a1d9ea80b076b
+      2.46.2: 94326746dd3f65444925c054c11a1d9ea80b076b
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 6
       removed: 2
@@ -39345,9 +39506,10 @@ pages:
       2.45.2: 9cea4af53c6931ec3e313ec9db8b138f70ac4de4
       2.46.0: e7d1e37cca37e7c25e9057cb349fcfb8d4151cb9
       2.46.1: e7d1e37cca37e7c25e9057cb349fcfb8d4151cb9
+      2.46.2: e7d1e37cca37e7c25e9057cb349fcfb8d4151cb9
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 1
       removed: 1
@@ -39617,9 +39779,10 @@ pages:
       2.45.2: de6d774f68b10fd43019fe238f62ca6b0aa48ce1
       2.46.0: de6d774f68b10fd43019fe238f62ca6b0aa48ce1
       2.46.1: de6d774f68b10fd43019fe238f62ca6b0aa48ce1
+      2.46.2: de6d774f68b10fd43019fe238f62ca6b0aa48ce1
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 5
       removed: 3
@@ -39857,9 +40020,10 @@ pages:
       2.45.2: 380802c616543a6f3ff5b3446de10e055cfabdf6
       2.46.0: 9f304894364e29dcf3b11de716808b2171e8bf7a
       2.46.1: 9f304894364e29dcf3b11de716808b2171e8bf7a
+      2.46.2: 9f304894364e29dcf3b11de716808b2171e8bf7a
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 4
       removed: 4
@@ -40121,9 +40285,10 @@ pages:
       2.45.2: 9ba7419af3a31d07cca86465fc62ac43e47c549e
       2.46.0: 643b6c1fb5b45b759f275d0864537d532cd8dc82
       2.46.1: 643b6c1fb5b45b759f275d0864537d532cd8dc82
+      2.46.2: 643b6c1fb5b45b759f275d0864537d532cd8dc82
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 6
       removed: 2
@@ -40649,9 +40814,10 @@ pages:
       2.45.2: e4b3706c5bfe6923a5dcc4035aa3f523c0a11656
       2.46.0: e4b3706c5bfe6923a5dcc4035aa3f523c0a11656
       2.46.1: e4b3706c5bfe6923a5dcc4035aa3f523c0a11656
+      2.46.2: e4b3706c5bfe6923a5dcc4035aa3f523c0a11656
     latest-changes: 2.35.0
     page-versions:
-    - name: 2.35.1 &rarr; 2.46.1
+    - name: 2.35.1 &rarr; 2.46.2
     - name: 2.35.0
       added: 1
       removed: 1
@@ -40868,9 +41034,10 @@ pages:
       2.45.2: 68ce698cc0895b55ed417d081eb09e6d765ea51c
       2.46.0: 68ce698cc0895b55ed417d081eb09e6d765ea51c
       2.46.1: 68ce698cc0895b55ed417d081eb09e6d765ea51c
+      2.46.2: 68ce698cc0895b55ed417d081eb09e6d765ea51c
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -41209,9 +41376,10 @@ pages:
       2.45.2: f47a2439b5ef738dbfdf5242233f566f3b74ff75
       2.46.0: f47a2439b5ef738dbfdf5242233f566f3b74ff75
       2.46.1: f47a2439b5ef738dbfdf5242233f566f3b74ff75
+      2.46.2: f47a2439b5ef738dbfdf5242233f566f3b74ff75
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 3
       removed: 1
@@ -41590,9 +41758,10 @@ pages:
       2.45.2: a22779ce8a051359cf39164b92c0c3e96c10015c
       2.46.0: a22779ce8a051359cf39164b92c0c3e96c10015c
       2.46.1: a22779ce8a051359cf39164b92c0c3e96c10015c
+      2.46.2: a22779ce8a051359cf39164b92c0c3e96c10015c
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 3
       removed: 3
@@ -41821,9 +41990,10 @@ pages:
       2.45.2: 320b32532cce2c08101618b6017db217f10a6f61
       2.46.0: 320b32532cce2c08101618b6017db217f10a6f61
       2.46.1: 320b32532cce2c08101618b6017db217f10a6f61
+      2.46.2: 320b32532cce2c08101618b6017db217f10a6f61
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 2
       removed: 2
@@ -42184,9 +42354,10 @@ pages:
       2.45.2: '02148ddbae8718957bd63abdc674c658ad002ec0'
       2.46.0: '02148ddbae8718957bd63abdc674c658ad002ec0'
       2.46.1: '02148ddbae8718957bd63abdc674c658ad002ec0'
+      2.46.2: '02148ddbae8718957bd63abdc674c658ad002ec0'
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 4
       removed: 4
@@ -42537,9 +42708,10 @@ pages:
       2.45.2: 94a874723e8f280a4bcb810223e9e772d268fc86
       2.46.0: 94a874723e8f280a4bcb810223e9e772d268fc86
       2.46.1: 94a874723e8f280a4bcb810223e9e772d268fc86
+      2.46.2: 94a874723e8f280a4bcb810223e9e772d268fc86
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -42753,9 +42925,10 @@ pages:
       2.45.2: 58e0debeae46577d7e3791f6c564d5097fb9d85b
       2.46.0: a87f3d0a51899408199b3626776704f9ec7d43c2
       2.46.1: a87f3d0a51899408199b3626776704f9ec7d43c2
+      2.46.2: a87f3d0a51899408199b3626776704f9ec7d43c2
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 7
       removed: 1
@@ -43169,9 +43342,10 @@ pages:
       2.45.2: 52b8f44c8b9fa8334d21fb75d33b1c8251396066
       2.46.0: 52b8f44c8b9fa8334d21fb75d33b1c8251396066
       2.46.1: 52b8f44c8b9fa8334d21fb75d33b1c8251396066
+      2.46.2: 52b8f44c8b9fa8334d21fb75d33b1c8251396066
     latest-changes: 2.13.7
     page-versions:
-    - name: 2.14.6 &rarr; 2.46.1
+    - name: 2.14.6 &rarr; 2.46.2
     - name: 2.13.7
       added: 1
       removed: 1
@@ -43382,9 +43556,10 @@ pages:
       2.45.2: e5594236a266c0cd48b1563ec59bbaf2e7ef2f9d
       2.46.0: e5594236a266c0cd48b1563ec59bbaf2e7ef2f9d
       2.46.1: e5594236a266c0cd48b1563ec59bbaf2e7ef2f9d
+      2.46.2: e5594236a266c0cd48b1563ec59bbaf2e7ef2f9d
     latest-changes: 2.0.5
     page-versions:
-    - name: 2.1.4 &rarr; 2.46.1
+    - name: 2.1.4 &rarr; 2.46.2
     - name: 2.0.5
       added: 8
       removed: 0
@@ -43581,9 +43756,10 @@ pages:
       2.45.2: 81bd5ac30c3e2a378082e057dab607e1645ac919
       2.46.0: 81bd5ac30c3e2a378082e057dab607e1645ac919
       2.46.1: 81bd5ac30c3e2a378082e057dab607e1645ac919
+      2.46.2: 81bd5ac30c3e2a378082e057dab607e1645ac919
     latest-changes: 2.11.4
     page-versions:
-    - name: 2.12.5 &rarr; 2.46.1
+    - name: 2.12.5 &rarr; 2.46.2
     - name: 2.11.4
       added: 3
       removed: 0
@@ -43805,9 +43981,10 @@ pages:
       2.45.2: 344e77cac9ac24bd11801ec5a7539255511dcb75
       2.46.0: a5b7d626284bef69b2b5d533240c0349c6e71f82
       2.46.1: a5b7d626284bef69b2b5d533240c0349c6e71f82
+      2.46.2: a5b7d626284bef69b2b5d533240c0349c6e71f82
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 1
       removed: 0
@@ -44163,9 +44340,10 @@ pages:
       2.45.2: 5669a3cdaa96dde19c8abcdf51c17ff7235d52e7
       2.46.0: d5f53d0fdf3f9d33e513e38217c4c891ffecdbcd
       2.46.1: d5f53d0fdf3f9d33e513e38217c4c891ffecdbcd
+      2.46.2: d5f53d0fdf3f9d33e513e38217c4c891ffecdbcd
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 8
       removed: 0
@@ -44442,9 +44620,10 @@ pages:
       2.45.2: 9633f438a80b9093b1bfb1c0c27cc454a558a942
       2.46.0: 9633f438a80b9093b1bfb1c0c27cc454a558a942
       2.46.1: 9633f438a80b9093b1bfb1c0c27cc454a558a942
+      2.46.2: 9633f438a80b9093b1bfb1c0c27cc454a558a942
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -44666,9 +44845,10 @@ pages:
       2.45.2: f69eda69fdcfb686c59c4baa7caf623dc7319655
       2.46.0: f69eda69fdcfb686c59c4baa7caf623dc7319655
       2.46.1: f69eda69fdcfb686c59c4baa7caf623dc7319655
+      2.46.2: f69eda69fdcfb686c59c4baa7caf623dc7319655
     latest-changes: 2.39.0
     page-versions:
-    - name: 2.39.1 &rarr; 2.46.1
+    - name: 2.39.1 &rarr; 2.46.2
     - name: 2.39.0
       added: 2
       removed: 2
@@ -44882,9 +45062,10 @@ pages:
       2.45.2: 70e2a3ce71f26c5190fa57680b6cdb0304a740ab
       2.46.0: 70e2a3ce71f26c5190fa57680b6cdb0304a740ab
       2.46.1: 70e2a3ce71f26c5190fa57680b6cdb0304a740ab
+      2.46.2: 70e2a3ce71f26c5190fa57680b6cdb0304a740ab
     latest-changes: 2.45.1
     page-versions:
-    - name: 2.45.2 &rarr; 2.46.1
+    - name: 2.45.2 &rarr; 2.46.2
     - name: 2.45.1
       added: 8
       removed: 0
@@ -45191,9 +45372,10 @@ pages:
       2.45.2: b3509775dd0268fc34cd4b2645c729b121f95262
       2.46.0: b3509775dd0268fc34cd4b2645c729b121f95262
       2.46.1: b3509775dd0268fc34cd4b2645c729b121f95262
+      2.46.2: b3509775dd0268fc34cd4b2645c729b121f95262
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -45439,9 +45621,10 @@ pages:
       2.45.2: d2735ffa90090278cfbb9c55a04b494a6ca19443
       2.46.0: d2735ffa90090278cfbb9c55a04b494a6ca19443
       2.46.1: d2735ffa90090278cfbb9c55a04b494a6ca19443
+      2.46.2: d2735ffa90090278cfbb9c55a04b494a6ca19443
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 3
       removed: 3
@@ -45663,9 +45846,10 @@ pages:
       2.45.2: 5d0bd100b15ae44c345ab3f4ebbaed69030d787a
       2.46.0: 5d0bd100b15ae44c345ab3f4ebbaed69030d787a
       2.46.1: 5d0bd100b15ae44c345ab3f4ebbaed69030d787a
+      2.46.2: 5d0bd100b15ae44c345ab3f4ebbaed69030d787a
     latest-changes: 2.39.0
     page-versions:
-    - name: 2.39.1 &rarr; 2.46.1
+    - name: 2.39.1 &rarr; 2.46.2
     - name: 2.39.0
       added: 1
       removed: 1
@@ -45888,9 +46072,10 @@ pages:
       2.45.2: ff9ffee69bd02d48fc63cfbca65a45fd8bbe2b9e
       2.46.0: ff9ffee69bd02d48fc63cfbca65a45fd8bbe2b9e
       2.46.1: ff9ffee69bd02d48fc63cfbca65a45fd8bbe2b9e
+      2.46.2: ff9ffee69bd02d48fc63cfbca65a45fd8bbe2b9e
     latest-changes: 2.35.0
     page-versions:
-    - name: 2.35.1 &rarr; 2.46.1
+    - name: 2.35.1 &rarr; 2.46.2
     - name: 2.35.0
       added: 1
       removed: 1
@@ -46127,9 +46312,10 @@ pages:
       2.45.2: f41bc94b6300e1a47829888967420b923a874b79
       2.46.0: f41bc94b6300e1a47829888967420b923a874b79
       2.46.1: f41bc94b6300e1a47829888967420b923a874b79
+      2.46.2: f41bc94b6300e1a47829888967420b923a874b79
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -46335,9 +46521,10 @@ pages:
       2.45.2: b95d548e6017616485810c7a35d9dabd258b5956
       2.46.0: b95d548e6017616485810c7a35d9dabd258b5956
       2.46.1: b95d548e6017616485810c7a35d9dabd258b5956
+      2.46.2: b95d548e6017616485810c7a35d9dabd258b5956
     latest-changes: 2.0.5
     page-versions:
-    - name: 2.1.4 &rarr; 2.46.1
+    - name: 2.1.4 &rarr; 2.46.2
     - name: 2.0.5
       added: 8
       removed: 0
@@ -46535,9 +46722,10 @@ pages:
       2.45.2: 2d2d9691d7219bf421bb4ce632b90295cc3a467d
       2.46.0: fb6372d5c849d4357294e5f39d5af70e4ada408e
       2.46.1: fb6372d5c849d4357294e5f39d5af70e4ada408e
+      2.46.2: fb6372d5c849d4357294e5f39d5af70e4ada408e
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 6
       removed: 2
@@ -47184,9 +47372,10 @@ pages:
       2.45.2: df2e0f25afbf8a5c9bd0de7fd0c19a03db9248bd
       2.46.0: 24ce46233c32d97b697a86f01215e365c86c7713
       2.46.1: 24ce46233c32d97b697a86f01215e365c86c7713
+      2.46.2: 24ce46233c32d97b697a86f01215e365c86c7713
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 6
       removed: 1
@@ -47599,9 +47788,10 @@ pages:
       2.45.2: c31dd7b70c8221abc2823d8c051e0192fe01a3be
       2.46.0: c31dd7b70c8221abc2823d8c051e0192fe01a3be
       2.46.1: c31dd7b70c8221abc2823d8c051e0192fe01a3be
+      2.46.2: c31dd7b70c8221abc2823d8c051e0192fe01a3be
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 0
       removed: 3
@@ -47875,9 +48065,10 @@ pages:
       2.45.2: 60a8e198a2449404a781d9f86c2184412a6cc32e
       2.46.0: 60a8e198a2449404a781d9f86c2184412a6cc32e
       2.46.1: 60a8e198a2449404a781d9f86c2184412a6cc32e
+      2.46.2: 60a8e198a2449404a781d9f86c2184412a6cc32e
     latest-changes: 2.43.1
     page-versions:
-    - name: 2.43.2 &rarr; 2.46.1
+    - name: 2.43.2 &rarr; 2.46.2
     - name: 2.43.1
       added: 1
       removed: 1
@@ -48157,9 +48348,10 @@ pages:
       2.45.2: 1a25cd95d0ab4e5519c5fcbacc6654a042907b78
       2.46.0: 1a25cd95d0ab4e5519c5fcbacc6654a042907b78
       2.46.1: 1a25cd95d0ab4e5519c5fcbacc6654a042907b78
+      2.46.2: 1a25cd95d0ab4e5519c5fcbacc6654a042907b78
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 7
       removed: 1
@@ -48458,9 +48650,10 @@ pages:
       2.45.2: 3ed7d4034984bf1632ac84480dbdc632764a473b
       2.46.0: 3ed7d4034984bf1632ac84480dbdc632764a473b
       2.46.1: 3ed7d4034984bf1632ac84480dbdc632764a473b
+      2.46.2: 3ed7d4034984bf1632ac84480dbdc632764a473b
     latest-changes: 2.12.5
     page-versions:
-    - name: 2.13.7 &rarr; 2.46.1
+    - name: 2.13.7 &rarr; 2.46.2
     - name: 2.12.5
       added: 1
       removed: 1
@@ -48679,9 +48872,10 @@ pages:
       2.45.2: 99cadf87ae3892d47a595a56c09f3de9ef2afc40
       2.46.0: 99cadf87ae3892d47a595a56c09f3de9ef2afc40
       2.46.1: 99cadf87ae3892d47a595a56c09f3de9ef2afc40
+      2.46.2: 99cadf87ae3892d47a595a56c09f3de9ef2afc40
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 4
       removed: 4
@@ -48940,9 +49134,10 @@ pages:
       2.45.2: 3e6f85795eacdd908643c248d329a3a0f139ddd9
       2.46.0: 6557796582319fb3cf28048dcda4ad37363a23e4
       2.46.1: 6557796582319fb3cf28048dcda4ad37363a23e4
+      2.46.2: 6557796582319fb3cf28048dcda4ad37363a23e4
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 4
       removed: 4
@@ -49314,8 +49509,10 @@ pages:
       2.45.2: 4c7a61fdb45e2df3d26adad0ab640f46a0401d46
       2.46.0: f3e74ce49cc28d101492126cb15a9157f137e1ef
       2.46.1: 7e6bcb78ff6f23de8ec8d6b23d9d3473989c8f90
+      2.46.2: 7e6bcb78ff6f23de8ec8d6b23d9d3473989c8f90
     latest-changes: 2.46.1
     page-versions:
+    - name: 2.46.2
     - name: 2.46.1
       added: 5
       removed: 3
@@ -49728,9 +49925,10 @@ pages:
       2.45.2: 6146427e1a5e9ee6980f06f5e6d95c3484c23f49
       2.46.0: 6146427e1a5e9ee6980f06f5e6d95c3484c23f49
       2.46.1: 6146427e1a5e9ee6980f06f5e6d95c3484c23f49
+      2.46.2: 6146427e1a5e9ee6980f06f5e6d95c3484c23f49
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 4
       removed: 4
@@ -50038,9 +50236,10 @@ pages:
       2.45.2: c2828aecdb59f217184c45f65ec2079353e9a4fc
       2.46.0: c2828aecdb59f217184c45f65ec2079353e9a4fc
       2.46.1: c2828aecdb59f217184c45f65ec2079353e9a4fc
+      2.46.2: c2828aecdb59f217184c45f65ec2079353e9a4fc
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 2
       removed: 2
@@ -50321,9 +50520,10 @@ pages:
       2.45.2: '08a0dd1037a8afe6787eb18e94dca1f4753c28ee'
       2.46.0: '08a0dd1037a8afe6787eb18e94dca1f4753c28ee'
       2.46.1: '08a0dd1037a8afe6787eb18e94dca1f4753c28ee'
+      2.46.2: '08a0dd1037a8afe6787eb18e94dca1f4753c28ee'
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 3
       removed: 3
@@ -50709,9 +50909,10 @@ pages:
       2.45.2: 5bad30f98beb03162cb04d4c56c86076741cc60b
       2.46.0: 5bad30f98beb03162cb04d4c56c86076741cc60b
       2.46.1: 5bad30f98beb03162cb04d4c56c86076741cc60b
+      2.46.2: 5bad30f98beb03162cb04d4c56c86076741cc60b
     latest-changes: 2.32.0
     page-versions:
-    - name: 2.32.1 &rarr; 2.46.1
+    - name: 2.32.1 &rarr; 2.46.2
     - name: 2.32.0
       added: 4
       removed: 0
@@ -50922,9 +51123,10 @@ pages:
       2.45.2: fc90ad8ce61c37abda58c5778935252617003be3
       2.46.0: fc90ad8ce61c37abda58c5778935252617003be3
       2.46.1: fc90ad8ce61c37abda58c5778935252617003be3
+      2.46.2: fc90ad8ce61c37abda58c5778935252617003be3
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 3
       removed: 5
@@ -51229,9 +51431,10 @@ pages:
       2.45.2: 976b1677ff51ab58e3fb2f24bf26b6fc7d0474d2
       2.46.0: 976b1677ff51ab58e3fb2f24bf26b6fc7d0474d2
       2.46.1: 976b1677ff51ab58e3fb2f24bf26b6fc7d0474d2
+      2.46.2: 976b1677ff51ab58e3fb2f24bf26b6fc7d0474d2
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 3
       removed: 2
@@ -51558,9 +51761,10 @@ pages:
       2.45.2: 7e272257ee26331c9b565be5b9b26cad12b16bdb
       2.46.0: 7e272257ee26331c9b565be5b9b26cad12b16bdb
       2.46.1: 7e272257ee26331c9b565be5b9b26cad12b16bdb
+      2.46.2: 7e272257ee26331c9b565be5b9b26cad12b16bdb
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 6
       removed: 2
@@ -51918,9 +52122,10 @@ pages:
       2.45.2: d7c43c2fe4d240fb099e7fb4b8d83c98e057176e
       2.46.0: d7c43c2fe4d240fb099e7fb4b8d83c98e057176e
       2.46.1: d7c43c2fe4d240fb099e7fb4b8d83c98e057176e
+      2.46.2: d7c43c2fe4d240fb099e7fb4b8d83c98e057176e
     latest-changes: 2.23.0
     page-versions:
-    - name: 2.23.1 &rarr; 2.46.1
+    - name: 2.23.1 &rarr; 2.46.2
     - name: 2.23.0
       added: 2
       removed: 2
@@ -52139,8 +52344,10 @@ pages:
       2.45.2: ad8cfd091d84aa94c56d0e0ac51690a6b01af4e5
       2.46.0: ad8cfd091d84aa94c56d0e0ac51690a6b01af4e5
       2.46.1: 3dd1d1e3ca7048b561c7ac43d93e10bebdf5b9d7
+      2.46.2: 3dd1d1e3ca7048b561c7ac43d93e10bebdf5b9d7
     latest-changes: 2.46.1
     page-versions:
+    - name: 2.46.2
     - name: 2.46.1
       added: 1
       removed: 1
@@ -52407,9 +52614,10 @@ pages:
       2.45.2: 40088532ead49694e39d3bdc7da91011e8b7c98b
       2.46.0: 40088532ead49694e39d3bdc7da91011e8b7c98b
       2.46.1: 40088532ead49694e39d3bdc7da91011e8b7c98b
+      2.46.2: 40088532ead49694e39d3bdc7da91011e8b7c98b
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 4
       removed: 4
@@ -52720,9 +52928,10 @@ pages:
       2.45.2: 15d0a8cb250285faa9d6bbb9296b8d07721f82f6
       2.46.0: 15d0a8cb250285faa9d6bbb9296b8d07721f82f6
       2.46.1: 15d0a8cb250285faa9d6bbb9296b8d07721f82f6
+      2.46.2: 15d0a8cb250285faa9d6bbb9296b8d07721f82f6
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 1
       removed: 1
@@ -52987,9 +53196,10 @@ pages:
       2.45.2: d30bd569f92249efbed55fbd2d7edc42eaf99ed8
       2.46.0: d30bd569f92249efbed55fbd2d7edc42eaf99ed8
       2.46.1: d30bd569f92249efbed55fbd2d7edc42eaf99ed8
+      2.46.2: d30bd569f92249efbed55fbd2d7edc42eaf99ed8
     latest-changes: 2.35.0
     page-versions:
-    - name: 2.35.1 &rarr; 2.46.1
+    - name: 2.35.1 &rarr; 2.46.2
     - name: 2.35.0
       added: 3
       removed: 3
@@ -53331,9 +53541,10 @@ pages:
       2.45.2: b9829dc8e3120d4031b19a55961a9344cc486016
       2.46.0: b9829dc8e3120d4031b19a55961a9344cc486016
       2.46.1: b9829dc8e3120d4031b19a55961a9344cc486016
+      2.46.2: b9829dc8e3120d4031b19a55961a9344cc486016
     latest-changes: 2.43.1
     page-versions:
-    - name: 2.43.2 &rarr; 2.46.1
+    - name: 2.43.2 &rarr; 2.46.2
     - name: 2.43.1
       added: 2
       removed: 2
@@ -53643,9 +53854,10 @@ pages:
       2.45.2: 87efc460e9a8391851a15268aa7b50a4f67113a0
       2.46.0: 87efc460e9a8391851a15268aa7b50a4f67113a0
       2.46.1: 87efc460e9a8391851a15268aa7b50a4f67113a0
+      2.46.2: 87efc460e9a8391851a15268aa7b50a4f67113a0
     latest-changes: 2.34.0
     page-versions:
-    - name: 2.34.1 &rarr; 2.46.1
+    - name: 2.34.1 &rarr; 2.46.2
     - name: 2.34.0
       added: 4
       removed: 4
@@ -53903,9 +54115,10 @@ pages:
       2.45.2: e5108790c086dfe863432c7251843d2a12f4ee0b
       2.46.0: e5108790c086dfe863432c7251843d2a12f4ee0b
       2.46.1: e5108790c086dfe863432c7251843d2a12f4ee0b
+      2.46.2: e5108790c086dfe863432c7251843d2a12f4ee0b
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 3
       removed: 5
@@ -54312,9 +54525,10 @@ pages:
       2.45.2: 61cc7960fb9183adffba8c5bbea2ae423a25a1b0
       2.46.0: 61cc7960fb9183adffba8c5bbea2ae423a25a1b0
       2.46.1: 61cc7960fb9183adffba8c5bbea2ae423a25a1b0
+      2.46.2: 61cc7960fb9183adffba8c5bbea2ae423a25a1b0
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 6
       removed: 2
@@ -54593,9 +54807,10 @@ pages:
       2.45.2: ff9cea7405f11f4e472515ba37b2f0558f8e0f4a
       2.46.0: ff9cea7405f11f4e472515ba37b2f0558f8e0f4a
       2.46.1: ff9cea7405f11f4e472515ba37b2f0558f8e0f4a
+      2.46.2: ff9cea7405f11f4e472515ba37b2f0558f8e0f4a
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 3
       removed: 3
@@ -54845,9 +55060,10 @@ pages:
       2.45.2: c8c27d4d5dfd3bd282432c55bd98dfab043665c5
       2.46.0: c8c27d4d5dfd3bd282432c55bd98dfab043665c5
       2.46.1: c8c27d4d5dfd3bd282432c55bd98dfab043665c5
+      2.46.2: c8c27d4d5dfd3bd282432c55bd98dfab043665c5
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 6
       removed: 2
@@ -55349,9 +55565,10 @@ pages:
       2.45.2: 0fa9796ed48afa7c49b300f6f80cfb6566263a57
       2.46.0: 0fa9796ed48afa7c49b300f6f80cfb6566263a57
       2.46.1: 0fa9796ed48afa7c49b300f6f80cfb6566263a57
+      2.46.2: 0fa9796ed48afa7c49b300f6f80cfb6566263a57
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 6
       removed: 2
@@ -56647,9 +56864,10 @@ pages:
       2.45.2: e8fa29d63e17ceb0da341d723a99c65c14cc8d6b
       2.46.0: e8fa29d63e17ceb0da341d723a99c65c14cc8d6b
       2.46.1: e8fa29d63e17ceb0da341d723a99c65c14cc8d6b
+      2.46.2: e8fa29d63e17ceb0da341d723a99c65c14cc8d6b
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -56875,9 +57093,10 @@ pages:
       2.45.2: 1b8a3f5d44179164f22edd4196ef836621f7d418
       2.46.0: 1b8a3f5d44179164f22edd4196ef836621f7d418
       2.46.1: 1b8a3f5d44179164f22edd4196ef836621f7d418
+      2.46.2: 1b8a3f5d44179164f22edd4196ef836621f7d418
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 2
       removed: 2
@@ -57177,9 +57396,10 @@ pages:
       2.45.2: 163f761a1650ab2b4ee705eeb05dd365f6c72395
       2.46.0: 163f761a1650ab2b4ee705eeb05dd365f6c72395
       2.46.1: 163f761a1650ab2b4ee705eeb05dd365f6c72395
+      2.46.2: 163f761a1650ab2b4ee705eeb05dd365f6c72395
     latest-changes: 2.38.0
     page-versions:
-    - name: 2.38.1 &rarr; 2.46.1
+    - name: 2.38.1 &rarr; 2.46.2
     - name: 2.38.0
       added: 7
       removed: 1
@@ -58296,9 +58516,10 @@ pages:
       2.45.2: b1cdf80a1ca627c91fd59e8dd271291a5bac2b4d
       2.46.0: 335be61eb70bbbd98067a62eea36733acb2f92b6
       2.46.1: 335be61eb70bbbd98067a62eea36733acb2f92b6
+      2.46.2: 335be61eb70bbbd98067a62eea36733acb2f92b6
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 8
       removed: 0
@@ -59247,9 +59468,10 @@ pages:
       2.45.2: 9f7c7feb6d01be97d925e2878db265598558d9f2
       2.46.0: 9f7c7feb6d01be97d925e2878db265598558d9f2
       2.46.1: 9f7c7feb6d01be97d925e2878db265598558d9f2
+      2.46.2: 9f7c7feb6d01be97d925e2878db265598558d9f2
     latest-changes: 2.0.5
     page-versions:
-    - name: 2.1.4 &rarr; 2.46.1
+    - name: 2.1.4 &rarr; 2.46.2
     - name: 2.0.5
       added: 8
       removed: 0
@@ -60154,9 +60376,10 @@ pages:
       2.45.2: 9d678beb56af337c527a81a55995da07fd1e1b80
       2.46.0: 9d678beb56af337c527a81a55995da07fd1e1b80
       2.46.1: 9d678beb56af337c527a81a55995da07fd1e1b80
+      2.46.2: 9d678beb56af337c527a81a55995da07fd1e1b80
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -60375,9 +60598,10 @@ pages:
       2.45.2: 20a428ce74c6c83ee2d0ec0094c5f4a742207939
       2.46.0: 20a428ce74c6c83ee2d0ec0094c5f4a742207939
       2.46.1: 20a428ce74c6c83ee2d0ec0094c5f4a742207939
+      2.46.2: 20a428ce74c6c83ee2d0ec0094c5f4a742207939
     latest-changes: 2.0.5
     page-versions:
-    - name: 2.1.4 &rarr; 2.46.1
+    - name: 2.1.4 &rarr; 2.46.2
     - name: 2.0.5
       added: 8
       removed: 0
@@ -60571,9 +60795,10 @@ pages:
       2.45.2: b6b5abb561f21434986717f4d404f81399401936
       2.46.0: b6b5abb561f21434986717f4d404f81399401936
       2.46.1: b6b5abb561f21434986717f4d404f81399401936
+      2.46.2: b6b5abb561f21434986717f4d404f81399401936
     latest-changes: 2.29.0
     page-versions:
-    - name: 2.29.1 &rarr; 2.46.1
+    - name: 2.29.1 &rarr; 2.46.2
     - name: 2.29.0
       added: 1
       removed: 1
@@ -60784,9 +61009,10 @@ pages:
       2.45.2: c83a8a4d450d81a02d158d3b1d007d2ae2062909
       2.46.0: c83a8a4d450d81a02d158d3b1d007d2ae2062909
       2.46.1: c83a8a4d450d81a02d158d3b1d007d2ae2062909
+      2.46.2: c83a8a4d450d81a02d158d3b1d007d2ae2062909
     latest-changes: 2.15.4
     page-versions:
-    - name: 2.16.6 &rarr; 2.46.1
+    - name: 2.16.6 &rarr; 2.46.2
     - name: 2.15.4
       added: 2
       removed: 2
@@ -60989,9 +61215,10 @@ pages:
       2.45.2: 9df565317243900ed12715232782e3c6baecabe0
       2.46.0: 1338e84dc0cf5293410f39f8cc3ce18ac0b4532c
       2.46.1: 1338e84dc0cf5293410f39f8cc3ce18ac0b4532c
+      2.46.2: 1338e84dc0cf5293410f39f8cc3ce18ac0b4532c
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 4
       removed: 4
@@ -61432,9 +61659,10 @@ pages:
       2.45.2: f9a164bcb3170cbcc55bcf28c1c49c7a1bb6ecf1
       2.46.0: f9a164bcb3170cbcc55bcf28c1c49c7a1bb6ecf1
       2.46.1: f9a164bcb3170cbcc55bcf28c1c49c7a1bb6ecf1
+      2.46.2: f9a164bcb3170cbcc55bcf28c1c49c7a1bb6ecf1
     latest-changes: 2.39.0
     page-versions:
-    - name: 2.39.1 &rarr; 2.46.1
+    - name: 2.39.1 &rarr; 2.46.2
     - name: 2.39.0
       added: 1
       removed: 1
@@ -61735,9 +61963,10 @@ pages:
       2.45.2: 92f0f104b2bb0d998284e364ba6fc02df7f31ea5
       2.46.0: 92f0f104b2bb0d998284e364ba6fc02df7f31ea5
       2.46.1: 92f0f104b2bb0d998284e364ba6fc02df7f31ea5
+      2.46.2: 92f0f104b2bb0d998284e364ba6fc02df7f31ea5
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 3
       removed: 3
@@ -62076,9 +62305,10 @@ pages:
       2.45.2: c745fcc2d8afa3e14e6b18cd8a5daa71962280d7
       2.46.0: c745fcc2d8afa3e14e6b18cd8a5daa71962280d7
       2.46.1: c745fcc2d8afa3e14e6b18cd8a5daa71962280d7
+      2.46.2: c745fcc2d8afa3e14e6b18cd8a5daa71962280d7
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -62317,9 +62547,10 @@ pages:
       2.45.2: e5a61b02f006e9e8b479c3167cb3327151692553
       2.46.0: e5a61b02f006e9e8b479c3167cb3327151692553
       2.46.1: e5a61b02f006e9e8b479c3167cb3327151692553
+      2.46.2: e5a61b02f006e9e8b479c3167cb3327151692553
     latest-changes: 2.37.0
     page-versions:
-    - name: 2.37.1 &rarr; 2.46.1
+    - name: 2.37.1 &rarr; 2.46.2
     - name: 2.37.0
       added: 8
       removed: 0
@@ -62525,9 +62756,10 @@ pages:
       2.45.2: f8809becc28a3d39df61cd55a347a7e5e52ff724
       2.46.0: f8809becc28a3d39df61cd55a347a7e5e52ff724
       2.46.1: f8809becc28a3d39df61cd55a347a7e5e52ff724
+      2.46.2: f8809becc28a3d39df61cd55a347a7e5e52ff724
     latest-changes: 2.43.1
     page-versions:
-    - name: 2.43.2 &rarr; 2.46.1
+    - name: 2.43.2 &rarr; 2.46.2
     - name: 2.43.1
       added: 2
       removed: 2
@@ -62997,9 +63229,10 @@ pages:
       2.45.2: ca1f0401e52a085ba6d34b63a012fd6288d65b81
       2.46.0: ca1f0401e52a085ba6d34b63a012fd6288d65b81
       2.46.1: ca1f0401e52a085ba6d34b63a012fd6288d65b81
+      2.46.2: ca1f0401e52a085ba6d34b63a012fd6288d65b81
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 3
       removed: 2
@@ -63483,9 +63716,10 @@ pages:
       2.45.2: 79a932fb08571e0fd5519d015b56a42aa000eb1d
       2.46.0: 79a932fb08571e0fd5519d015b56a42aa000eb1d
       2.46.1: 79a932fb08571e0fd5519d015b56a42aa000eb1d
+      2.46.2: 79a932fb08571e0fd5519d015b56a42aa000eb1d
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 2
       removed: 2
@@ -63745,9 +63979,10 @@ pages:
       2.45.2: 3a0878d5a9acb00a41c9bfcd2f11ba52e6ea4879
       2.46.0: 3a0878d5a9acb00a41c9bfcd2f11ba52e6ea4879
       2.46.1: 3a0878d5a9acb00a41c9bfcd2f11ba52e6ea4879
+      2.46.2: 3a0878d5a9acb00a41c9bfcd2f11ba52e6ea4879
     latest-changes: 2.40.0
     page-versions:
-    - name: 2.40.1 &rarr; 2.46.1
+    - name: 2.40.1 &rarr; 2.46.2
     - name: 2.40.0
       added: 1
       removed: 1
@@ -63998,9 +64233,10 @@ pages:
       2.45.2: 03100b82c0c23b1e648ed5589ba21dd367f73de3
       2.46.0: 03100b82c0c23b1e648ed5589ba21dd367f73de3
       2.46.1: 03100b82c0c23b1e648ed5589ba21dd367f73de3
+      2.46.2: 03100b82c0c23b1e648ed5589ba21dd367f73de3
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -64250,9 +64486,10 @@ pages:
       2.45.2: f86a8cf0ff52c3d7b7ca728ab6a6d9480cab5258
       2.46.0: f86a8cf0ff52c3d7b7ca728ab6a6d9480cab5258
       2.46.1: f86a8cf0ff52c3d7b7ca728ab6a6d9480cab5258
+      2.46.2: f86a8cf0ff52c3d7b7ca728ab6a6d9480cab5258
     latest-changes: 2.38.0
     page-versions:
-    - name: 2.38.1 &rarr; 2.46.1
+    - name: 2.38.1 &rarr; 2.46.2
     - name: 2.38.0
       added: 1
       removed: 1
@@ -64431,9 +64668,10 @@ pages:
       2.45.2: 6e9bfc078ea6cd669d00ab067032d058102f9a68
       2.46.0: 766c577534308bbce80705181400029f52858cbd
       2.46.1: 766c577534308bbce80705181400029f52858cbd
+      2.46.2: 766c577534308bbce80705181400029f52858cbd
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 7
       removed: 1
@@ -64908,9 +65146,10 @@ pages:
       2.45.2: d45fc59dd30837780e6e07ae38021359d3d482da
       2.46.0: d45fc59dd30837780e6e07ae38021359d3d482da
       2.46.1: d45fc59dd30837780e6e07ae38021359d3d482da
+      2.46.2: d45fc59dd30837780e6e07ae38021359d3d482da
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -65387,9 +65626,10 @@ pages:
       2.45.2: cea081835ecdec7a709a293cbb3b92e99ced64e0
       2.46.0: cea081835ecdec7a709a293cbb3b92e99ced64e0
       2.46.1: cea081835ecdec7a709a293cbb3b92e99ced64e0
+      2.46.2: cea081835ecdec7a709a293cbb3b92e99ced64e0
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -65598,9 +65838,10 @@ pages:
       2.45.2: 17ad1d4b6725471790b08998088d9bf59dedb32e
       2.46.0: 17ad1d4b6725471790b08998088d9bf59dedb32e
       2.46.1: 17ad1d4b6725471790b08998088d9bf59dedb32e
+      2.46.2: 17ad1d4b6725471790b08998088d9bf59dedb32e
     latest-changes: 2.33.1
     page-versions:
-    - name: 2.33.2 &rarr; 2.46.1
+    - name: 2.33.2 &rarr; 2.46.2
     - name: 2.33.1
       added: 5
       removed: 3
@@ -65782,9 +66023,10 @@ pages:
       2.45.2: 94207d98cbde09dc488de42ee7fd833a5b8a6acd
       2.46.0: 94207d98cbde09dc488de42ee7fd833a5b8a6acd
       2.46.1: 94207d98cbde09dc488de42ee7fd833a5b8a6acd
+      2.46.2: 94207d98cbde09dc488de42ee7fd833a5b8a6acd
     latest-changes: 2.38.2
     page-versions:
-    - name: 2.38.3 &rarr; 2.46.1
+    - name: 2.38.3 &rarr; 2.46.2
     - name: 2.38.2
       added: 4
       removed: 3
@@ -66006,9 +66248,10 @@ pages:
       2.45.2: f9d4b5bb2230d069a2ecdfe869cf747ff00112bc
       2.46.0: f9d4b5bb2230d069a2ecdfe869cf747ff00112bc
       2.46.1: f9d4b5bb2230d069a2ecdfe869cf747ff00112bc
+      2.46.2: f9d4b5bb2230d069a2ecdfe869cf747ff00112bc
     latest-changes: 2.36.0
     page-versions:
-    - name: 2.36.1 &rarr; 2.46.1
+    - name: 2.36.1 &rarr; 2.46.2
     - name: 2.36.0
       added: 1
       removed: 0
@@ -66214,9 +66457,10 @@ pages:
       2.45.2: 8f7849ed3be4d44e9b07ae84f911ceca5645f824
       2.46.0: 8f7849ed3be4d44e9b07ae84f911ceca5645f824
       2.46.1: 8f7849ed3be4d44e9b07ae84f911ceca5645f824
+      2.46.2: 8f7849ed3be4d44e9b07ae84f911ceca5645f824
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 3
       removed: 3
@@ -66395,9 +66639,10 @@ pages:
       2.45.2: 7a12b5e8a89f1ad02fd9593adab3bf3e91665c69
       2.46.0: 7a12b5e8a89f1ad02fd9593adab3bf3e91665c69
       2.46.1: 7a12b5e8a89f1ad02fd9593adab3bf3e91665c69
+      2.46.2: 7a12b5e8a89f1ad02fd9593adab3bf3e91665c69
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 1
       removed: 1
@@ -66641,9 +66886,10 @@ pages:
       2.45.2: 715d4522814e36dcfbda94bf9b3e0264b2d28ffe
       2.46.0: 6d3ab9950ac8c144f6cbb5000d39285492edec3a
       2.46.1: 6d3ab9950ac8c144f6cbb5000d39285492edec3a
+      2.46.2: 6d3ab9950ac8c144f6cbb5000d39285492edec3a
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 8
       removed: 0
@@ -66934,9 +67180,10 @@ pages:
       2.45.2: 9259f26a2ac7d62fc7228bee9ba7900ae7da1279
       2.46.0: 9259f26a2ac7d62fc7228bee9ba7900ae7da1279
       2.46.1: 9259f26a2ac7d62fc7228bee9ba7900ae7da1279
+      2.46.2: 9259f26a2ac7d62fc7228bee9ba7900ae7da1279
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 6
       removed: 2
@@ -67122,9 +67369,10 @@ pages:
       2.45.2: 640debacb8b43a49dcf7a3f68d10dfacd324e6e9
       2.46.0: 640debacb8b43a49dcf7a3f68d10dfacd324e6e9
       2.46.1: 640debacb8b43a49dcf7a3f68d10dfacd324e6e9
+      2.46.2: 640debacb8b43a49dcf7a3f68d10dfacd324e6e9
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 6
       removed: 2
@@ -67313,9 +67561,10 @@ pages:
       2.45.2: 1e1cd7497415a0aa15fc277c9f05c150174cb250
       2.46.0: 1e1cd7497415a0aa15fc277c9f05c150174cb250
       2.46.1: 1e1cd7497415a0aa15fc277c9f05c150174cb250
+      2.46.2: 1e1cd7497415a0aa15fc277c9f05c150174cb250
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 5
       removed: 3
@@ -67510,9 +67759,10 @@ pages:
       2.45.2: cd3f435a0d374550933a11945794a787ded0dbb2
       2.46.0: cd3f435a0d374550933a11945794a787ded0dbb2
       2.46.1: cd3f435a0d374550933a11945794a787ded0dbb2
+      2.46.2: cd3f435a0d374550933a11945794a787ded0dbb2
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 1
       removed: 1
@@ -67832,9 +68082,10 @@ pages:
       2.45.2: b39aa7e00739e2d74f05f14c6dad1b968622f21e
       2.46.0: b39aa7e00739e2d74f05f14c6dad1b968622f21e
       2.46.1: b39aa7e00739e2d74f05f14c6dad1b968622f21e
+      2.46.2: b39aa7e00739e2d74f05f14c6dad1b968622f21e
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 5
       removed: 1
@@ -68007,9 +68258,10 @@ pages:
       2.45.2: 4b3132ca29ac8e40e0466ded34b67e902952ef49
       2.46.0: d26c27a27957296703a890c536e5a37fa4fbbc3d
       2.46.1: d26c27a27957296703a890c536e5a37fa4fbbc3d
+      2.46.2: d26c27a27957296703a890c536e5a37fa4fbbc3d
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 8
       removed: 0
@@ -68152,9 +68404,10 @@ pages:
       2.45.2: 5709c6c6b68d2bb40793d818b2f2c4c5bacc1935
       2.46.0: 5709c6c6b68d2bb40793d818b2f2c4c5bacc1935
       2.46.1: 5709c6c6b68d2bb40793d818b2f2c4c5bacc1935
+      2.46.2: 5709c6c6b68d2bb40793d818b2f2c4c5bacc1935
     latest-changes: 2.38.0
     page-versions:
-    - name: 2.38.1 &rarr; 2.46.1
+    - name: 2.38.1 &rarr; 2.46.2
     - name: 2.38.0
       added: 1
       removed: 1
@@ -68297,9 +68550,10 @@ pages:
       2.45.2: e5ccb529d6ec05cffb9d55eb48ee4006e02013a0
       2.46.0: e5ccb529d6ec05cffb9d55eb48ee4006e02013a0
       2.46.1: e5ccb529d6ec05cffb9d55eb48ee4006e02013a0
+      2.46.2: e5ccb529d6ec05cffb9d55eb48ee4006e02013a0
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -68456,8 +68710,12 @@ pages:
       2.45.2: ac97d5b2840724ffd0bbd03318a7e5ae8410a4ed
       2.46.0: ac97d5b2840724ffd0bbd03318a7e5ae8410a4ed
       2.46.1: ac97d5b2840724ffd0bbd03318a7e5ae8410a4ed
-    latest-changes: 2.43.0
+      2.46.2: 35a8f8e1fb14cdf92baf4490ae1127a37dcf3bb9
+    latest-changes: 2.46.2
     page-versions:
+    - name: 2.46.2
+      added: 3
+      removed: 0
     - name: 2.43.1 &rarr; 2.46.1
     - name: 2.43.0
       added: 4
@@ -68534,6 +68792,10 @@ pages:
       - 4
       - 4
       - 0
+      ac97d5b2840724ffd0bbd03318a7e5ae8410a4ed..35a8f8e1fb14cdf92baf4490ae1127a37dcf3bb9:
+      - 3
+      - 0
+      - 5
   rev-list-description:
     version-map:
       2.29.0: de67093125527ab92b15872b543116173894248c
@@ -68646,9 +68908,10 @@ pages:
       2.45.2: de67093125527ab92b15872b543116173894248c
       2.46.0: de67093125527ab92b15872b543116173894248c
       2.46.1: de67093125527ab92b15872b543116173894248c
+      2.46.2: de67093125527ab92b15872b543116173894248c
     latest-changes: 2.29.0
     page-versions:
-    - name: 2.29.1 &rarr; 2.46.1
+    - name: 2.29.1 &rarr; 2.46.2
     - name: 2.29.0
       added: 8
       removed: 0
@@ -68760,9 +69023,10 @@ pages:
       2.45.2: ae602c79ce7d3c62c1585be7498d29283f235a15
       2.46.0: 3ca64c9a6c67cdaa32d8e363bc0dd9eff7d46da4
       2.46.1: 3ca64c9a6c67cdaa32d8e363bc0dd9eff7d46da4
+      2.46.2: 3ca64c9a6c67cdaa32d8e363bc0dd9eff7d46da4
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 8
       removed: 0
@@ -68873,9 +69137,10 @@ pages:
       2.45.2: 1291163cdc8377ec509c2a59860bdf3a536b7523
       2.46.0: 1291163cdc8377ec509c2a59860bdf3a536b7523
       2.46.1: 1291163cdc8377ec509c2a59860bdf3a536b7523
+      2.46.2: 1291163cdc8377ec509c2a59860bdf3a536b7523
     latest-changes: 2.32.0
     page-versions:
-    - name: 2.32.1 &rarr; 2.46.1
+    - name: 2.32.1 &rarr; 2.46.2
     - name: 2.32.0
       added: 7
       removed: 0
@@ -69044,9 +69309,10 @@ pages:
       2.45.2: 9c0b8adadca622f48e907e7ef6eb515aad5a87f1
       2.46.0: 9c0b8adadca622f48e907e7ef6eb515aad5a87f1
       2.46.1: 9c0b8adadca622f48e907e7ef6eb515aad5a87f1
+      2.46.2: 9c0b8adadca622f48e907e7ef6eb515aad5a87f1
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -69156,9 +69422,10 @@ pages:
       2.45.2: aee784e02cdad5118474084090df6dc6fb45edb5
       2.46.0: aee784e02cdad5118474084090df6dc6fb45edb5
       2.46.1: aee784e02cdad5118474084090df6dc6fb45edb5
+      2.46.2: aee784e02cdad5118474084090df6dc6fb45edb5
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -69268,9 +69535,10 @@ pages:
       2.45.2: f8317483add010d53c40764442b456d6ec3c4c32
       2.46.0: f8317483add010d53c40764442b456d6ec3c4c32
       2.46.1: f8317483add010d53c40764442b456d6ec3c4c32
+      2.46.2: f8317483add010d53c40764442b456d6ec3c4c32
     latest-changes: 2.32.0
     page-versions:
-    - name: 2.32.1 &rarr; 2.46.1
+    - name: 2.32.1 &rarr; 2.46.2
     - name: 2.32.0
       added: 8
       removed: 0
@@ -69355,9 +69623,10 @@ pages:
       2.45.2: 86b6a318a5ed48926b48e96d4983457f9058132d
       2.46.0: 86b6a318a5ed48926b48e96d4983457f9058132d
       2.46.1: 86b6a318a5ed48926b48e96d4983457f9058132d
+      2.46.2: 86b6a318a5ed48926b48e96d4983457f9058132d
     latest-changes: 2.42.0
     page-versions:
-    - name: 2.42.1 &rarr; 2.46.1
+    - name: 2.42.1 &rarr; 2.46.2
     - name: 2.42.0
       added: 1
       removed: 1
@@ -69458,9 +69727,10 @@ pages:
       2.45.2: 07f2d560511eeb513b507e69fb80e8c6dfeec60d
       2.46.0: 07f2d560511eeb513b507e69fb80e8c6dfeec60d
       2.46.1: 07f2d560511eeb513b507e69fb80e8c6dfeec60d
+      2.46.2: 07f2d560511eeb513b507e69fb80e8c6dfeec60d
     latest-changes: 2.33.1
     page-versions:
-    - name: 2.33.2 &rarr; 2.46.1
+    - name: 2.33.2 &rarr; 2.46.2
     - name: 2.33.1
       added: 8
       removed: 0
@@ -69518,9 +69788,10 @@ pages:
       2.45.2: 91bf30386de3cf01cd5657baf17d45aa55b0f2a7
       2.46.0: 91bf30386de3cf01cd5657baf17d45aa55b0f2a7
       2.46.1: 91bf30386de3cf01cd5657baf17d45aa55b0f2a7
+      2.46.2: 91bf30386de3cf01cd5657baf17d45aa55b0f2a7
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -69595,9 +69866,10 @@ pages:
       2.45.2: b4d3a837e5931769f6fdc52e3e8ffdf34a83fde7
       2.46.0: b4d3a837e5931769f6fdc52e3e8ffdf34a83fde7
       2.46.1: b4d3a837e5931769f6fdc52e3e8ffdf34a83fde7
+      2.46.2: b4d3a837e5931769f6fdc52e3e8ffdf34a83fde7
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -69665,9 +69937,10 @@ pages:
       2.45.2: 787ad476f239f1a81fc8847b87ff51f5c5b5b865
       2.46.0: 787ad476f239f1a81fc8847b87ff51f5c5b5b865
       2.46.1: 787ad476f239f1a81fc8847b87ff51f5c5b5b865
+      2.46.2: 787ad476f239f1a81fc8847b87ff51f5c5b5b865
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 2
       removed: 1
@@ -69743,9 +70016,10 @@ pages:
       2.45.2: b929d774105e8bb77c62cc916df3c340362fa54e
       2.46.0: b929d774105e8bb77c62cc916df3c340362fa54e
       2.46.1: b929d774105e8bb77c62cc916df3c340362fa54e
+      2.46.2: b929d774105e8bb77c62cc916df3c340362fa54e
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 1
       removed: 1
@@ -69797,9 +70071,10 @@ pages:
       2.45.2: c917e70a2a0b1b2cf75d0c97cdf3c8c4474f4dee
       2.46.0: c917e70a2a0b1b2cf75d0c97cdf3c8c4474f4dee
       2.46.1: c917e70a2a0b1b2cf75d0c97cdf3c8c4474f4dee
+      2.46.2: c917e70a2a0b1b2cf75d0c97cdf3c8c4474f4dee
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 4
       removed: 4
@@ -69851,9 +70126,10 @@ pages:
       2.45.2: f1df68fb9520b76c3829947e41244defcb44a75c
       2.46.0: f1df68fb9520b76c3829947e41244defcb44a75c
       2.46.1: f1df68fb9520b76c3829947e41244defcb44a75c
+      2.46.2: f1df68fb9520b76c3829947e41244defcb44a75c
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 2
       removed: 2
@@ -69905,9 +70181,10 @@ pages:
       2.45.2: 5216dd853cb36a1fe92236f73ef4a7336fd79c3a
       2.46.0: 350fa32402d39e7bcb8b1618b0b51161b1565a34
       2.46.1: 350fa32402d39e7bcb8b1618b0b51161b1565a34
+      2.46.2: 350fa32402d39e7bcb8b1618b0b51161b1565a34
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 5
       removed: 3
@@ -69967,9 +70244,10 @@ pages:
       2.45.2: 84dba05a1b2990e5332bd36642209e347d2ec934
       2.46.0: 84dba05a1b2990e5332bd36642209e347d2ec934
       2.46.1: 84dba05a1b2990e5332bd36642209e347d2ec934
+      2.46.2: 84dba05a1b2990e5332bd36642209e347d2ec934
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 2
       removed: 2
@@ -70029,9 +70307,10 @@ pages:
       2.45.2: d7c9f7faf15eec1645cffdee6fa0e86b73146242
       2.46.0: d7c9f7faf15eec1645cffdee6fa0e86b73146242
       2.46.1: d7c9f7faf15eec1645cffdee6fa0e86b73146242
+      2.46.2: d7c9f7faf15eec1645cffdee6fa0e86b73146242
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 8
       removed: 0
@@ -70099,9 +70378,10 @@ pages:
       2.45.2: 94074b7c94ec8860c54a9fc676453b773c7144ce
       2.46.0: 94074b7c94ec8860c54a9fc676453b773c7144ce
       2.46.1: 94074b7c94ec8860c54a9fc676453b773c7144ce
+      2.46.2: 94074b7c94ec8860c54a9fc676453b773c7144ce
     latest-changes: 2.40.0
     page-versions:
-    - name: 2.40.1 &rarr; 2.46.1
+    - name: 2.40.1 &rarr; 2.46.2
     - name: 2.40.0
       added: 6
       removed: 2
@@ -70153,9 +70433,10 @@ pages:
       2.45.2: 82f6680b5e7d509a8f341e1e0dcdc042753cdf1e
       2.46.0: 82f6680b5e7d509a8f341e1e0dcdc042753cdf1e
       2.46.1: 82f6680b5e7d509a8f341e1e0dcdc042753cdf1e
+      2.46.2: 82f6680b5e7d509a8f341e1e0dcdc042753cdf1e
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 1
       removed: 1
@@ -70215,9 +70496,10 @@ pages:
       2.45.2: d3471b78059fde00de08f9a0a5d980f9325b98d1
       2.46.0: d3471b78059fde00de08f9a0a5d980f9325b98d1
       2.46.1: d3471b78059fde00de08f9a0a5d980f9325b98d1
+      2.46.2: d3471b78059fde00de08f9a0a5d980f9325b98d1
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 1
       removed: 1
@@ -70269,9 +70551,10 @@ pages:
       2.45.2: be98daefa82e93b18bebd5ef424d81e097a63cc4
       2.46.0: be98daefa82e93b18bebd5ef424d81e097a63cc4
       2.46.1: be98daefa82e93b18bebd5ef424d81e097a63cc4
+      2.46.2: be98daefa82e93b18bebd5ef424d81e097a63cc4
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 4
       removed: 4
@@ -70338,9 +70621,10 @@ pages:
       2.45.2: 9eddf823a6151354abc8c84c50a9364e297a0eaf
       2.46.0: 9eddf823a6151354abc8c84c50a9364e297a0eaf
       2.46.1: 9eddf823a6151354abc8c84c50a9364e297a0eaf
+      2.46.2: 9eddf823a6151354abc8c84c50a9364e297a0eaf
     latest-changes: 2.43.0
     page-versions:
-    - name: 2.43.1 &rarr; 2.46.1
+    - name: 2.43.1 &rarr; 2.46.2
     - name: 2.43.0
       added: 3
       removed: 3
@@ -70392,9 +70676,10 @@ pages:
       2.45.2: 4c12b6d12f879561c76db37441a71bfc94a70840
       2.46.0: 4c12b6d12f879561c76db37441a71bfc94a70840
       2.46.1: 4c12b6d12f879561c76db37441a71bfc94a70840
+      2.46.2: 4c12b6d12f879561c76db37441a71bfc94a70840
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 4
       removed: 2
@@ -70470,9 +70755,10 @@ pages:
       2.45.2: 550b18d644f06c75844aacf51478ae94d4779f4c
       2.46.0: 550b18d644f06c75844aacf51478ae94d4779f4c
       2.46.1: 550b18d644f06c75844aacf51478ae94d4779f4c
+      2.46.2: 550b18d644f06c75844aacf51478ae94d4779f4c
     latest-changes: 2.42.1
     page-versions:
-    - name: 2.42.2 &rarr; 2.46.1
+    - name: 2.42.2 &rarr; 2.46.2
     - name: 2.42.1
       added: 7
       removed: 1
@@ -70524,9 +70810,10 @@ pages:
       2.45.2: 6cd4e693bb68d971aa4fa473473d04cedf6f967d
       2.46.0: 6cd4e693bb68d971aa4fa473473d04cedf6f967d
       2.46.1: 6cd4e693bb68d971aa4fa473473d04cedf6f967d
+      2.46.2: 6cd4e693bb68d971aa4fa473473d04cedf6f967d
     latest-changes: 2.40.0
     page-versions:
-    - name: 2.40.1 &rarr; 2.46.1
+    - name: 2.40.1 &rarr; 2.46.2
     - name: 2.40.0
       added: 4
       removed: 4
@@ -70580,9 +70867,10 @@ pages:
       2.45.2: a75b5ddec2718d3e799c8b247ce644d76505e15a
       2.46.0: a75b5ddec2718d3e799c8b247ce644d76505e15a
       2.46.1: a75b5ddec2718d3e799c8b247ce644d76505e15a
+      2.46.2: a75b5ddec2718d3e799c8b247ce644d76505e15a
     latest-changes: 2.39.0
     page-versions:
-    - name: 2.39.1 &rarr; 2.46.1
+    - name: 2.39.1 &rarr; 2.46.2
     - name: 2.39.0
       added: 8
       removed: 0
@@ -70596,9 +70884,10 @@ pages:
       2.45.2: e41899b2a256d03fbd0638f072d71faeac04cc3b
       2.46.0: e41899b2a256d03fbd0638f072d71faeac04cc3b
       2.46.1: e41899b2a256d03fbd0638f072d71faeac04cc3b
+      2.46.2: e41899b2a256d03fbd0638f072d71faeac04cc3b
     latest-changes: 2.45.0
     page-versions:
-    - name: 2.45.1 &rarr; 2.46.1
+    - name: 2.45.1 &rarr; 2.46.2
     - name: 2.45.0
       added: 5
       removed: 3
@@ -70621,9 +70910,10 @@ pages:
       2.45.2: 7ea8788da3b55fb2daf3f0a389c3a13907880769
       2.46.0: 7ea8788da3b55fb2daf3f0a389c3a13907880769
       2.46.1: 7ea8788da3b55fb2daf3f0a389c3a13907880769
+      2.46.2: 7ea8788da3b55fb2daf3f0a389c3a13907880769
     latest-changes: 2.44.0
     page-versions:
-    - name: 2.44.1 &rarr; 2.46.1
+    - name: 2.44.1 &rarr; 2.46.2
     - name: 2.44.0
       added: 8
       removed: 0
@@ -70631,9 +70921,10 @@ pages:
     version-map:
       2.46.0: c27d1daac81430425e08d762264ddef703c2ab42
       2.46.1: c27d1daac81430425e08d762264ddef703c2ab42
+      2.46.2: c27d1daac81430425e08d762264ddef703c2ab42
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 8
       removed: 0
@@ -70641,13 +70932,14 @@ pages:
     version-map:
       2.46.0: 3c37eb9b19b09c7c9edbb0fa4e68184b80e9a8d3
       2.46.1: 3c37eb9b19b09c7c9edbb0fa4e68184b80e9a8d3
+      2.46.2: 3c37eb9b19b09c7c9edbb0fa4e68184b80e9a8d3
     latest-changes: 2.46.0
     page-versions:
-    - name: 2.46.1
+    - name: 2.46.1 &rarr; 2.46.2
     - name: 2.46.0
       added: 8
       removed: 0
-latest-version: 2.46.1
+latest-version: 2.46.2
 l10n:
   commit_sha: 35f909baec99310ecdc1dbe22d99abaf45dd9680
   tree_sha: 56078a9d0b1bf7291815bd32b92b6dcd1fac8468