Skip to main content

Extend Github Copilot capabilities through the Copilot Marketplace

I already talked about custom instructions in Github Copilot as a way to tweak Github Copilot. Today I want to show another way to extend the capabilities of your Copilot; Copilot Extensions, a set of third party tools, services, and data available (in preview) through the Copilot marketplace:

 

 

What are Copilot Extensions?

Copilot extensions are third-party tools, services, and data integrations that enhance the functionality of GitHub Copilot. They allow you to leverage additional features and capabilities directly within your coding environment. Whether you need help with code quality, security, documentation, or project management, there's likely a Copilot extension that can assist you.

At the moment of writing this post Copilot Extensions is still in preview and the list of available extension is still limited. Extension usage is not possible in every IDE. Here is the list of supported IDEs:

 

How to get started with Copilot Extensions

Getting started with Copilot extensions is easy. Follow these steps to enhance your Copilot experience:

  1. Explore the Marketplace: Visit the GitHub Marketplace to browse and discover Copilot extensions. You can filter by type, creator, and popularity to find the extensions that best suit your needs.

  2. Install the Extension: Once you've found an extension you like, click on it to view more details and follow the installation instructions. Most extensions can be installed directly from the Marketplace.

  3. Configure and Use: After installation, configure the extension according to your preferences. Each extension may have its own setup process, so be sure to follow the provided documentation.

  4. Integrate with Copilot: Start using the extension within your coding environment. Copilot extensions are designed to seamlessly integrate with GitHub Copilot, providing you with enhanced functionality and support.

Let’s give it a try…

Let’s apply the steps above with a concrete example. Yesterday I talked about how I generated a mermaid diagram using Copilot. Turns out that there is an extension exactly for that: Mermaid Chart · GitHub Marketplace.

On the extension detail page, click on Add.

This will bring you to the bottom of the page where you can select the account and organization:

We click on Install it for free to continue. We now arrive on the Review your order screen where you can click on Complete order and start installation.

As a last step, we need to set the user permissions for this extension. Click on Install.

Finally, the extension is installed and we can give it a try.

Remark: If you are using a Copilot Business/Enterprise subscription, you may need to ask an admin of your organization to install and activate the extension.

To use the extension, we need to execute the @Mermaid-Chart command when in the Copilot chat window. The first time you use it; you are asked to authorize the extension.

After authorizing, we finally get an answer to our question:

Let’s now try generating a diagram:

We can directly view the diagram in the Mermaid Chart playground:

 

Sweet!

Conclusion

Copilot extensions are a powerful way to extend the capabilities of GitHub Copilot and streamline your development workflow. By leveraging these third-party tools and services, you can improve code quality, enhance security, automate documentation, and much more.

So, explore the Marketplace, find the extensions that work for you, and unlock the full potential of GitHub Copilot.

More information

Extending the capabilities of GitHub Copilot in your organization - GitHub Docs

Custom instructions when using GitHub Copilot

Marketplace

Mermaid Chart · GitHub Marketplace

Labels:

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

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more