Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| The Runners page shows the machines a workspace's agents and workflow jobs run on, in Workspace under Compute: g1t's cloud beside your own runners, what each is running now with a link to it, what's waiting, this month's machine time and its cost (your own runners' free), where agent work and workflow jobs run, adding a runner, and groups; runner_activity in Actions says what runs where, work handed to your runners keeps its agent run, and the self-hosted runners guide says how. | 1 | -- The agent run a task handed to a self-hosted runner belongs to, so the |
| 2 | -- Runners page can link a runner's agent work to it and leave it out of | |
| 3 | -- what runs on g1t's cloud. Null for tasks handed over before this. | |
| 4 | ALTER TABLE runner_tasks ADD COLUMN run_id TEXT; | |
| 5 | ||
| 6 | -- What runs in g1t's sandboxes for a workspace now, for the Runners page: | |
| 7 | -- jobs without labels, by the lowercased workspace and status. | |
| 8 | CREATE INDEX IF NOT EXISTS jobs_cloud_lower ON jobs (lower(namespace), status) WHERE labels IS NULL; |
