Solutions
My own runners take every job — how do SolveLang runners get work?
Route chosen pull requests to SolveLang with a label, so your own fleet and SolveLang share the work the way you decide.
Symptom
You bought runner minutes, but your jobs keep running on your own runners and your SolveLang balance never moves.
Cause
SolveLang can only start a machine for a job that is still waiting in GitHub's queue. When one of your own runners is free, GitHub usually hands the job to it first — that is normal, and you are never billed for a job your own runners ran.
If you want specific work to run on SolveLang, you have to say so. The way to say it is a label.
Fix
Route chosen pull requests to SolveLang with label routing:
- Decide which pull requests should run on SolveLang — for example, your biggest test suites.
- Add the label
solvelangto those pull requests. - Add a small rule to your workflow so that jobs on a labeled pull request ask for SolveLang's runner labels, like the example below. Pull requests without the label keep the labels they already use.
- Add the label before the run starts. If a run is already going, push a new commit so a fresh run picks the label up.
Example
This workflow keeps the usual self-hosted label for ordinary pull requests, and asks for SolveLang's Standard runners when the pull request carries the solvelang label:
jobs:
test:
runs-on: ${{ contains(github.event.pull_request.labels.*.name, 'solvelang') && fromJSON('["self-hosted", "solvelang-runners-standard"]') || fromJSON('["self-hosted"]') }}Labeled pull requests now run on SolveLang and draw from your minutes; everything else runs exactly as before.