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.
These steps must be completed prior to starting the actual labs.
If not, when signed into GitHub, click on your profile picture/icon in the upper right and either select Copilot
OR select Settings->Copilot and sign up.
You can also find help there for using Copilot in other supported IDEs, set the switch for whether or not to allow matching public code suggestions, etc.
Step 2. To create your working environment for the labs, create a codespace by clicking on the button below:
Click on this button ⬇️
Then click on the option to create a new codespace.
This will run for several minutes while it gets everything ready.
- After the codespace has initialized there will be a terminal present.
After the codespace has started, open the labs document by going to the file tree on the left, find the file named labs.md, right-click on it, and open it with the Preview option.)
This will open it up in a tab above your terminal. Then you can follow along with the steps in the labs. 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 Testing Labs
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 90 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. In that case, you will need to run the minikube start command again.)