Skipbox documentation
Run your GitHub Actions jobs on Skipbox: setting up, labels and sizes, plans and the trial, security, and fixes for common problems.
Getting started
Runners
- Labels and sizesThe runs-on labels Skipbox answers to, the VM size each gives, and which plans run each size.
- Runner imageWhat a Skipbox VM has installed, the user a job runs as, and how to add the tools GitHub's ubuntu-latest has and Skipbox doesn't.
- Concurrency and queueingHow many jobs run at once on your plans, what happens to a job that doesn't fit, and where you see the queue.
- Job time limitA Skipbox job can run for up to the same number of hours as on GitHub-hosted runners, counted from when its VM starts.
- Network and egressWhere Skipbox VMs run, what they can reach, what is blocked, and what that means for latency and allowlists.
Accounts and billing
- Organizations and personal accountsWhich Skipbox app to install on a GitHub organization or a personal account, who installs it, and who can buy plans.
- PlansWhat each Skipbox plan costs a month, the vCPU it adds, the largest job it runs, and how plans add up.
- Free trialHow long Skipbox's free trial lasts, what it runs, when it starts, who gets one, and what happens when it ends.
- Billing, invoices and refundsHow Skipbox charges, where to find invoices, the refunds it gives, and what happens when a payment fails.
- Cancel and uninstallHow to cancel Skipbox plans, what runs until the end of the paid month, how to uninstall the app, and how to delete your account.
Security
- GitHub App permissionsEvery permission the Skipbox CI and Skipbox (personal) apps ask for, what Skipbox does with each, and what neither asks for.
- VM isolationHow Skipbox keeps jobs apart: one new VM per job, deleted with its disk, a runner for one job, no inbound connections, and private repositories only.
- Data kept and deletedWhat Skipbox records about your account and jobs, what it never keeps, and when each record is deleted.
Troubleshooting
- A job stays queuedWhy a job set to a Skipbox label waits on GitHub, how to read the reason on your account's page, and what to do for each.
- Jobs blocked by GitHub's spending limitWhen GitHub says a job wasn't started because of failed payments or the spending limit, fix the budget, or move the job to Skipbox.
- A job fails after movingThe usual reasons a job that passed on GitHub's runners fails or doesn't start on Skipbox, and the fix for each.