Skip to content

Error fetching pull requests with git remote alias #7835

Closed

Description

Bug Description

  • Extension version: 0.118.1
  • VSCode Version: 1.104.1
  • OS: MacOS Tahoe 26.0
  • Repository Clone Configuration: Using git remote alias (e.g., origin [email protected]:repo-name for work account, and origin [email protected]:repo-name for personal)
  • GitHub Product: GitHub.com

Steps to Reproduce

  1. Clone repository using a non-standard remote alias (e.g., [email protected]:repo-name).
  2. Open repository in VSCode with the Pull Request extension enabled.
  3. Try to fetch pull requests.

Actual Behavior

Error message displayed: Fetching pull requests for remote origin with query failed, please check if the repo undefined is valid.

Additional Information

  • Issue appears only for repositories with non-standard remote alias ([email protected]:repo-name).
  • For personal repositories using standard alias ([email protected]:repo-name), the error does not occur.
  • This issue started appearing about a week ago, previously (about a month ago) it worked fine.

Expected Behavior

Fetching pull requests should work for repositories using non-standard remote aliases as well.

Notes

  • Please let me know if you need any extra logs or details.

Activity

  1. James-Bartman commented on Sep 23, 2025

    @James-Bartman

    I am getting the same error, and when I check the Output console it shows the following:

    2025-09-23 10:31:07.478 [warning] [GitHubRepository+0] Fetching default branch failed: HttpError: Not Found - https://docs.github.com/rest/repos/repos#get-a-repository
    2025-09-23 10:31:07.478 [error] [FolderRepositoryManager+0] Fetching pull request with query failed: HttpError: Not Found - https://docs.github.com/rest/repos/repos#get-a-repository

    I do not know why it is trying to fetch from the docs URL as I have nothing configured for that URL. This is only happening on my org-#####@wwwin-github.<company>.com:<path_to_repo>.git repository though, not when I am opened to a direct git@<company>.com:<path_to_repo>.git.

  2. alexr00 commented on Sep 26, 2025

    @alexr00
    Member

    Duplicate of #4551

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

    *duplicateIssue identified as a duplicate of another issue(s)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions