/pr auto misses review threads
- 主要語言
- Shell
- 星號
- 11.2k
- 分支
- 1.9k
- 平均合併
- 14 小時 16 分鐘
- 30 天內合併 PR
- 6
描述
### Describe the bug
❯ Okay so there aren't any unresolved threads?
● I’ll verify the review thread state directly.
● Check PR review thread resolution state (shell)
│ gh api graphql -f query='query { repository(owner:"AylaLegal", name:"Ayla") { pullRequest(number: 80) { reviewThreads(first: 100) { nodes { isResolved isOutdated path
│ comments(first: 20) { nodes { author { login } body } } } } } } }' 2>&1
└ 2 lines...
● Actually yes — 2 unresolved threads remain.
### Affected version
1.0.63
### Steps to reproduce the behavior
Run /pr auto against a PR with an open review thread
### Expected behavior
It should know to query the review threads and address them
### Additional context
MacOS
GPT-5.4-xhigh
貢獻指南
研究方向
Start by reproducing /pr auto against a pull request with an open review thread, then inspect the GitHub GraphQL reviewThreads query shown in the issue. Trace how /pr auto determines remaining review work and ensure unresolved threads are included in that process. Done means the command detects and addresses open review threads, including the reported case with two unresolved threads.
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- github, shell
- 領域
- cli
- Issue 類型
- 缺陷
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 55/100