Migrating from GitHub-hosted runners

Before

Nothing has to change in a workflow for it to run on Apex. Two things are worth checking:

• Runner labels. runs-on: ubuntu-latest and the other GitHub-hosted labels resolve to the standard Apex runner. A self-hosted label set such as [self-hosted, linux, arm64] resolves the same way it did. Larger sizes are listed in runner sizes.
• Secrets. Repository and organisation secrets are read from GitHub as before; there is nothing to copy.

During

Install the App on the repositories you are moving. Leave GitHub-hosted runners enabled until you have seen the first Apex run on a pull request, then disable Actions on those repositories so each workflow runs once.

After

Checks, annotations and logs continue to appear on the pull request. In addition, every run carries the verdict, the step timing and the flaky-test warnings described in your first run.

Rolling back

Uninstall the App and re-enable Actions. The next push runs on GitHub-hosted runners. No workflow file was changed, so there is nothing to revert.