Replace GitHub runners with Syva sandboxes

Open the Syva project that should own usage, credits, quotas, and job history. GitHub runner setup is scoped to the project you are viewing in the dashboard.

In project settings, choose Connect GitHub and install the Syva GitHub App on the repositories you want to run on Syva. GitHub asks the installer to authorize the app, then redirects back to the dashboard. Syva links repositories to the current project only after GitHub confirms the authorized user is associated with the installation.

Change one workflow job to use the linked runner label. Keep the label narrow while testing so only intended jobs run on Syva.

 jobs:
   test:
-    runs-on: ubuntu-latest
+    runs-on: [self-hosted, syva-linux]
     steps:
       - uses: actions/checkout@v5
       - run: npm test

Runner jobs and linked repositories appear under the Syva project that completed GitHub setup. Webhooks from repositories that have not been connected to a project are ignored.

• The runner has outbound network access so it can talk to GitHub and download action dependencies.
• Persist build artifacts through GitHub Actions artifacts, packages, or your own registry before destroying the sandbox.
• GitHub-hosted runner image parity is not automatic. Add packages to the Syva image when your workflow depends on them.
• macOS and Windows runner replacement are not covered by Syva Linux sandboxes.