[3.6 Git Branching - Rebasing] - first example of this section is showing old/wrong terminal output

Open
#2,007 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
git
Domain
documentation

Research direction

Start in the Pro Git source for section 3.6, “Git Branching - Rebasing,” and compare the first rebase example with the output from the reported Git commands. Update the displayed terminal output to the expected current wording and verify the book example on the website or PDF.

Written by the indexing model from the issue text.

Description

bug
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 the following example:

$ git checkout experiment
$ git rebase master
First, rewinding head to replay your work on top of it...
Applying: added staged command

The output from git version 2.48.0-rc0 is updated.

Steps to reproduce:

git checkout experiment
git rebase master

The output from the book is:

First, rewinding head to replay your work on top of it...
Applying: added staged command

Expected behavior:

Expected the following output:

"Successfully rebased and updated refs/heads/experiment."

Screenshots:

No response

Additional context:

No response

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from progit/progit2

All issues in progit/progit2

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.