PR overview remains stuck checking mergeability after an UNKNOWN response
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, typescript
- Domain
- developer-experience, frontend
Research direction
Locate the polling code that calls checkMergeability() and setMergeability(), then inspect how the mergeability response is passed into the merge-status view. Update the handling so the calculated mergeability replaces the indefinite checking state, and verify the pull request overview updates after GitHub returns a resolved status.
Written by the indexing model from the issue text.
Description
- 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.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 796
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 43
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-pull-request-github
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug description page issues performance
microsoft/vscode-pull-request-github#8979 · 1 assignee ·
-
grrrrrrr Open~spam
Difficulty 5/5 Over a week Newbie friendliness 5/100
-
grrrrrrr Open~spam
Difficulty 5/5 Over a week Newbie friendliness 1/100
-
microsoft/vscode-pull-request-github#8969 · 1 assignee ·
All issues in microsoft/vscode-pull-request-github
Similar issues
-
blocklist removal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pastelsky/bundlephobia#1122 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100