can name an arbitrary remote ref (for example, the name of a tag) or even a collection of refs with corresponding remote-tracking branches (e.g., refs/heads/*:refs/remotes/origin/*), but usually it is the name of a branch in the remote repository.ĭefault values for and are read from the "remote" and "merge" configuration for the current branch as set by git-branch(1) -track.Īssume the following history exists and the current branch is " master": A-B-C master on origin should be the name of a remote repository as passed to git-fetch(1). More precisely, git pull runs git fetch with the given parameters and then depending on configuration options or command line flags, will call either git rebase or git merge to reconcile diverging branches.
#Git fetch vs pull origin how to
If the current branch and the remote have diverged, the user needs to specify how to reconcile the divergent branches with -rebase or -no-rebase (or the corresponding configuration option in pull.rebase). If the current branch is behind the remote, then by default it will fast-forward the current branch to match the remote. Incorporates changes from a remote repository into the current branch. Download changes from given remote repository and branch, then merge them into HEAD: git pull remote_name branch.Download changes from default remote repository and use fast-forward: git pull -rebase.Download changes from default remote repository and merge it: git pull.
Fetch from and integrate with another repository or a local branch Examples (TL DR)
0 kommentar(er)
