Module fetch

Functions

• all
  Fetch all remotes. –all
• 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. -a, –append
• deepen
  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. –deepen=
• 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= option (see git-clone(1)), deepen or shorten the history to the specified number of commits. Tags for the deepened commits are not fetched. –depth=
• dry_run
  Show what would be done, without making any changes. –dry-run
• fetch
• force
  When git fetch is used with : refspec, it refuses to update the local branch unless the remote branch it fetches is a descendant of . This option overrides that check. -f, –force
• ipv4
  Use IPv4 addresses only, ignoring IPv6 addresses. -4, –ipv4
• ipv6
  Use IPv6 addresses only, ignoring IPv4 addresses. -6, –ipv6
• jobs
  Number of parallel children to be used for fetching submodules. Each will fetch from different submodules, such that fetching many submodules will be faster. By default submodules will be fetched one at a time. -j, –jobs=
• keep
  Keep downloaded pack. -k, –keep
• multiple
  Allow several and arguments to be specified. No s may be specified. –multiple
• no_recurse_submodules
  Disable recursive fetching of submodules (this has the same effect as using the –recurse-submodules=no option). –no-recurse-submodules
• 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..tagOpt setting. -n, –no-tags
• 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. –progress
• prune
  Before fetching, remove any remote-tracking references that no longer exist on the remote. -p, –prune
• quiet
  Pass –quiet to git-fetch-pack and silence any other internally used git commands. Progress is not reported to the standard error stream. -q, –quiet
• recurse_submodules
  This option controls if and under what conditions new commits of populated submodules should be fetched too. –recurse-submodules[=yes|on-demand|no]
• recurse_submodules_default
  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 gitmodules(5) and git-config(1)) override this option, as does specifying –[no-]recurse-submodules directly. –recurse-submodules-default=[yes|on-demand]
• refmap
  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. –refmap=
• shallow_exclude
  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. –shallow-exclude=
• shallow_since
  Deepen or shorten the history of a shallow repository to include all reachable commits after . –shallow-since=
• submodule_prefix
  Prepend to paths printed in informative messages. –submodule-prefix=
• 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. -t, –tags
• 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. –unshallow
• 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. -u, –update-head-ok
• 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 accept such refs. –update-shallow
• upload_pack
  When given, and the repository to fetch from is handled by git fetch-pack, –exec= is passed to the command to specify non-default path for the command run on the other end. –upload-pack
• verbose
  Be verbose. -v, –verbose