Launchpad shows "needs reviewers" for mergeable PRs with no required or requested reviewers

Summary

GitLens Launchpad classifies a GitHub pull request as needs reviewers even though GitHub reports no requested reviewers and the repository ruleset requires zero approving reviews.

This makes the Launchpad status look like a merge-blocking review requirement when, in fact, no review is required.

Steps to reproduce

1. Create or use a GitHub repository with a ruleset / branch protection rule that:

   • requires pull requests for changes to main
   • requires status checks
   • requires signed commits
   • requires 0 approving reviews

2. Open a pull request that:

   • is not a draft
   • is mergeable
   • has no requested reviewers
   • has no requested team reviewers

3. Enable the GitLens Launchpad status-bar indicator.

4. Observe the PR in the Launchpad / status bar.

Actual behavior

GitLens shows a status such as:

owner/repo#23 needs reviewers

However, the pull request has:

• mergeable: true
• draft: false
• requested_reviewers: []
• requested_team_reviewers: []
• required_approving_review_count: 0

GitHub itself does not indicate that a review is required.

Expected behavior

GitLens should not classify the pull request as needs reviewers when:

• no reviewers are requested, and
• no approving reviews are required by the repository ruleset.

If GitLens intentionally distinguishes between "no reviewers assigned" and "review required", the wording should make that distinction explicit.

Possible alternatives could be:

• do not include the PR in a needs reviewers category
• show no reviewers assigned
• only show needs reviewers when a review is actually required or explicitly requested

Why this is confusing

The wording needs reviewers strongly implies that a review is required before the pull request can be merged.

That is misleading for repositories where the ruleset explicitly uses:

required_approving_review_count = 0

In this case, the pull request can be merged once the other required conditions are satisfied, but GitLens still presents it as needing reviewers.

This can easily be confused with GitHub branch protection or ruleset requirements.

Additional context

The affected pull request is generated automatically by a GitHub Actions workflow, but merging remains manual.

The repository intentionally uses:

• pull requests for changes to main
• required status checks
• signed commits
• zero required approving reviews

The pull request is therefore intentionally valid without reviewer approval.

Environment

• GitLens: 19.3.0
• Visual Studio Code
• Windows 11
• GitHub integration enabled
• Launchpad status-bar indicator enabled