Option to limit runner to a particular run or job

**Describe the enhancement** In addition to supporting the `--once` option (#510), it would be useful if a runner could be limited to a specific run or job, exiting once this job is completed (or cancelled or not otherwise queued). A typical use case would be for autoscaling: either via a webhook or polling the [workflow runs API](https://docs.github.com/en/rest/reference/actions#list-workflow-runs-for-a-repository), i would start up the necessary number of workers for the jobs/runs. **Code Snippet** ``` ./run.sh --job=<job_id> # run job matching job_id, or exit if complete/cancelled ``` **Additional information** Similar to the [Buildkite](https://buildkite.com/docs/agent/v3/cli-start) `--acquire-job` option.

Posted by simonbyrne on Jul 29, 2020, 4:48 AM

Tags

• github (Software)

Related issues

• [Meta] Feedback on granular control over Copilot changes
• unexpected status 401 Unauthorized issue
• [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
• [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
• Video stops playing after some minutes
• [MODEL] Claude verbose code comments by default — ignores instructions to stop.