Skip to main content

Custom instructions when using GitHub Copilot

Last week when talking about a new release of the JetBrains AI assistant, I noticed a specific feature I really liked; the prompt library. This allows you to tweak the prompts that are used in specific contexts.

This made me wonder, does a similar feature exists for GitHub Copilot? Let’s find out…

Custom instructions(preview)

For GitHub Copilot, a similar feature is in preview; Custom Instructions. With custom instructions you can provide extra context that will be added to your conversations so that Copilot can generate higher quality responses.

To use this feature, we first need to enable it because it is still in preview. I’ll show you how to this using Visual Studio(check the link at the bottom of this post to see the instructions for VS Code).

  • Open Visual Studio (make sure you have the latest version installed)
  • Go to Tools  -> Options
  • Search for custom instructions
  • Select the checkbox for (Preview) Enable custom instructions to be loaded from .github/copilot-instructions.md files and added to requests.

Now that the feature is enabled, we can use it by creating a copilot-instructions.md file in a .github folder at the root of our repository.

Here is an example I created:

If I now ask Copilot a question, my instructions are taken into account:

 



More information

Adding custom instructions for GitHub Copilot - GitHub Docs

JetBrains AI Assistent–Ollama support

Master Copilot Your Way: Unlocking the Power of Copilot Instructions in Visual Studio!

Labels:

Popular posts from this blog

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

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