Exercise: Your First Extension for GitHub Copilot

[github-actions]

Your First Extension for GitHub Copilot

👋 Hey there wtobis-splunk! Welcome to your Skills exercise!

Get excited! We're about to learn how to make your favorite AI pair programmer even better by extending it with some customized skills!

As you complete each step, I will respond in the comments to:

• check your work and give feedback
• share next steps
• occasionally share tips
• congratulate you when you finish!

Good luck and have fun!
- Mona

[github-actions]

Step 1: Preparing to make your extension

Welcome to "Your first extension for GitHub Copilot" exercise! 🤖

We will be making an extension for GitHub Copilot by creating a web service, connecting to a GitHub App, and customizing it to our needs (the staff of a high school). But before we get started, let's learn a bit more about extensions.

What is a GitHub Copilot Extension?

A GitHub Copilot Extension is an add-on that provides customized abilities for GitHub Chat and github.com. That means, it can be more dynamic and include consistent context.

For example:

• Querying documentation: A Copilot Extension can allow Copilot Chat to query a third-party documentation service to find information about a specific topic.
• AI-assisted coding: A Copilot Extension can use a third-party AI model to provide code suggestions.
• Data retrieval: A Copilot Extension can allow Copilot Chat to query a third-party data service to retrieve information about a specific topic.
• Action execution: A Copilot Extension can allow Copilot Chat to execute a specific action, such as posting to a message board or updating a tracking item in an external system.

In fact, you can even publish your extension on the GitHub Marketplace to share it with the world!

Ref: For more information, see the About building extensions page.

How do I make an extension?

Creating an extension is fairly easy. It includes 3 parts, which we will learn in this lesson.
Naturally, the web service must be hosted, but that is covered in another lesson. For this exercise, we will use a Codespace.

1. GitHub App - Enables message handling and communicating with GitHub Copilot.
2. Extension Service - A standard web service for receiving the messages, performing the custom actions, and responding back to GitHub Copilot.
3. Extension Content - Materials provided to your extension to customize it for your application.

Important

A GitHub Copilot Extension is NOT the GitHub Copilot VS Code Extension found in your IDE, but rather an extra capability to enhance it.

flowchart LR

   %% User
   user@{ shape: circle, label: "User" }
   ide@{ shape: div-rect, label: "IDE
                                 (Copilot Chat)" }

   %% Extension
   github_app@{ shape: div-rect, label: "GitHub App" }
   extension_content@{ shape: docs, label: "Extension Content"}
   %% extension_calls@{ shape: docs, label: "Function Calls"}
   %% extension_resource@{ shape: cyl, label: "Other
   %%                                         Resources" }
   extension_service@{ shape: subproc, label: "Extension Service" }

   %% Copilot
   copilot_service@{ shape: curv-trap, label: "Copilot
   Services" }

   %%% Main Flow
   user -- "**@my-ghc-extension**:
            How do I...?" --> ide
   --> github_app --> extension_service --response--> ide

   %% Extension Flow
   extension_service --> copilot_service --> extension_service
   extension_content o--o extension_service
   %% extension_resource <--> extension_calls --> extension_service --> extension_calls

Loading

Ok, let's get to developing! 🦾

Before we get started on your extension, we have to configure our development environment.
Fortunately, this has been bootstrapped for us with a pre-configured Codespace.

This development environment includes:

• The Node.js runtime.
• A template GitHub Extension (javascript web app service).
• VS Code launch settings to start your extension in debug mode.

⌨️ Activity: Getting to know your extension development environment

1. Right-click the below button to open the Create Codespace page in a new tab.

   

   • The free tier of Codespaces that comes with all GitHub accounts is fine, assuming you still have minutes available.
   • The default Codespace settings are fine.
   • This repository will provide the additional settings and files for making your extension.

2. Confirm the Repository field is your copy of the exercise, not the original, then click the green Create Codespace button.

   • ✅ Your copy: /wtobis-splunk/skills-your-first-extension-for-github-copilot
   • ❌ Original: /skills/your-first-extension-for-github-copilot

3. Wait a moment for Visual Studio Code to load.

4. Before we continue let's take a moment to familiarize ourselves with the project folder.

   • The left navigation bar is where you can access the file explorer, debugger, and search.
   • The lower panel (Ctrl+J) shows the debugger output, allows running terminal commands, and allows configuring the web service ports.
   • Our template extension is in the ghc-extension-js folder. More on that in the next steps!
   • The index.js file is the entry point for the extension and hosts the web service for Copilot to interact with.
   • The package-lock.json and package.json files define the extension's dependencies.

5. Create a new branch named my-ghc-extension. Ensure it is checked out in VS Code and published to GitHub.

   • Note: Creating this branch triggers the next step in your exercise.

[github-actions]

Please, follow the steps above.
I'll watch your progress in the background to provide feedback. 🧐