Now that we are on Fly.io we'll want to replicate the functionality that Vercel was automatically doing for us by creating and configuring a GitHub Action to deploy our site whenever new commits hit the main branch.

Luckily for us there are a number of pre-defined GitHub actions that we can utilize like actions/checkout@v3, actions/setup-node@v3, and superfly/flyctl-actions/setup-flyctl@master. You'll notice that the first two actions are maintained by GitHub where the last is maintained by Fly.io.

During this process you will also need to generate a token to verify your deployment to Fly.io and store that in the repository Action secrets.