Skip to main content

GitHub Copilot–Code referencing

One of the risks of using tools like GitHub Copilot, is that we start to over rely on these tools and that we blindly accept any suggestion or code change it wants to make. This is not so different than what we had before with the ‘copy-paste’ programmer who just copied the first snippet he could find online. But with the integration of AI inside our IDE’s, it has become a lot easier to just accept these changes without questioning the quality of the suggestion or its source, especially as these tools can generate bigger and bigger code blocks.

This is where Code Referencing can help. It introduces a filter that detects when code suggestions match public code on GitHub, providing you with valuable context to make more informed decisions about the code you are about to incorporate into your projects.

Let’s give it a try!

Enable Code Referencing

Before we can use this feature, we have to check if it is enabled.

  • In the upper-right corner of any page on GitHub, click your profile photo, then click Your Copilot.

  • Next to Suggestions matching public code, use the dropdown menu to select Allowed or Blocked.

Remark: If you are a member of an organization and have been assigned a GitHub Copilot seat through your organization, you may not be able to configure this from your personal account settings.

Using Code Referencing

Now that the feature is active, we get a message when matches are found in a code repository:

The first time you accept such a code change, you also get a toast notification when you accept a completion that matches public code. The notification contains information about the matching code, the repository where the code was found and any associated license information.

This gives you some context about the origin of the code suggestion and if you would like to accept it or not.

After that, the same details are available in your GitHub Copilot Output Window, including the license type and a link to the GitHub.com, the public repository where the original code is located:

 

If you had chosen to block suggestions, you get a message like this:

Remark: Code referencing is available starting from Visual Studio 2022 17.13.

 

More information

Introducing Code Referencing for GitHub Copilot Chat in Visual Studio - Visual Studio Blog

Introducing Code Referencing for GitHub Copilot Completions in Visual Studio - Visual Studio Blog

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