Skip to content

Commit e83725a

Browse files
committed
Add release note updates
1 parent 815b174 commit e83725a

File tree

7 files changed

+91
-2
lines changed

7 files changed

+91
-2
lines changed
Lines changed: 3 additions & 0 deletions
Loading
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
version https://git-lfs.github.com/spec/v1
2+
oid sha256:be1a03a2a2869d65132321621ade57eb0e1671c8486b19aa8bb81b64a14d2773
3+
size 2477068
Lines changed: 3 additions & 0 deletions
Loading
Lines changed: 3 additions & 0 deletions
Loading
Lines changed: 3 additions & 0 deletions
Loading
Lines changed: 3 additions & 0 deletions
Loading

release-notes/v1_95.md

Lines changed: 73 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,12 +15,13 @@ DownloadVersion: 1.95.0
1515

1616
Welcome to the October 2024 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:
1717

18+
* [Copilot Edits](#start-a-code-editing-session-with-copilot-edits) - Iterate quickly on large changes across multiple files
1819
* [Copilot Chat in Secondary Side Bar](#chat-in-the-secondary-side-bar) - Keep Copilot Chat open and ready to-go while you work
1920
* [Multiple GitHub accounts](#multiple-github-accounts) - Log in to multiple GitHub accounts in VS Code simultaneously
21+
* [Copilot code reviews](#copilot-code-reviews) - Get a quick review pass or a deeper review of uncommitted changes
2022
* [Docstrings with Pylance](#generate-docstrings-with-pylance) - Generate docstring templates for classes or methods
2123
* [Preview settings indicator](#settings-editor-indicator-for-experimental-and-preview-settings) - View experimental and preview settings in the Settings editor
22-
* [File events in vscode.dev](#vs-code-for-the-web-supports-local-file-events) - Change a local file and see the changes in vscode.dev
23-
* [Copilot extensibility showcase](#copilot-extensions-showcase) - Learn how to extend Copilot in your own extension
24+
* [Copilot extensibility](#copilot-extensions-showcase) - Showcasing Copilot extensibility in VS Code
2425

2526
>If you'd like to read these release notes online, go to [Updates](https://code.visualstudio.com/updates) on [code.visualstudio.com](https://code.visualstudio.com).
2627
**Insiders:** Want to try new features as soon as possible? You can download the nightly [Insiders](https://code.visualstudio.com/insiders) build and try the latest updates as soon as they are available.
@@ -37,6 +38,30 @@ Copilot features might go through different early access stages, which are typic
3738

3839
This setting controls a new feature that is still under refinement yet ready to use. Feedback is welcome.
3940

41+
### Start a code editing session with Copilot Edits
42+
43+
> Copilot Edits is currently in preview
44+
45+
**Setting**: `setting(github.copilot.chat.edits.enabled)`
46+
47+
With Copilot Edits, you can start an AI-powered code editing session where you can quickly iterate on code changes. Based on your prompts, Copilot Edits proposes code changes across multiple files in your workspace. These edits are applied directly in the editor, so you can quickly review them in-place, with the full context of the surrounding code.
48+
49+
Copilot Edits is great for iterating on large changes across multiple files. It brings the conversational flow of Copilot Chat and fast feedback from Inline Chat together in one experience. Have an ongoing, multi-turn chat conversation on the side, while benefiting from inline code suggestions.
50+
51+
<video src="images/1_95/copilot-edits-hero.mp4" title="Use Copilot Edits to modify an Express app." autoplay loop controls muted></video>
52+
53+
Get started with Copilot Edits in just three steps:
54+
55+
1. Start an edit session by selecting **Open Copilot Edits** from the Chat menu, or press `kb(workbench.action.chat.openEditSession)`.
56+
57+
![Screenshot showing the Copilot menu in the Command Center, highlighting the Open Edit Session item](images/1_95/copilot-command-center-open-edit-session.png)
58+
59+
1. Add relevant files to the _working set_ to indicate to Copilot which files you want to work on.
60+
61+
1. Enter a prompt to tell Copilot about the edit you want to make! For example, `Add a simple navigation bar to all pages` or `Use vitest instead of jest`.
62+
63+
Get more details about [Copilot Edits](https://code.visualstudio.com/docs/copilot/copilot-edits) in our documentation. Try it out now and provide your feedback through [our issues](https://github.com/microsoft/vscode-copilot-release/issues)!
64+
4065
### Chat in the Secondary Side Bar
4166

4267
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.
@@ -55,6 +80,52 @@ The chat menu gives you access to the most common tasks for Copilot Chat. If you
5580

5681
![Chat view in its old location showing that Chat has moved to the Secondary Side Bar.](<images/1_95/chat-old-location.png>)
5782

83+
### Copilot code reviews
84+
85+
> Copilot code reviews are currently in preview
86+
87+
With GitHub Copilot code review in Visual Studio Code, you can now get fast, AI-powered feedback on your code as you write it, or request a review of all your changes before you push. GitHub Copilot code review in Visual Studio Code is currently in preview. Try it out and provide feedback through [our issues](https://github.com/microsoft/vscode-copilot-release/issues).
88+
89+
There are two ways to use Copilot code review in VS Code:
90+
91+
* **Review selection**: for a quick review pass, select code in the editor and either select **Copilot** > **Review and Comment** from the editor context menu, or use the **GitHub Copilot: Review and Comment** command from the Command Palette. _(This feature is in preview.)_
92+
93+
* **Review changes**: for a deeper review of all uncommitted changes, select the **Copilot Code Review** button in the **Source Control** view, which you can also do in your pull request on GitHub.com. _(Join the [waitlist](https://gh.io/copilot-code-review-waitlist), open to all Copilot subscribers)_
94+
95+
![Request review of uncommited changes](images/1_95/review_diff.png)
96+
97+
Copilot's feedback shows up as comments in the editor, attached to lines of your code. Where possible, the comments include actionable code suggestions, which you can apply in one action.
98+
99+
![Screenshot showing a comment reviewing a code selection](./images/1_95/reviewing_selection.png)
100+
101+
To learn more about Copilot code review, head to the [GitHub code review documentation](https://gh.io/copilot-code-review-docs).
102+
103+
Copilot's quick review on code selection can provide feedback that match the specific practices of your team or project, provided you give the right context. When reviewing selections with custom review instructions, you can define those specific requirements via the `setting(github.copilot.chat.reviewSelection.instructions)` setting. Similar to [code-generation and test-generation instructions](https://code.visualstudio.com/docs/copilot/copilot-customization), you can either define the instructions directly in the setting, or you can store them in a separate file and reference it in the setting.
104+
105+
The following code snippet shows an example of review instructions:
106+
107+
```json
108+
"github.copilot.chat.reviewSelection.instructions": [
109+
{
110+
"text": "Logging should be done with the Log4j ."
111+
},
112+
{
113+
"text": "Always use the Polly library for fault-handling."
114+
},
115+
{
116+
"file": "code-style.md" // import instructions from file `code-style.md`
117+
}
118+
],
119+
```
120+
121+
An example of the contents of the `code-style.md` file:
122+
123+
```markdown
124+
Private fields should start with an underscore.
125+
126+
A file can only contain one class declaration.
127+
```
128+
58129
### Automatic chat participant detection
59130

60131
**Setting**: `setting(chat.experimental.detectParticipant.enabled)`

0 commit comments

Comments
 (0)