All Fetch all remotes.

AllowUnrelatedHistories By default, git merge command refuses to merge histories that do not share a common ancestor.

Append Append ref names and object names of fetched refs to the existing contents of .git/FETCH_HEAD.

Autostash Before starting rebase, stash local modifications away if needed, and apply the stash when done.

Commit Perform the merge and commit the result.

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.

Depth Limit fetching to the specified number of commits from the tip of each remote branch history.

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.

Ff When the merge resolves as a fast-forward, only update the branch pointer, without creating a merge commit.

FfOnly Refuse to merge and exit with a non-zero status unless the current HEAD is already up-to-date or the merge can be resolved as a fast-forward.

Force When git fetch is used with <rbranch>:<lbranch> refspec, it refuses to update the local branch <lbranch> unless the remote branch <rbranch> it fetches is a descendant of <lbranch>.

Ipv4 Use IPv4 addresses only, ignoring IPv6 addresses.

Ipv6 Use IPv6 addresses only, ignoring IPv4 addresses.

Keep Keep downloaded pack.

Log In addition to branch names, populate the log message with one-line descriptions from at most <n> actual commits that are being merged.

NoAutostash --no-autostash is useful to override the rebase.autoStash configuration variable.

NoCommit With --no-commit perform the merge but pretend the merge failed and do not autocommit, to give the user a chance to inspect and further tweak the merge result before committing.

NoEdit The --no-edit option can be used to accept the auto-generated message (this is generally discouraged).

NoFf Create a merge commit even when the merge resolves as a fast-forward.

NoLog With --no-log do not list one-line descriptions from the actual commits being merged.

NoRebase Override earlier --rebase.

NoRecurseSubmodules This option controls if new commits of all populated submodules should be fetched too.

NoSquash With --no-squash perform the merge and commit the result.

NoStat With -n or --no-stat do not show a diffstat at the end of the merge.

NoTags By default, tags that point at objects that are downloaded from the remote repository are fetched and stored locally.

NoVerifySignatures Verify that the tip commit of the side branch being merged is signed with a valid key, i.e.

Progress Progress status is reported on the standard error stream by default when it is attached to a terminal, unless -q is specified.

Quiet This is passed to both underlying git-fetch to squelch reporting of during transfer, and underlying git-merge to squelch output during merging.

Rebase When true, rebase the current branch on top of the upstream branch after fetching.

RecurseSubmodules This option controls if new commits of all populated submodules should be fetched too.

Refspec Specifies which refs to fetch and which local refs to update.

Repository The "remote" repository that is the source of a fetch or pull operation.

ShallowExclude Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag.

ShallowSince Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.

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).

Stat Show a diffstat at the end of the merge.

Strategy Use the given merge strategy; can be supplied more than once to specify them in the order they should be tried.

StrategyOption Pass merge strategy specific option through to the merge strategy.

Unshallow If the source repository is complete, convert a shallow repository to a complete one, removing all the limitations imposed by shallow repositories.

UpdateHeadOk By default git fetch refuses to update the head which corresponds to the current branch.

UpdateShallow By default when fetching from a shallow repository, git fetch refuses refs that require updating .git/shallow.

UploadPack 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.

Verbose Pass --verbose to git-fetch and git-merge.

VerifySignatures Verify that the tip commit of the side branch being merged is signed with a valid key, i.e.