git-pull

git pull [options] [remote] [branch]

git pull fetches from a remote and integrates the changes with the current branch. It is equivalent to running `git fetch` followed by `git merge`, or `git rebase` when the `--rebase` option is used.
Pull strategies vary by workflow. Some teams prefer merge (preserving all history), others prefer rebase (linear history), and some use `--ff-only` to reject non-fast-forward updates and prevent unexpected merge commits. The `pull.rebase` configuration setting controls default behavior.

--rebase[=true|merges|false]

Rebase current branch on top of upstream after fetching instead of merging.

Merge upstream into current branch (overrides `pull.rebase` config).

Only update if fast-forward is possible, fail otherwise.

Always create a merge commit, even when fast-forward is possible.

Perform the merge but stop before creating a commit.

Squash all fetched commits into a single commit on the current branch.

Fetch from all remotes.

Automatically stash and reapply uncommitted changes.

Add upstream tracking reference for the pulled branch.

Limit fetch to specified number of commits from remote tip.

Fetch all tags from the remote.

Suppress output during fetch and merge.

Be verbose.

Pulling into a dirty working tree can cause conflicts. Use `--autostash` to automatically stash and reapply local changes. The default merge-or-rebase behavior is controlled by the `pull.rebase` configuration setting. Since Git 2.27, `git pull` warns if `pull.rebase` is not set.

git pull has been part of Git since its initial release by Linus Torvalds in 2005. The `--ff-only` option was added in Git 1.6.6. The `--autostash` option was added in Git 2.9.

git-fetch(1), git-merge(1), git-rebase(1), git-stash(1)