Update alt texts
This commit is contained in:
Nick Trogh
Родитель
e080b55c37
Коммит
e9c44b5602
|
|
@ -41,7 +41,7 @@ Copilot features might go through different early access stages, which are typic
|
|||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
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:
|
||||
|
||||
|
|
@ -49,11 +49,11 @@ With the introduction of the new Chat menu next to the Command Center, bringing
|
|||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
**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.
|
||||
|
||||
|
||||
|
||||
|
||||
### Automatic chat participant detection
|
||||
|
||||
|
|
@ -69,7 +69,7 @@ If the automatically selected participant is not appropriate for your question,
|
|||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
You can also disable automatic participant detection entirely with the following setting.
|
||||
|
||||
|
|
@ -93,11 +93,11 @@ Symbol links are rendered as little pills in the response, just like the [file l
|
|||
|
||||
You can also hover over the symbol link to see which file the symbol is defined in:
|
||||
|
||||
|
||||
|
||||
|
||||
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**:
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
|
@ -105,7 +105,7 @@ Basic symbol links should work for any language that supports Go to Definition.
|
|||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
### Workspace indexing
|
||||
|
||||
|
|
@ -115,11 +115,11 @@ First up, the new **GitHub Copilot: Build Local Workspace index** command lets y
|
|||
|
||||
While the index is being built, we now also show a progress item in the status bar:
|
||||
|
||||
|
||||
|
||||
|
||||
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:
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
|
@ -139,7 +139,7 @@ Last milestone, we introduced the ability to perform a semantic search using Cop
|
|||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
Here are a couple of scenarios in which you might need multiple accounts:
|
||||
|
||||
|
|
@ -156,7 +156,7 @@ Last month, we introduced the [Account Preference Quick Pick](./v1_94.md#change-
|
|||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
### Settings editor indicator for Experimental and Preview settings
|
||||
|
||||
|
|
@ -172,7 +172,7 @@ _Theme: [Light Pink](https://marketplace.visualstudio.com/items?itemName=mgwg.li
|
|||
|
||||
In this milestone, we have added more icons for profiles. You can now choose from a wider range of icons to customize your profile.
|
||||
|
||||
|
||||
|
||||
|
||||
### View Icons in Panel
|
||||
|
||||
|
|
@ -180,11 +180,11 @@ In the workbench panel, views are typically displayed as labels in the title bar
|
|||
|
||||
**`workbench.panel.showLabels: true`**
|
||||
|
||||
|
||||
|
||||
|
||||
**`workbench.panel.showLabels: false`**
|
||||
|
||||
|
||||
|
||||
|
||||
## Editor
|
||||
|
||||
|
|
@ -213,11 +213,11 @@ Version [0.100.0](https://github.com/microsoft/vscode-pull-request-github/blob/m
|
|||
|
||||
The new `@githubpr` Chat Participant can search for issues on GitHub.
|
||||
|
||||
|
||||
|
||||
|
||||
When displaying issues, `@githubpr` will show a markdown table and try to pick the best columns to show based on the search.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Summarizing and Fixing with Copilot
|
||||
|
||||
|
|
@ -274,7 +274,7 @@ chat participant, which is capable of handling questions that likely need live i
|
|||
You can invoke it manually using
|
||||
`@websearch when did Workspace Trust ship in vscode?`
|
||||
|
||||
|
||||
|
||||
|
||||
##### Chat Tool
|
||||
|
||||
|
|
@ -284,7 +284,7 @@ chat tool as well, which is similar to the participant but is useful for providi
|
|||
For example:
|
||||
* `@workspace /new #websearch create a new web app written in Python using the most popular framework`
|
||||
|
||||
|
||||
|
||||
|
||||
Additionally,
|
||||
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
|
|||
|
||||
Welcome views now support the ability to render codicons. You can do so using the usual `$(icon-name)` in your welcome view.
|
||||
|
||||
|
||||
|
||||
|
||||
### Chat participant access to model picker
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче