You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Statement:
"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."
Corrected Statement:
"git pull will look up which server and branch your current branch is tracking, fetch from that server, and then try to merge that remote branch into your current local branch."
There's no existing/similar bug report.
This report is about a single actionable bug.
This report is about the ProGit book, version 2, English language.
Bug covers book website/pdf
Problem is present in the Pro Git book on the website?
Which version of the book is affected?
Source files
Describe the bug:
The Pro Git v2 book contains a misleading statement about the behavior of git pull in Chapter 3.5
link: https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches
The current statement is:
"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."
This implies that the merge happens in the remote branch, which is incorrect. The correct behavior is that the merge happens in the local branch.
Steps to reproduce:
Expected behavior:
Current Statement:
"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."
Corrected Statement:
"git pull will look up which server and branch your current branch is tracking, fetch from that server, and then try to merge that remote branch into your current local branch."
Screenshots:
Additional context:
Location:
Chapter 3.5, Section Pulling
Link: https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches
Device
desktop
Operating system
macos
Browser/application + version
google chrome
The text was updated successfully, but these errors were encountered: