Auto-generated session titles no longer include the PR number when prompting to review a PR
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 68/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- github
- 領域
- desktop
研究方向
Start by reproducing the issue in the macOS desktop app with prompts such as "Review PR 1234," comparing title generation in v1.1.21 with v1.1.20 if available. Trace the session-title generation entry point and its handling of pull-request numbers. Done means prompts naming a PR produce distinct titles that include its number, with a regression test covering the behavior.
由索引模型根據 Issue 內容生成。
描述
Short summary
Session titles for PR review prompts dropped the PR number starting in v1.1.21.
Affected version or release
v1.1.21 (macOS). Worked in v1.1.20 or earlier. Not yet tested on v1.1.23.
Installation context
macOS desktop app, project sessions on GitHub repositories.
What happened?
When I start a session by prompting it to review a specific PR, the generated title is now generic and has no PR number. Every PR review session I started after updating to v1.1.21 got the same title. That makes them impossible to tell apart in the sidebar without renaming each one by hand.
Before the update, the same kind of prompt reliably produced titles like "PR 792 review" or "Review PR 799".
Steps to reproduce
- Start a new session in a project.
- Prompt it to review a PR by number, for example "Review PR 1234".
- Wait for the session title to be generated.
- Observe that the title is generic, with no PR number.
Expected behavior
The generated title includes the PR number when the prompt names one, as it did before v1.1.21.
Additional context
- The changelog doesn't list any change to title generation between v1.1.20 and v1.1.21.
- The v1.1.18 entry "pull request numbers no longer appear inline in sidebar rows" seems unrelated. It covers the badge on sessions linked to a PR, and these sessions aren't linked to one. The number used to be part of the generated title itself.
- 主要語言
- 沒有語言資料
- 星號
- 2.1k
- 分支
- 157
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/app 的其他 Issue
-
triage
難度 2/5 1-3 小時 新手友好度 70/100
-
難度 2/5 1-3 小時 新手友好度 65/100
-
難度 2/5 1-3 小時 新手友好度 70/100
-
難度 2/5 1-3 小時 新手友好度 70/100
-
難度 2/5 1-3 小時 新手友好度 70/100
相似的 Issue
-
area:dictation bug P2
難度 2/5 1-3 小時 新手友好度 88/100
uttrflow/uttrflow-swift#1584 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 70/100
-
comp/desktop P3 type/bug
難度 2/5 1-3 小時 新手友好度 86/100
NousResearch/hermes-agent#123437 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 76/100
alexgorbatchev/simple-ptt#61 ·