Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Run: Use multiple accounts per host, including GitHub.com

オープン
  • 何か問題がありますか？
#9,005 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@TylerLeonhardt がすでに取り組んでいます。

2026年10月1日 から。

評価

この issue はまだ評価されていません。

説明

authentication feature-request GitHubEnterprise

Goal

Use multiple accounts on the same GitHub host concurrently, including separate personal and work accounts on GitHub.com, with explicit repository-to-account selection.

This is the Run phase, building on host-aware connections in Walk (#9004). Crawl (#9003 / #8996) provides basic multi-Enterprise configuration and account switching; Walk adds simultaneous hosts. Neither phase provides simultaneous accounts on one host.

User experience

In one window, a user should be able to work on repository A with one account and repository B with another account on the same host, without repeatedly changing a provider-wide preference. The selected account and its permissions should be clear, and changing one binding should not silently switch unrelated repositories.

Scope

  • Identify connections by provider, issuer/deployment, and account. Do not rely on account labels or native IDs being globally unique.
  • Define an explicit repository-to-account binding and account-picker experience. Do not infer authentication identity from Git commit authorship or a username embedded in a remote URL.
  • Decide where bindings persist, how workspace preferences interact with user preferences, and what happens when a binding is absent, inaccessible, signed out, or removed.
  • Request and validate the intended account and issuer for every repository-bound operation, including reauthentication and scope upgrades. Never silently retry an operation with another account just because it has access.
  • Partition permission-sensitive repository metadata, user caches, reviews/comments, and notifications by connection identity, including when the same repository is accessible to several accounts.
  • Define account selection or aggregation for hostless tools, notifications, clone/search, and agent entry points.
  • Keep sign-in, consent, switching, and removal explicit while reusing native authentication/account UX where the platform supports it.

Design prerequisite

Verify which VS Code authentication and account-preference APIs can express the required bindings before committing to the UX. Coordinate with upstream structured-account identity work rather than encoding identities into display labels or creating a competing preference store without a clear need.

Acceptance

  • Two GitHub.com accounts can operate concurrently on different repositories in one window.
  • Two accounts on the same Enterprise instance can operate concurrently, including different permissions and scope sets.
  • Switching/signing out/re-authenticating one binding does not change another account's repositories or cached state.
  • Ambiguous or missing bindings produce an actionable choice/error, not an unintended account fallback.
  • Regression coverage proves credentials, comments, notifications, and permission-sensitive data do not cross account boundaries, with real-account verification across supported environments.

Related

  • #7745 tracks detecting that the currently selected account may be wrong; that is a related, narrower UX problem rather than simultaneous account support.
  • Walk/Run design outline.
主要言語
TypeScript
スター
2.6k
フォーク
805
平均マージ
1日 23時間
マージ済み PR（30日）
42

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/vscode-pull-request-github のほかの issue

microsoft/vscode-pull-request-github の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。