Chapter 10. Extending Copilot’s Functionality
GitHub Copilot is an amazingly useful tool. It can be made even more useful by extending its capabilities through integration with other tools. This includes ones you can write. The mechanisms for doing this are called extensions.
Copilot extensions enhance the functionality of GitHub Copilot by tailoring it to specific use cases or environments. For example, extensions can integrate custom or third-party applications with Copilot through the chat interface. As an example, you can install a Copilot Docker extension and then ask questions via chat like “@Docker, how do I containerize this project?”
In this chapter, we’ll examine what extensions for GitHub Copilot are and how to find and work with public ones from the marketplace. Then we’ll progress to understanding details about the various types, how they work, and their advantages and disadvantages. And we’ll cover some details on simple, yet useful, implementation examples. But before we cover those topics, we need to clarify some possibly confusing terminology.
Copilot Extensions Versus VS Code Extensions for Copilot
Extensions for Copilot’s functionality can be implemented for one of two different targets. They can be engineered to work on any platform where Copilot Chat is supported (IDEs, GitHub.com, etc.), independent of the platform. Or they can be targeted for VS Code to leverage its underlying functions and only run on that platform (or on another IDE if ported).
Throughout ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access