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?
I don't know
Describe the bug:
While reading through the book, I noticed that Chapter 2, Section 4 ("Undoing Things") heavily relies on git reset HEAD ... to demonstrate how to unstage a file. While git reset still works for backwards compatibility, modern versions of Git (v2.23+) now explicitly output (use "git rm --cached ..." to unstage) when running git status. To ensure the text aligns with modern terminal hints and best practices, it would be highly beneficial to update this section to prioritize git restore --staged as the primary method for unstaging, while keeping a brief note about legacy git reset functionality.
Expected behavior:
Commands to be updated in the textbook
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?
I don't know
Describe the bug:
While reading through the book, I noticed that Chapter 2, Section 4 ("Undoing Things") heavily relies on git reset HEAD ... to demonstrate how to unstage a file. While git reset still works for backwards compatibility, modern versions of Git (v2.23+) now explicitly output (use "git rm --cached ..." to unstage) when running git status. To ensure the text aligns with modern terminal hints and best practices, it would be highly beneficial to update this section to prioritize git restore --staged as the primary method for unstaging, while keeping a brief note about legacy git reset functionality.
Expected behavior:
Commands to be updated in the textbook