Skip to main content

Visual Studio –Git line staging

Visual Studio supports staging files from the moment Git support was introduced and most of the time that is sufficient. But sometimes it can be useful to stage chunks of changes in a file instead of a complete file. This feature (also known as interactive staging) was introduced in Visual Studio 2022 v17.2. I never used the feature before so let's see how this works...

Git line staging is still marked as a preview feature but if you are using Visual Studio 2022 v17.2 or higher, it should be enabled by default.

The first thing you should notice when line staging is enabled, is that individual changes are visible in the editor margin. Added, edited or deleted lines are all shown using a different color and annotation:

If we now click on a color margin, an inline Peek Difference view is opened.

Now you can  stage the selected change by clicking on the + Stage Line <LineNumbers> button:

You can also select one or more lines in the Peek Difference view, right click and choose Git –> Stage selected Range to only stage your selection.

Another option is to go to the Git Staging window and choose Compare with Unmodified:

Here you can hover over a specific change and choose + Stage Change:

If you want to stage a specific line, click on a specific line and choose + Stage Line:

Nice!

Remark: At the moment of writing this post, the Visual Studio 2022 v17.6 preview 1 was released that introduced support for unstaging specific lines.

More information: Line-staging (Interactive Staging) - Visual Studio Blog (microsoft.com)

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’: ...