Skip to content

Route GHE.com remotes through enterprise authentication - #8870

Draft
alexr00 with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-ghe-data-residency-issue
Draft

Route GHE.com remotes through enterprise authentication#8870
alexr00 with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-ghe-data-residency-issue

Conversation

Copilot AI commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

GHE.com remotes could be classified as Enterprise but still use the GitHub.com authentication provider, causing repository queries to fail and the PR panel to appear empty.

Changes

  • Derive GitHubRemote.authProviderId from its detected server type:
    Enterprise    github-enterprise
    GitHubDotCom  github
    None          existing URI-based fallback
  • Log each remote’s server classification and selected authentication provider.
  • Add regression coverage for Enterprise and GitHub.com remotes.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Co-authored-by: alexr00 <38270282+alexr00@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix repo-scoped queries showing zero in PR panel Route GHE.com remotes through enterprise authentication Jul 31, 2026
Copilot AI requested a review from alexr00 July 31, 2026 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GHE.com data residency: repo-scoped queries bound to github.com provider — PR panel shows 0 in all categories (clean-profile repro included)

2 participants