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)

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more