Documentation/fetch-options.txt

   1 --all::
   2         Fetch all remotes.
   3
   4 -a::
   5 --append::
   6         Append ref names and object names of fetched refs to the
   7         existing contents of `.git/FETCH_HEAD`.  Without this
   8         option old data in `.git/FETCH_HEAD` will be overwritten.
   9
  10 --depth=<depth>::
  11         Limit fetching to the specified number of commits from the tip of
  12         each remote branch history. If fetching to a 'shallow' repository
  13         created by `git clone` with `--depth=<depth>` option (see
  14         linkgit:git-clone[1]), deepen or shorten the history to the specified
  15         number of commits. Tags for the deepened commits are not fetched.
  16
  17 --deepen=<depth>::
  18         Similar to --depth, except it specifies the number of commits
  19         from the current shallow boundary instead of from the tip of
  20         each remote branch history.
  21
  22 --shallow-since=<date>::
  23         Deepen or shorten the history of a shallow repository to
  24         include all reachable commits after <date>.
  25
  26 --shallow-exclude=<revision>::
  27         Deepen or shorten the history of a shallow repository to
  28         exclude commits reachable from a specified remote branch or tag.
  29         This option can be specified multiple times.
  30
  31 --unshallow::
  32         If the source repository is complete, convert a shallow
  33         repository to a complete one, removing all the limitations
  34         imposed by shallow repositories.
  35 +
  36 If the source repository is shallow, fetch as much as possible so that
  37 the current repository has the same history as the source repository.
  38
  39 --update-shallow::
  40         By default when fetching from a shallow repository,
  41         `git fetch` refuses refs that require updating
  42         .git/shallow. This option updates .git/shallow and accept such
  43         refs.
  44
  45 --negotiation-tip=<commit|glob>::
  46         By default, Git will report, to the server, commits reachable
  47         from all local refs to find common commits in an attempt to
  48         reduce the size of the to-be-received packfile. If specified,
  49         Git will only report commits reachable from the given tips.
  50         This is useful to speed up fetches when the user knows which
  51         local ref is likely to have commits in common with the
  52         upstream ref being fetched.
  53 +
  54 This option may be specified more than once; if so, Git will report
  55 commits reachable from any of the given commits.
  56 +
  57 The argument to this option may be a glob on ref names, a ref, or the (possibly
  58 abbreviated) SHA-1 of a commit. Specifying a glob is equivalent to specifying
  59 this option multiple times, one for each matching ref name.
  60 +
  61 See also the `fetch.negotiationAlgorithm` configuration variable
  62 documented in linkgit:git-config[1].
  63
  64 ifndef::git-pull[]
  65 --dry-run::
  66         Show what would be done, without making any changes.
  67 endif::git-pull[]
  68
  69 -f::
  70 --force::
  71         When 'git fetch' is used with `<src>:<dst>` refspec it may
  72         refuse to update the local branch as discussed
  73 ifdef::git-pull[]
  74         in the `<refspec>` part of the linkgit:git-fetch[1]
  75         documentation.
  76 endif::git-pull[]
  77 ifndef::git-pull[]
  78         in the `<refspec>` part below.
  79 endif::git-pull[]
  80         This option overrides that check.
  81
  82 -k::
  83 --keep::
  84         Keep downloaded pack.
  85
  86 ifndef::git-pull[]
  87 --multiple::
  88         Allow several <repository> and <group> arguments to be
  89         specified. No <refspec>s may be specified.
  90
  91 --[no-]auto-gc::
  92         Run `git gc --auto` at the end to perform garbage collection
  93         if needed. This is enabled by default.
  94
  95 --[no-]write-commit-graph::
  96         Write a commit-graph after fetching. This overrides the config
  97         setting `fetch.writeCommitGraph`.
  98
  99 -p::
 100 --prune::
 101         Before fetching, remove any remote-tracking references that no
 102         longer exist on the remote.  Tags are not subject to pruning
 103         if they are fetched only because of the default tag
 104         auto-following or due to a --tags option.  However, if tags
 105         are fetched due to an explicit refspec (either on the command
 106         line or in the remote configuration, for example if the remote
 107         was cloned with the --mirror option), then they are also
 108         subject to pruning. Supplying `--prune-tags` is a shorthand for
 109         providing the tag refspec.
 110 +
 111 See the PRUNING section below for more details.
 112
 113 -P::
 114 --prune-tags::
 115         Before fetching, remove any local tags that no longer exist on
 116         the remote if `--prune` is enabled. This option should be used
 117         more carefully, unlike `--prune` it will remove any local
 118         references (local tags) that have been created. This option is
 119         a shorthand for providing the explicit tag refspec along with
 120         `--prune`, see the discussion about that in its documentation.
 121 +
 122 See the PRUNING section below for more details.
 123
 124 endif::git-pull[]
 125
 126 ifndef::git-pull[]
 127 -n::
 128 endif::git-pull[]
 129 --no-tags::
 130         By default, tags that point at objects that are downloaded
 131         from the remote repository are fetched and stored locally.
 132         This option disables this automatic tag following. The default
 133         behavior for a remote may be specified with the remote.<name>.tagOpt
 134         setting. See linkgit:git-config[1].
 135
 136 ifndef::git-pull[]
 137 --refmap=<refspec>::
 138         When fetching refs listed on the command line, use the
 139         specified refspec (can be given more than once) to map the
 140         refs to remote-tracking branches, instead of the values of
 141         `remote.*.fetch` configuration variables for the remote
 142         repository.  Providing an empty `<refspec>` to the
 143         `--refmap` option causes Git to ignore the configured
 144         refspecs and rely entirely on the refspecs supplied as
 145         command-line arguments. See section on "Configured Remote-tracking
 146         Branches" for details.
 147
 148 -t::
 149 --tags::
 150         Fetch all tags from the remote (i.e., fetch remote tags
 151         `refs/tags/*` into local tags with the same name), in addition
 152         to whatever else would otherwise be fetched.  Using this
 153         option alone does not subject tags to pruning, even if --prune
 154         is used (though tags may be pruned anyway if they are also the
 155         destination of an explicit refspec; see `--prune`).
 156
 157 --recurse-submodules[=yes|on-demand|no]::
 158         This option controls if and under what conditions new commits of
 159         populated submodules should be fetched too. It can be used as a
 160         boolean option to completely disable recursion when set to 'no' or to
 161         unconditionally recurse into all populated submodules when set to
 162         'yes', which is the default when this option is used without any
 163         value. Use 'on-demand' to only recurse into a populated submodule
 164         when the superproject retrieves a commit that updates the submodule's
 165         reference to a commit that isn't already in the local submodule
 166         clone.
 167
 168 -j::
 169 --jobs=<n>::
 170         Number of parallel children to be used for all forms of fetching.
 171 +
 172 If the `--multiple` option was specified, the different remotes will be fetched
 173 in parallel. If multiple submodules are fetched, they will be fetched in
 174 parallel. To control them independently, use the config settings
 175 `fetch.parallel` and `submodule.fetchJobs` (see linkgit:git-config[1]).
 176 +
 177 Typically, parallel recursive and multi-remote fetches will be faster. By
 178 default fetches are performed sequentially, not in parallel.
 179
 180 --no-recurse-submodules::
 181         Disable recursive fetching of submodules (this has the same effect as
 182         using the `--recurse-submodules=no` option).
 183
 184 --set-upstream::
 185         If the remote is fetched successfully, pull and add upstream
 186         (tracking) reference, used by argument-less
 187         linkgit:git-pull[1] and other commands. For more information,
 188         see `branch.<name>.merge` and `branch.<name>.remote` in
 189         linkgit:git-config[1].
 190
 191 --submodule-prefix=<path>::
 192         Prepend <path> to paths printed in informative messages
 193         such as "Fetching submodule foo".  This option is used
 194         internally when recursing over submodules.
 195
 196 --recurse-submodules-default=[yes|on-demand]::
 197         This option is used internally to temporarily provide a
 198         non-negative default value for the --recurse-submodules
 199         option.  All other methods of configuring fetch's submodule
 200         recursion (such as settings in linkgit:gitmodules[5] and
 201         linkgit:git-config[1]) override this option, as does
 202         specifying --[no-]recurse-submodules directly.
 203 endif::git-pull[]
 204
 205 -u::
 206 --update-head-ok::
 207         By default 'git fetch' refuses to update the head which
 208         corresponds to the current branch.  This flag disables the
 209         check.  This is purely for the internal use for 'git pull'
 210         to communicate with 'git fetch', and unless you are
 211         implementing your own Porcelain you are not supposed to
 212         use it.
 213
 214 --upload-pack <upload-pack>::
 215         When given, and the repository to fetch from is handled
 216         by 'git fetch-pack', `--exec=<upload-pack>` is passed to
 217         the command to specify non-default path for the command
 218         run on the other end.
 219
 220 ifndef::git-pull[]
 221 -q::
 222 --quiet::
 223         Pass --quiet to git-fetch-pack and silence any other internally
 224         used git commands. Progress is not reported to the standard error
 225         stream.
 226
 227 -v::
 228 --verbose::
 229         Be verbose.
 230 endif::git-pull[]
 231
 232 --progress::
 233         Progress status is reported on the standard error stream
 234         by default when it is attached to a terminal, unless -q
 235         is specified. This flag forces progress status even if the
 236         standard error stream is not directed to a terminal.
 237
 238 -o <option>::
 239 --server-option=<option>::
 240         Transmit the given string to the server when communicating using
 241         protocol version 2.  The given string must not contain a NUL or LF
 242         character.  The server's handling of server options, including
 243         unknown ones, is server-specific.
 244         When multiple `--server-option=<option>` are given, they are all
 245         sent to the other side in the order listed on the command line.
 246
 247 --show-forced-updates::
 248         By default, git checks if a branch is force-updated during
 249         fetch. This can be disabled through fetch.showForcedUpdates, but
 250         the --show-forced-updates option guarantees this check occurs.
 251         See linkgit:git-config[1].
 252
 253 --no-show-forced-updates::
 254         By default, git checks if a branch is force-updated during
 255         fetch. Pass --no-show-forced-updates or set fetch.showForcedUpdates
 256         to false to skip this check for performance reasons. If used during
 257         'git-pull' the --ff-only option will still check for forced updates
 258         before attempting a fast-forward update. See linkgit:git-config[1].
 259
 260 -4::
 261 --ipv4::
 262         Use IPv4 addresses only, ignoring IPv6 addresses.
 263
 264 -6::
 265 --ipv6::
 266         Use IPv6 addresses only, ignoring IPv4 addresses.