microsoft / microsoft/vscode-pull-request-github
PR overview remains stuck checking mergeability after an UNKNOWN response
还没有人认领这个 Issue。
- 主要语言
- TypeScript
- 星标
- 2.6k
- 派生
- 796
- 平均合并
- 1 天 4 小时
- 30 天内合并 PR
- 46
描述
- Extension version:
0.166.0and0.167.2026091104(pre-release) - VSCode Version:
1.137.0 - OS: macOS
26.6.2(25G83), arm64 - Repository Clone Configuration: Single repository
- GitHub Product: GitHub.com
Steps to Reproduce:
- Open a repository containing an open pull request.
- Open the pull request description from the GitHub Pull Requests view while GitHub reports its mergeability as
UNKNOWN, such as immediately after creating or updating the pull request. - Scroll to the merge-status section and wait for GitHub to finish calculating mergeability.
Expected:
The extension polls again and replaces “Checking if this branch can be merged...” with the calculated mergeability status.
Actual:
“Checking if this branch can be merged...” remains indefinitely, even after GitHub.com and the GitHub API report the pull request as mergeable.
The polling code receives an object shaped like { mergeability, conflicts }, but passes the entire object to setMergeability():
const newMergeability = await checkMergeability();
setMergeability(newMergeability);
It should use:
setMergeability(newMergeability.mergeability);
Related: #4118 reported the same symptom but was closed before this response-shape regression was introduced.
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
定位调用 checkMergeability() 和 setMergeability() 的轮询代码,然后检查 mergeability 响应是如何传递到 merge-status 视图中的。更新处理逻辑,使计算出的 mergeability 替换不确定的检查状态,并验证 GitHub 返回已确定的状态后 pull request 概览会更新。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github, typescript
- 领域
- developer-experience, frontend
- Issue 类型
- 缺陷
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 活跃度
- 活跃
- 描述清晰度
- 描述清楚
- 新手友好度
- 78/100