rack_remote/master have changed to rack_remote/main
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- git
- Domain
- documentation
Research direction
Start at Git Tools -> Advanced Merging -> Subtree Merging in the Pro Git source, then run the three reproduction commands from the report against the rack remote. Update the example so its remote branch reference matches the current rack repository, and verify the corrected example appears in the website/PDF 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:
In Git Tools -> Advanced Merging -> Subtree Merging
Code in the example:
git checkout -b rack_branch rack_remote/master error occured:
fatal: 'rack_remote/master' is not a commit and a branch 'rack_branch' cannot be created from it
Steps to reproduce:
- git remote add rack_remote https://github.com/rack/rack
- git fetch rack_remote --no-tags
- git checkout -b rack_branch rack_remote/master
Expected behavior:
Screenshots:
No response
Additional context:
The reason is that rack_remote/master has changed to rack_remote/main
Device
No response
Operating system
No response
Browser/application + version
No response
- Dominant language
- CSS
- Stars
- 6.6k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Contributor 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
-
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
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
git/git-scm.com#2207 ·
-
link-check link-check:sphinx-theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
CSCfi/sd-search-api#39 ·
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 85/100