[Feedback]: Generate the commit message from the diff in Changes → Ship → Commit
还没有人认领这个 Issue。
评估
调研方向
The payload names no source files. Start from the Changes → Ship → Commit view and the default message Changes from Command Code, which is the fallback the request wants kept. Find where the commit is assembled and where the session model is called, then check how the diff and stat are gathered. Done means a generated conventional-commit message fills the editable field, a failure falls back to the default with a non-blocking error, and the user still has to click to commit.
由索引模型根据 Issue 内容生成。
描述
What would you like?
In Command Code Desktop's Changes → Ship → Commit flow, add a way to generate the commit message from the current changes instead of typing it manually or falling back to a static default.
Current behavior (Desktop 0.1.60, macOS)
- The Ship menu has a "Commit message" textarea whose placeholder reads:
Commit message (blank uses "Changes from Command Code"). - Leaving it blank commits with the hardcoded message
Changes from Command Code. - There is no generate action anywhere in the Changes view.
Proposed behavior
- A "Generate" action next to the commit message field (and/or generate automatically when the field is empty), using the current session model.
- The generation should read the diff/stat of everything the commit would include (the Changes view already states that a commit includes all current project changes, not only agent edits).
- Output a conventional-commit style message (
type(scope): subject, plus an optional body). - Keep it editable, and still require the user's click to commit.
- On failure (model unavailable, empty diff, timeout), fall back to the current default message and show a non-blocking error.
Why
Writing the message by hand for every commit is repetitive, and the current workaround is to ask the agent in chat to run git commit or to generate a message and paste it into the field, which breaks the Ship flow.
Environment
- Command Code Desktop 0.1.60
- macOS
- 主要语言
- Shell
- 星标
- 110
- 派生
- 9
- 平均合并
- 12 分钟
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
CommandCodeAI/desktop 的其他 Issue
-
[Bug]: v0.1.61 fails to initialize preload script due to system memory information error on Linux未关闭bug
难度 2/5 1-3 小时 新手友好度 68/100
CommandCodeAI/desktop#167 ·
-
bug
难度 3/5 1-2 天 新手友好度 56/100
CommandCodeAI/desktop#166 ·
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
CommandCodeAI/desktop#164 ·
-
enhancement
难度 4/5 3-5 天 新手友好度 48/100
CommandCodeAI/desktop#163 · 1 个 reaction ·
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
CommandCodeAI/desktop#162 ·
查看 CommandCodeAI/desktop 的全部 Issue
相似的 Issue
-
S3: friction & debt ws:testing
难度 2/5 1-3 小时 新手友好度 72/100
MedakaLang/medaka#5184 ·
维护者通常 1 天内回复
-
automated issue report
难度 1/5 1 小时以内 新手友好度 78/100
a2aproject/A2A#2445 ·
维护者通常 2 天内回复
-
难度 1/5 1 小时以内 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 75/100
MadiroGlobalHealth/UVL-EMR#580 ·
维护者通常 1 天内回复
-
Storage with Nitro Sandboxes: clarify which CSI volumes are supported (third-party NFS volumes fail)未关闭
难度 2/5 1-3 小时 新手友好度 68/100
awsdocs/amazon-eks-user-guide#1259 ·