Incorrect description of git pull behavior in Chapter 3.5 of Pro Git book V2
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 58/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- git
- Domain
- documentation
Research direction
Locate the Pro Git v2 source for Chapter 3.5, “Git Branching - Remote Branches,” and find the “Pulling” section. Update the statement so it clearly says that git pull merges the fetched remote branch into the current local branch, then verify the wording in the generated book output.
Written by the indexing model from the issue text.
Description
There's no existing/similar bug report.
- I have searched the existing issues
This report is about a single actionable bug.
- I'm reporting a single actionable bug
This report is about the ProGit book, version 2, English language.
- This bug is not about a translation or old version
Bug covers book website/pdf
- I confirm the bug is about the book as found on the website/pdf
Problem is present in the Pro Git book on the website?
- This bug also affects the Pro Git book as published 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:
- Go to https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches
- Scroll down to "Pulling" section
- See error
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
- Dominant language
- CSS
- Stars
- 6.6k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from progit/progit2
-
Difficulty 1/5 Under an hour Newbie friendliness 87/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
AI-Agent/Queued Type/Bug
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
approved documentation
Difficulty 1/5 Under an hour Newbie friendliness 89/100
vitest-dev/vitest#12015 · 4 comments ·
Maintainers usually reply within 1 day
-
Pri3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/windows-dev-docs#6205 ·