Would be useful if cherry-picker messages were more prominent
还没有人认领这个 Issue。
- 主要语言
- Python
- 星标
- 65
- 派生
- 47
- 平均合并
- 5 分钟
- 30 天内合并 PR
- 1
描述
As people have learned I am not always the most observant person in the world. My initial attempts to use cherry-picker were complicated by the fact that I paid attention to messages from git cherry-pick, not cherry-picker's own messages. It would be nice if the message sources were better distinguished, either by dimming the messages from git cherry-pick or by coloring the messages from cherry-picker.
If you think something like this would be useful, I could work on a PR. It seems that any desired changes would be straightforward, as current console output already uses click.echo().
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先定位使用 click.echo() 的 cherry-picker 控制台输出,然后将其中的消息与 issue 中描述的 git cherry-pick 输出进行比较。当 cherry-picker 的消息能够在视觉上与 git cherry-pick 的消息区分开,并且相关输出路径都有覆盖时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- cli
- Issue 类型
- 功能
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 48/100