Skip to main content

Github Copilot Edits

I continue my journey on getting the most out of Github Copilot. Today I want to take a look at Copilot Edits as another way to use AI in your day-to-day coding experience. Until recently, you either had to use completions or the chat experience. 

With Copilot Edits, a third option is added to the list.

Why Copilot Edits?

Where the completions or the chat experience are a great fit for single file changes, they can be cumbersome for bigger changes that span multiple files. When using Copilot Edits, you can specify a set of files that should edited and then ask Copilot to do some changes. 

Remark: At the moment of writing Copilot Edits seems only to be available inside VS Code and not (yet) in Visual Studio.

Let’s give it a try…

  • Click on the Github Copilot icon at the top and choose Open Copilot Edits from the dropdown(or just hit CTRL-Shift-I)


  • This will open up the Copilot Edits view where we can start a new editing session.

 

  • First we need to add a set of files to our Working Set. Therefore click on + Add Files and choose the files that should be part of the working set. Copilot will only apply changes to these files.
    • Remark: At the moment the working set is limited to 10 files.

 

  • Now we can enter a chat prompt telling the change that we want taking our working set into account.

 

  • We now have the option to go through all the changes and either Accept or Discard them.

 

  • The edits are not saved to disk automatically. You can save the files by clicking on the Save icon.
    • Remark: This doesn’t mean that the changes are accepted automatically.

 

  • If you are happy with the final set of changes you can click Accept.
  • Click on Done to end the editing session.

This first experience of this new feature was certainly positive. Would be nice if I could define the working set by just specifying it as text(e.g. Edit all razor files...).

Update:  
  • I was able to mimic the behavior I mentioned above by first entering my request in the Copilot Chat experience:


  • And then I hit the Edit with Copilot button:
  • Copilot automatically added all impacted files to the working set and when I click on Rerun in the Chat window it starts to apply the change. Nice!

More information

Copilot Edits

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...