Add negative refspec examples to 10.5 Git Internals - The Refspec

未关闭 适合新手
#1,816 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

从 issue 中链接的 Git Book“10.5 Git Internals - The Refspec”一节开始，然后对比链接的 pull-fetch 文档和 Stack Overflow 示例。在该节中添加一个子标题和/或 negative refspec 示例，以解释此功能。完成的标准是该章节清楚地涵盖 negative refspec 标记，并且文档能够成功构建。

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

描述

enhancement
General overview of your idea.

Since Git v2.29.0, it has been possible to add negative refspec markers to the fetch config. These are modestly popular, but the documentation is buried in a multi-paragraph explanation on a fairly obscure doc page. Please consider adding a subheading and/or some examples to the relevant section of the Git Book.

What problem will this solve?

Negative refspecs are a fairly helpful tool for people whose upstream branches are not optimally named[^1]. It's a shame that the feature is not more widely covered.

[^1]: This isn't the user's fault. It's the project's fault.

Have you thought about other solutions?

Please feel totally free[^2] to lift, adapt, etc. the text from my Stack Overflow example if that's helpful.

[^2]: For the purposes of this project, any copyright I hold on that answer is waived.

Do you want to help with this enhancement idea?

Maybe Edit: Sure. See #2025

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

贡献指南

打开贡献指南

从这里开始

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

progit/progit2 的其他 Issue

查看 progit/progit2 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

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