Fix unhandled rejections from "upstream ref ... is not a GitHub repo"

[Copilot]

When a workspace's branch upstream points at a non-GitHub remote (e.g., a parent folder with a non-GitHub origin), getPullRequestDefaults() throws BadUpstreamError. Two callers fail to handle this, producing repeated unhandled promise rejections in the Debug Console — matching the screenshot in the issue and likely correlating with the reported VS Code unresponsiveness, since the chat context provider re-fires on many events.

Changes

• src/lm/pullRequestContextProvider.ts — WorkspaceContextProvider.provideWorkspaceChatContext awaited getPullRequestDefaults() per folder with no try/catch. Wrap it, skip the offending folder, and debug-log its URI. This is the first stack in the screenshot:

  at getOrigin → getPullRequestDefaults → provideWorkspaceChatContext
  

• src/view/treeNodes/categoryNode.ts — The catch handler did e.response.status === 422, which throws TypeError for any error lacking .response (e.g. BadUpstreamError propagated from extractRepoFromQuery). Because the throw occurs inside the catch, it escapes as a second unhandled rejection (the getPullRequestsForQuery stack in the screenshot). Optional-chained the access:

  if (this.isCopilot && (e?.response?.status === 422) && e.message?.includes('the users do not exist')) {

[Copilot]

Pull request overview

This PR prevents repeated unhandled promise rejections when a workspace folder’s current branch upstream points to a non-GitHub remote, improving stability (especially for frequently re-triggered chat context collection).

Changes:

• Guarded WorkspaceContextProvider.provideWorkspaceChatContext against getPullRequestDefaults() failures by catching and skipping problematic folders with a debug log.
• Made the Copilot-specific error filter in CategoryTreeNode resilient to errors that don’t have an HTTP response object by optional-chaining the status/message access.

Show a summary per file

File	Description
src/lm/pullRequestContextProvider.ts	Catches failures from getPullRequestDefaults() to avoid unhandled rejections during workspace chat context generation.
src/view/treeNodes/categoryNode.ts	Prevents a secondary exception inside a catch block by optional-chaining e.response.status (and message access).

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 0