Travis CI to Actions migrations powered by Valet

The instructions below will guide you through configuring a GitHub Codespace environment that will be used in subsequent labs that demonstrate how to use Valet to migrate Travis CI pipelines to GitHub Actions.

These steps must be completed prior to starting other labs.

Create your own repository for these labs

Ensure that you have created a repository using the valet-customers/labs as a template.

Configure your Codespace

Start a new Codespace.
- Click the Code with button down arrow above repository on the repository's landing page.
- Click the Codespaces tab.
- Click Create codespaces on main to create the codespace.
- After the Codespace has initialized there will be a terminal present.
Verify the Valet CLI is installed and working. More information on the Valet extension for the official GitHub CLI can be found here.
- Run the following command in the codespace's terminal:
```
gh valet version
```
- Verify the output is similar to below.
```
$ gh valet version
gh version 2.14.3 (2022-07-26)
gh valet        github/gh-valet v0.1.12
valet-cli       unknown
```
- If gh valet version did not produce similar output then please follow the troubleshooting guide.

Labs for Travis CI

Perform the following labs to test-drive Valet

Troubleshoot the Valet CLI

The CLI extension for Valet can be manually installed by following these steps:

Verify you are in the codespace terminal
Run this command from within the codespace's terminal:
```
gh extension install github/gh-valet
```

Verify the result of the install contains:

$ gh extension install github/gh-valet
✓ Installed extension github/gh-valet

If you get an error similar to the image below, then click the link in the terminal output to authorize the token.
- Restart the codespace after clicking the link.
Verify Valet CLI extension is installed and working by running the following command from the codespace's terminal:
```
gh valet version
```