syntaqxThe desktop app's Runner settings show each kind of job as a card of its own, and each starts and stops on its own. Linux jobs and Windows jobs (macOS jobs once they are released) sit side by side, one under the other in a narrow window: an icon and name, a label for its state (Running a job, Waiting for jobs, Starting, Downloading image with how far, Updating, Waiting for image, Stopped, Not available, Problem), a line of what it is, the job it is running with a link to it, and when it isn't running why and the fix, with the fix's buttons and its own Stop or Start; its runner's name on g1t, version and isolation sit quietly below. Above the cards there is only what is about the whole runner (signed out, no workspace, turned off, stopped, the sandbox down), so nothing is said twice. Commands in the catalogue's sentences show as code, state changes are announced to screen readers, and the breathing dot stops under reduced motion.894c28bHistory
- ..
- deploy
- emoji
- ops
- perf
- build-runner.mjs
- build-rust-worker.mjs
- cli-release.mjs
- cloudflare-setup.py
- conformance-diff.mjs
- deploy.mjs
- deploy.sh
- desktop-release.mjs
- desktop-release.test.mjs
- mobile-release.mjs
- mobile-release.test.mjs
- runner-release.mjs
- runner-release.test.mjs
- sandbox-image.mjs
- sccache.sh
- setup-custom-domains.sh
- setup-deployments.sh