Skip to content

Commit 04323e9

Browse files
committed
Remove recommendation for git fetch && git merge over git pull
1 parent 515e4e1 commit 04323e9

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

book/03-git-branching/sections/remote-branches.asc

-2
Original file line numberDiff line numberDiff line change
@@ -217,8 +217,6 @@ It will simply get the data for you and let you merge it yourself.
217217
However, there is a command called `git pull` which is essentially a `git fetch` immediately followed by a `git merge` in most cases.
218218
If you have a tracking branch set up as demonstrated in the last section, either by explicitly setting it or by having it created for you by the `clone` or `checkout` commands, `git pull` will look up what server and branch your current branch is tracking, fetch from that server and then try to merge in that remote branch.
219219

220-
Generally it's better to simply use the `fetch` and `merge` commands explicitly as the magic of `git pull` can often be confusing.
221-
222220
[[_delete_branches]]
223221
==== Deleting Remote Branches
224222

0 commit comments

Comments
 (0)