GitHub Copilot Hands-on - lab setup

These instructions will guide you through configuring a GitHub Codespaces environment that you can use to run the course labs. If you prefer and if you know one of the other IDEs supported by Copilot, you can use that. But the instructions will reference the codespace version.

NOTES:

1. We will be working in the public GitHub.com, not a private instance.
2. Chrome may work better than Firefox for some tasks.
3. The default environment will be a GitHub Codespace (with Copilot already installed). If you prefer to use your own IDE, you are responsible for installing Copilot in it. Some things in the lab may be different if you use your own environment.
4. To copy and paste in the codespace, you may need to use keyboard commands - CTRL-C and CTRL-V.
5. VPNs may interfere with the ability to run the codespace. It is recommended to not use a VPN if you run into problems.
6. If you use the new free Copilot plan (no signup), some advanced functionality may not be available. Pro version is free trial for 30 days.
   
   
   

These steps must be completed prior to starting the actual labs.

1. You can use the free version of Copilot for all but one or two items in the labs.

When signed into GitHub, you can verify your Copilot settings by clicking on your profile picture/icon in the upper right and seleting Copilot settings

2. Set codespace timeout (optional but recommended)

While logged in to GitHub, go to https://github.com/settings/codespaces.

Scroll down and find the section on the page labeled Default idle timeout.

Increase the default timeout value to 60 minutes and then select the Save button.

(NOTE: If your codespace does time out at some point in the course, there should be a button to restart it.)

3. Create your own codespace to run the labs by clicking on the button below.

Click here ----->

Then click on the option to create a new codespace.

This will run for several minutes while it gets everything ready.

4. In the Codespace, sign into GitHub (if needed).

After the codespace has started, look in the lower right of the codespace to see if there is a Sign in indicator for Copilot (see figure). If so, click on that and authenticate as needed.

Then select the Copilot icon again and make sure the options under Inline suggestions are enabled.

5. Open the labs

Open the labs document - either in the codespace or in a browser tab.

Any command in the gray boxes is either code intended to be run in the console or code to be updated in a file.

Labs doc: Copilot Hands-on Labs