Skip to main content

Github Copilot– Calling the outside world

Good news if you are using Github Copilot Free or Pro! You can now ask Github Copilot to search the web. This feature was already available for Github Business or Enterprise users but now it is in preview for everyone.

To start using this feature, you first need to enable it in your Copilot settings:

Before if you asked a question about data the model was not trained on, you get a response like this:

If we now ask a question in Copilot Chat where the trained model has no information about, it can search on the web. Therefore include @github in your query. Github Copilot will select an appropriate skill to help answering the question:

 

If the web search is not triggered automatically, you can explicitly trigger it by adding @github #web at the start of your query.

Nice!

More information

Web search in GitHub Copilot Chat now available for Copilot Individual - GitHub Changelog

GitHub Copilot · Your AI pair programmer

Managing Copilot policies as an individual subscriber - GitHub Docs

Asking GitHub Copilot questions in your IDE - GitHub Docs

Popular posts from this blog

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

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.

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