Skip to content

[Bug]: Undetected source-control provider produces misleading "unknown provider" error #19667

Closed

Description

@Guria

Problem

When T3 cannot detect a project's source-control provider, source-control operations can produce this error:

Source control provider unknown failed in listChangeRequests: No unknown source control provider is registered.

The message treats unknown as a provider name and suggests that a provider registration is missing. It does not clearly explain that T3 could not identify the project's source-control provider, making the failure difficult to interpret.

Reproduction condition

A project whose source-control provider remains undetected attempts a change-request lookup. The error above is returned for listChangeRequests.

Expected behavior

The error should distinguish an undetected source-control provider from a known provider that is unavailable, while identifying the operation that failed.

Related reports

Originally reported in PR #11131.

#9170 concerns repeated logging of this condition. This report is limited to the misleading error message, not provider detection or warning frequency.

Activity

  1. juliusmarminge commented on Oct 14, 2026

    @juliusmarminge
    Member

    Note

    Grok responding on behalf of Julius.

    Confirmed on main: unsupportedProvider in SourceControlProviderRegistry.ts builds No ${kind} source control provider is registered. for every operation, so an undetected provider reads as "No unknown … registered".

    The exact error you quoted (listChangeRequests) goes away with open PR #19030. That PR makes the unknown stand-in return an empty list for change-request lookups, which also covers the log flood in #9170. I've linked this issue to that PR so it closes when the PR merges.

    The other operations (getChangeRequest, createChangeRequest, createRepository, …) still use the same wording. Since they only fire when you explicitly ask for something that needs a provider, this is minor polish. For context, #11131 was closed under our contributor model policy, not for its approach. A compliant PR that rewords the unknown case is welcome.

  2. added
    bugSomething is broken or behaving incorrectly.
    via-triageFiled through npx t3 triage
    on Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.via-triageFiled through npx t3 triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions