Skip to content

Commit e26b523

Browse files
author
bamurtaugh
committed
Doc to use gifs
1 parent dc117c4 commit e26b523

18 files changed

+242
-26
lines changed

blogs/2025/next-edit-suggestions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,11 +70,11 @@ NES can also help with more challenging mistakes in logic, like a return stateme
7070
**Using newly added variables or logic:** Copilot NES helps you use new code you just added. This may be a small change, like calling a new method parameter in the actual method.
7171

7272
It could also be more complex: if you added a new command to your VS Code extension's `extension.ts`, NES will first suggest to clean up the command in `extension.ts`. Then when you open `package.json`, NES may suggest registering that command as well:
73-
![Updating extension.ts and package.json](nes-extension-and-package.gif)
73+
![Updating extension.ts and package.json with a new command](nes-extension-and-package.gif)
7474
<!-- ![Add command in package.json](add-disposable.png) -->
7575
<!-- ![Add command in package.json](call-disposable-full.png) -->
7676

77-
**Refactoring:** If you use a new name or naming pattern, Copilot NES suggests to rename subsequent variables similarly.
77+
**Refactoring:** If you use a new name or naming pattern, Copilot NES suggests to rename subsequent variables similarly. After copy-pasting some code, NES will suggest how to adjust it to match the current code where the paste happened.
7878

7979
## Share your feedback
8080
Copilot NES is rapidly evolving, and we can't wait to get your feedback via issues in [our repo](https://github.com/microsoft/vscode-copilot-release) – this will be instrumental to improving the experience.

docs/copilot/ai-powered-suggestions.md

Lines changed: 26 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -63,9 +63,9 @@ The following example shows how to instruct Copilot to create a class in TypeScr
6363

6464
## Next Edit Suggestions (preview)
6565

66-
Inline suggestions are great at autocompleting a section of code. But since most coding activity is editing existing code, it's a natural evolution of Copilot completions to also help with edits, both at the cursor and further away. Edits are often not made in isolation - there's a logical flow of what edits need to be made in different scenarios. Copilot Next Edit Suggestions (aka "Copilot NES") is this evolution.
66+
Inline suggestions are great at autocompleting a section of code. But since most coding activity is editing existing code, it's a natural evolution of Copilot code completions to also help with edits, both at the cursor and further away. Edits are often not made in isolation - there's a logical flow of what edits need to be made in different scenarios. Copilot Next Edit Suggestions (aka "Copilot NES") is this evolution.
6767

68-
Based on the edits you're making, NES both predicts the location of the next edit you'll want to make and what that edit should be. NES helps you stay in the flow, suggesting future changes relevant to your current work, and you can simply `kbstyle(Tab)` to quickly navigate and accept Copilot's suggestions. Suggestions may span a single symbol, an entire line, or multiple lines, depending on the scope of the potential change.
68+
Based on the edits you're making, Copilot NES both predicts the location of the next edit you'll want to make and what that edit should be. NES helps you stay in the flow, suggesting future changes relevant to your current work, and you can simply `kbstyle(Tab)` to quickly navigate and accept Copilot's suggestions. Suggestions may span a single symbol, an entire line, or multiple lines, depending on the scope of the potential change.
6969

7070
> [!NOTE]
7171
> Copilot NES is currently in preview. You can enable NES via the VS Code setting `setting(github.copilot.nextEdits.enabled)`.
@@ -76,51 +76,53 @@ Based on the edits you're making, NES both predicts the location of the next edi
7676
>
7777
> You can learn more about [managing policies for Copilot in your organization](https://docs.github.com/en/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization#enabling-copilot-features-in-your-organization).
7878
79-
<!-- TODO: Add video from blog -->
79+
![Video overview of Copilot NES in VS Code](./images/inline-suggestions/nes-video-silent.mp4)
80+
<!-- TODO: Update to video with voiceover from Olivia -->
8081

8182
### Navigate and accept edit suggestions
8283

8384
You can quickly navigate suggested code changes with the `kbstyle(Tab)` key, saving you time to find the next relevant edit (no manual searching through files or references required). You can then accept a suggestion with the `kbstyle(Tab)` key again.
8485

85-
An arrow in the gutter indicates if there is an edit suggestion available:
86-
![NES with right arrow](./images/inline-suggestions/scan-right-highlight.png)
87-
88-
If an edit suggestion is below the current editor view, the arrow will point down instead of right:
89-
![NES with down arrow](./images/inline-suggestions/scan-down-highlight.png)
86+
An arrow in the gutter indicates if there is an edit suggestion available. If an edit suggestion is below the current editor view, the arrow will point down instead of right:
87+
![NES with arrow directions changing](./images/inline-suggestions/nes-arrow-directions.gif)
88+
<!-- ![NES with right arrow](./images/inline-suggestions/scan-right-highlight.png) -->
89+
<!-- ![NES with down arrow](./images/inline-suggestions/scan-down-highlight.png) -->
9090

9191
You can hover over the arrow to explore the edit suggestion menu, which includes keyboard shortcuts and settings configuration:
9292
![NES gutter menu expanded](./images/inline-suggestions/gutter-menu-highlighted.png)
9393

9494
### Use cases for Next Edit Suggestions
9595

96-
**Changing intent**
96+
**Catching and correcting mistakes**
9797

98-
* **Copilot suggests changes to the rest of your code that match a new change in intent.** For example, when changing a class from `Point` to `Point3D`, Copilot will suggest to add a `z` variable to the class definition:
99-
![NES for updating Point to Point3D](./images/inline-suggestions/point3d.png)
98+
* **NES helps with simple mistakes like typos.** It'll suggest fixes where letters are missing or swapped, like `cont x = 5` or `conts x = 5`, which should've been `const x = 5`.
99+
![NES fixing a typo from "conts" to "const"](./images/inline-suggestions/nes-typo.gif)
100+
* **NES can also help with more challenging mistakes in logic**, like where a statement should've had `<` instead of `<=`:
101+
![NES fixing a fibonacci logic mistake](./images/inline-suggestions/nes-fib-logic.gif)
102+
or a comparison that should've used `&&` instead of `||`:
103+
![NES fixing an if statement mistake](./images/inline-suggestions/nes-de-morgan.gif)
100104

101-
After accepting the change, NES next recommends adding `z` to the distance calculation:
102-
![NES for adding z to distance calculation of Point3D](./images/inline-suggestions/point3d-distance.png)
105+
**Changing intent**
103106

104-
**Adding new variables or logic**
107+
* **Copilot suggests changes to the rest of your code that match a new change in intent.** For example, when changing a class from `Point` to `Point3D`, Copilot will suggest to add a `z` variable to the class definition. After accepting the change, NES next recommends adding `z` to the distance calculation:
108+
![NES gif for updating Point to Point3D](./images/inline-suggestions/nes-point.gif)
109+
<!-- ![NES for updating Point to Point3D](./images/inline-suggestions/point3d.png)
110+
![NES for adding z to distance calculation of Point3D](./images/inline-suggestions/point3d-distance.png) -->
105111

106-
* **Using newly added arguments, variables, or functions**. Copilot NES helps you use new code you just added. This may be a small change, like calling a new method parameter in the actual method.
112+
**Adding new variables or logic**
107113

108-
It could also be more complex: if you added a new command to your VS Code extension's `extension.ts`, NES will first suggest to clean up the command in `extension.ts`:
109-
![Add command in package.json](./images/inline-suggestions/add-disposable.png)
114+
* **Using newly added arguments, variables, or functions**. NES helps you use new code you just added. This may be a small change, like calling a new method parameter in the actual method.
110115

111-
And then when you open `package.json`, NES may suggest registering that command as well:
112-
![Add command in package.json](./images/inline-suggestions/call-disposable-full.png)
116+
It could also be more complex: if you added a new command to your VS Code extension's `extension.ts`, NES will first suggest to clean up the command in `extension.ts`. Then when you open `package.json`, NES may suggest registering that command as well:
117+
![Updating extension.ts and package.json with a new command](./images/inline-suggestions/nes-extension-and-package.gif)
118+
<!-- ![Add command in package.json](./images/inline-suggestions/add-disposable.png)
119+
![Add command in package.json](./images/inline-suggestions/call-disposable-full.png) -->
113120

114121
**Refactoring**
115122

116123
* **Rename a variable once in a file, and Copilot will suggest to update it everywhere else.** If you use a new name or naming pattern, Copilot suggests to rename subsequent variables similarly.
117124
* **Matching code style**. After copy-pasting some code, Copilot will suggest how to adjust it to match the current code where the paste happened.
118125

119-
**Correcting mistakes**
120-
121-
* **Copilot helps with mistakes like typos.** It'll suggest fixes where letters are missing or swapped, like `cont x = 5` or `conts x = 5`, which should've been `const x = 5`.
122-
* **Copilot can also help with mistakes in logic**, like where a statement should've had `<` instead of `<=`, or an `OR` statement that should've been an `AND`.
123-
124126
## Tips & tricks
125127

126128
### Context
Lines changed: 3 additions & 0 deletions
Loading

0 commit comments

Comments
 (0)