Suggest checking account preferences when repo access fails #8413
+75
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Users with multiple GitHub accounts (personal/work) often encounter cryptic 404 errors when the extension uses the wrong account for a repository. The "Manage Account Preferences" feature exists but is difficult to discover.
This PR surfaces account preferences when access errors indicate the user may be authenticated with the wrong account.
Changes
src/github/credentials.tsshowWrongAccountModal()- displays modal explaining the user may have multiple accounts, with button to open VS Code's account preferences commandisAuthenticatedForAccountPreferences()- gating check before showing the modalsrc/github/folderRepositoryManager.tsgetPullRequestsForCategory()now trigger the wrong account modal instead of generic warningsrc/view/treeNodes/categoryNode.tsExample Flow
When fetching PRs fails with 404:
Clicking the button invokes
_account.manageAccountPreferencesfor this extension.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.