Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[3.3 Git Branching - Branch Management] - tip 'git branch --no-merged master' does not work or is not clear

未关闭
#2,005 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
git
领域
documentation

调研方向

Start by locating the English Pro Git source for section 3.3, “Git Branching - Branch Management,” and inspect the tip containing git branch --no-merged master. Clarify the surrounding text or example so readers understand what topicA and featureB represent, then verify the result on the book website and in the generated PDF.

由索引模型根据 Issue 内容生成。

描述

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 section '3.3 Git Branching - Branch Management' there is the following tip:

$ git checkout testing
$ git branch --no-merged master
topicA
featureB

Reading the tip text and the output of the command, I got the impression that topicA and featureB are issues or functions, and not branches, since topicA and featureB are never mentioned earlier in the book.

Steps to reproduce:
  1. Go to '...'
  2. Click on '...'
  3. 'Scroll down to '...'
  4. See error
Expected behavior:

Clear tip text

Screenshots:

No response

Additional context:

No response

Device

No response

Operating system

No response

Browser/application + version

No response

主要语言
CSS
星标
6.6k
派生
2.1k
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

progit/progit2 的其他 Issue

查看 progit/progit2 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。