- Extension version:
0.166.0 and 0.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.
0.166.0and0.167.2026091104(pre-release)1.137.026.6.2(25G83), arm64Steps to Reproduce:
UNKNOWN, such as immediately after creating or updating the pull request.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 tosetMergeability():It should use:
Related: #4118 reported the same symptom but was closed before this response-shape regression was introduced.