Conversation
hediet
previously approved these changes
Feb 11, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the extension’s chat context integration to match the newer VS Code proposed “chat context provider” API split (workspace vs explicit vs resource), and adjusts provider registrations/types accordingly.
Changes:
- Split PR chat context into a new
WorkspaceContextProvider(workspace context) plus an updatedPullRequestContextProvider(explicit + resource context). - Update
IssueContextProviderto implement the new explicit/resource provider interfaces and method names. - Update chat context provider proposed typings and switch registrations in
extension.tsto the newregisterChat*ContextProviderAPIs.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| src/lm/pullRequestContextProvider.ts | Introduces WorkspaceContextProvider and adapts PR provider to explicit/resource provider APIs. |
| src/lm/issueContextProvider.ts | Migrates issue provider to new explicit/resource provider interfaces and method names. |
| src/extension.ts | Replaces deprecated registerChatContextProvider usage with new workspace/explicit/resource registrations. |
| src/@types/vscode.proposed.chatContextProvider.d.ts | Adds new provider interfaces and registration APIs; marks old API deprecated and updates ChatContextItem shape. |
Comments suppressed due to low confidence (2)
src/lm/pullRequestContextProvider.ts:106
provideExplicitChatContextunconditionally usesthis._reposManager.folderManagers[0]. If there are no folder managers this will throw, and in multi-root workspaces it ignores other repositories. Consider returning an empty list when there are no repos and aggregating PRs across allfolderManagers.
async provideExplicitChatContext(_token: vscode.CancellationToken): Promise<PRChatContextItem[]> {
const prs = await this._prsTreeModel.getAllPullRequests(this._reposManager.folderManagers[0], false);
return prs.items.map(pr => {
return this._prToUnresolvedContext(pr);
});
src/extension.ts:280
- The chat context provider registrations for
githubissuealso aren’t being disposed (the returnedDisposables are ignored). Add these registration disposables (and any disposable providers, if needed) tocontext.subscriptions.
const issueContextProvider = new IssueContextProvider(issueStateManager, reposManager, context);
vscode.chat.registerChatExplicitContextProvider('githubissue', issueContextProvider);
vscode.chat.registerChatResourceContextProvider({ scheme: 'webview-panel', pattern: '**/webview-IssueOverview**' }, 'githubissue', issueContextProvider);
auto-merge was automatically disabled
February 11, 2026 11:57
Pull request was converted to draft
aiday-mar
approved these changes
Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.