-
--all
-
Fetch all remotes.
-
-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
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 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
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 git-fetch(1) for details.
This is incompatible with --recurse-submodules=[yes|on-demand] and takes
precedence over the fetch.output config option.
-
-f
-
--force
-
When git fetch is used with <src>:<dst> refspec, it may
refuse to update the local branch as discussed
in the <refspec> part of the git-fetch(1)
documentation.
This option overrides that check.
-
-k
-
--keep
-
Keep downloaded pack.
-
--prefetch
-
Modify the configured refspec to place all refs into the
refs/prefetch/ namespace. See the prefetch task in
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.
-
--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 git-config(1).
-
--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).
-
-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 git-config(1)).
Typically, parallel recursive and multi-remote fetches will be faster. By
default fetches are performed sequentially, not in parallel.
-
--set-upstream
-
If the remote is fetched successfully, add upstream
(tracking) reference, used by argument-less
git-pull(1) and other commands. For more information,
see branch.<name>.merge and branch.<name>.remote in
git-config(1).
-
--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.
-
--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 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 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 GIT URLS below) or the name
of a remote (see the section REMOTES below).
-
<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
(see the section "CONFIGURED REMOTE-TRACKING BRANCHES"
in git-fetch(1)).
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 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
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 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 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 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. |
|
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. |