You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: release-notes/v1_95.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,19 +41,19 @@ Copilot features might go through different early access stages, which are typic
41
41
42
42
The new default location for the Chat view is the [Secondary Side Bar](https://aka.ms/vscode-secondary-sidebar). By using the Secondary Side Bar, you can have chat open at any time, while you still have other views available to you like the File Explorer or Source Control. This provides you with a more integrated AI experience in VS Code. You can quickly get to chat by using the `kb(workbench.action.chat.open)` keyboard shortcut.
43
43
44
-
44
+
45
45
46
46
With the introduction of the new Chat menu next to the Command Center, bringing up the Secondary Side Bar with chat is just a click away:
47
47
48
48
<videosrc="images/1_95/chat-video.mp4"title="Chat in Secondary Side Bar."autoplayloopcontrolsmuted></video>
49
49
50
50
The chat menu gives you access to the most common tasks for Copilot Chat. If you wish to hide this menu, a new setting `setting(chat.commandCenter.enabled)` is provided.
51
51
52
-
52
+
53
53
54
54
**Note:** If you had previously installed GitHub Copilot, a view will show up at the location you had Chat before that enables you to restore the Chat view to the old location, if that works better for you.
55
55
56
-
56
+
57
57
58
58
### Automatic chat participant detection
59
59
@@ -69,7 +69,7 @@ If the automatically selected participant is not appropriate for your question,
69
69
70
70
This month, we also added a command to let you skip this behavior on a per-request basis. "Send and dispatch" is the default command run when pressing "enter". "Send" will just send the request directly to Copilot Chat, and it won't be automatically dispatched to a chat participant.
71
71
72
-
72
+
73
73
74
74
You can also disable automatic participant detection entirely with the following setting.
75
75
@@ -93,19 +93,19 @@ Symbol links are rendered as little pills in the response, just like the [file l
93
93
94
94
You can also hover over the symbol link to see which file the symbol is defined in:
95
95
96
-
96
+
97
97
98
98
To start exploring a symbol in more detail, just right-click on the symbol link to bring up a context menu with options, such as **Go to Implementations** and **Go to References**:
99
99
100
-
100
+
101
101
102
102
Basic symbol links should work for any language that supports Go to Definition. More advanced IntelliSense options, such Go to Implementations, also require support for that language. Make sure to install language extensions to get the best symbol support for any programming languages used in Copilot responses.
103
103
104
104
### Fix using Copilot action in the Problem hover
105
105
106
106
The Problem hover now includes the action to fix the problem using Copilot. This action is available for problems that have a fix available, and the fix is generated by Copilot.
107
107
108
-
108
+
109
109
110
110
### Workspace indexing
111
111
@@ -115,11 +115,11 @@ First up, the new **GitHub Copilot: Build Local Workspace index** command lets y
115
115
116
116
While the index is being built, we now also show a progress item in the status bar:
117
117
118
-
118
+
119
119
120
120
Indexing workspaces with many hundreds of files can take a little time. If you try to ask an `@workspace` question while indexing is being constructed, instead of waiting, Copilot will try to respond quickly by using a simpler local index that can be built up more quickly. We now show a warning in the response when this happens:
121
121
122
-
122
+
123
123
124
124
Notice that Copilot was still able to answer the question in this case, even though it used the simpler local index instead of the more advanced one. That's often the case, although more ambiguous or complex questions might only be answerable once the smarter index has been constructed. Also keep in mind that if your workspace is backed by a GitHub repository, we can instead use [GitHub's code search](https://github.blog/2023-02-06-the-technology-behind-githubs-new-code-search) to answer questions. That means that code search is used instead of the simpler local index.
125
125
@@ -139,7 +139,7 @@ Last milestone, we introduced the ability to perform a semantic search using Cop
139
139
140
140
Graduating last month's feature to the default behavior, it's now possible to be logged in to multiple GitHub accounts in VS Code at the same time.
141
141
142
-
142
+
143
143
144
144
Here are a couple of scenarios in which you might need multiple accounts:
145
145
@@ -156,7 +156,7 @@ Last month, we introduced the [Account Preference Quick Pick](./v1_94.md#change-
156
156
157
157
One of the pieces of feedback we received was around wanting an easy way to add an account that is not yet logged in. This milestone, we have introduced a new item in the Quick Pick that enables you to do just that. Use the **Use a new account...** item to start an authentication flow and set the account preference to that account in one go.
158
158
159
-
159
+
160
160
161
161
### Settings editor indicator for Experimental and Preview settings
In this milestone, we have added more icons for profiles. You can now choose from a wider range of icons to customize your profile.
174
174
175
-
175
+
176
176
177
177
### View Icons in Panel
178
178
179
179
In the workbench panel, views are typically displayed as labels in the title bar. However, on smaller screens, these labels can exceed the available space, causing some views to overflow into a dropdown menu. To address this, we’ve added a new setting: setting(workbench.panel.showLabels:false). When disabled, views are displayed as icons instead of labels, conserving horizontal space and reducing overflow.
188
188
189
189
## Editor
190
190
@@ -213,11 +213,11 @@ Version [0.100.0](https://github.com/microsoft/vscode-pull-request-github/blob/m
213
213
214
214
The new `@githubpr` Chat Participant can search for issues on GitHub.
215
215
216
-
216
+
217
217
218
218
When displaying issues, `@githubpr` will show a markdown table and try to pick the best columns to show based on the search.
219
219
220
-
220
+
221
221
222
222
#### Summarizing and Fixing with Copilot
223
223
@@ -274,7 +274,7 @@ chat participant, which is capable of handling questions that likely need live i
274
274
You can invoke it manually using
275
275
`@websearch when did Workspace Trust ship in vscode?`
276
276
277
-
277
+
278
278
279
279
##### Chat Tool
280
280
@@ -284,7 +284,7 @@ chat tool as well, which is similar to the participant but is useful for providi
284
284
For example:
285
285
*`@workspace /new #websearch create a new web app written in Python using the most popular framework`
286
286
287
-
287
+
288
288
289
289
Additionally,
290
290
if you are working on your own Chat Particpant or Tool,
@@ -438,7 +438,7 @@ The expand/collapse state of a `CommentThread` can be changed using the new `Com
438
438
439
439
Welcome views now support the ability to render codicons. You can do so using the usual `$(icon-name)` in your welcome view.
440
440
441
-
441
+
0 commit comments