Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Walk: Use multiple GitHub Enterprise instances concurrently

Aberta
  • Algo errado?
#9,004 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@TylerLeonhardt já está trabalhando nisso.

Desde 1/10/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

authentication feature-request GitHubEnterprise

Goal

Use repositories on multiple GitHub Enterprise instances concurrently in the same VS Code window, with one selected account/client per host. GitHub.com continues to use its separate connection.

This is the Walk follow-up to Crawl (#9003, implemented by #8996). Crawl recognizes multiple configured instances but keeps only one Enterprise account active at a time. This issue removes that host-switching limitation; it is not part of #8996.

User experience

With GitHub.com, Enterprise A, and Enterprise B repositories open, all three should be usable at once. Authenticating, refreshing, or signing out on B should not replace A's connection or disrupt public GitHub repositories.

Scope

  • Introduce host-aware connections while retaining one selected account per host. Reuse the existing credential/authentication owner rather than adding a second source of truth.
  • Resolve a repository's host/deployment identity and request a session with an explicit authorizationServer hint. Validate the returned issuer; session provenance remains authoritative for API destinations.
  • Scope account selection, current-user data, scope upgrades, reauthentication deduplication, failures, and invalidation to the affected host.
  • Include provider/host/deployment identity wherever repository, notification, or cache keys currently rely only on owner/name or native account/session IDs.
  • Make repository-bound PR, issue, review, tool, and agent actions use the repository's connection.
  • Define explicit selection or aggregation for hostless entry points such as notifications and clone/search. Do not silently pick the first configured host or automatically sign into every instance at startup.
  • Keep errors and sign-in prompts local to the affected host. Configuration changes and account removal must not disrupt unrelated connections.

Design decisions before implementation

  • How should SSH remotes that do not uniquely identify a deployment path or API port select an instance?
  • How should native account preferences be represented per host under the single github-enterprise provider?
  • Which hostless views aggregate results, and which ask the user to select a host?

Acceptance

  • GitHub.com plus two Enterprise hosts work simultaneously, including identical owner/repository names and colliding native account/session IDs.
  • An account change, expired token, canceled scope upgrade, or removed instance affects only that host.
  • Tokens, current-user state, cached metadata, comments, and notifications never cross host boundaries.
  • Unavailable or slow hosts do not block healthy repositories, and background refresh does not produce surprise sign-in prompts.
  • Cover desktop, web, and remote extension hosts with product-code tests and a real-account integration pass.

Out of scope

Multiple accounts on the same host, including multiple GitHub.com accounts, belong to Run. This phase does not change Copilot service eligibility or invent new Enterprise authentication providers.

Walk/Run design outline.

Next phase: #9005 (Run: multiple accounts on the same host).

Linguagem predominante
TypeScript
Estrelas
2.6k
Forks
805
Merge médio
1d 13h
PRs com merge (30d)
38

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/vscode-pull-request-github

Todas as issues de microsoft/vscode-pull-request-github

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.