Skip to content

PR overview remains stuck checking mergeability after an UNKNOWN response #8953

Description

  • 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:

  1. Open a repository containing an open pull request.
  2. 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.
  3. 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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugIssue identified by VS Code Team member as probable bug

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions