Skip to content

Commit 06d4687

Browse files
committed
Add note on workspace perf
1 parent 1941815 commit 06d4687

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

release-notes/v1_96.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,12 @@ Additionally, there is a new, experimental, setting to make an Inline Chat hint
131131

132132
TODO@Tyriar
133133

134+
### Performance improvements for `@workspace`
135+
136+
When you use [`@workspace`](../docs/copilot/workspace-context.md) to ask Copilot about your currently opened workspace, we first need to narrow the workspace down into a set of relevant code snippets that we can hand off to Copilot as context. If your workspaces is backed by a GitHub repo, we can find these relevant snippets quickly by using Github code search. However as the code search index tracks the main branch of your repository, we couldn't rely on it for local changes or when on a branch.
137+
138+
This iteration, we've worked bring the speed benefits of Github search to branches and pull requests. This means that we now search both the remote index based on your repo's main branch, along with searching any locally changed files. We then merge these results together, giving Copilot a fast and up to date set of snippets to work with. You can read more about Github code search and how to enable it [here](https://docs.github.com/en/enterprise-cloud@latest/copilot/github-copilot-enterprise/copilot-chat-in-github/using-github-copilot-chat-in-githubcom#asking-a-question-about-a-specific-repository-file-or-symbol).
139+
134140
## Accessibility
135141

136142
### Code Action accessibility signals

0 commit comments

Comments
 (0)