SuperAPI AI Directory
Partner中文AI newsFavorites
Skillskf-g-github-actions-self-hosted-runner-label

kf-g-github-actions-self-hosted-runner-label

Office & productivity

View repository

Updated 10-15 20:24

About this skill

GitHub Actions self-hosted runner label conventions

Treat this SKILL.md as an entry point, and for details read the relevant file under references . The host operations README is the authoritative source for runner binary install / launchd / token acquisition. Cache / mise optimization is handled by the sibling skill kf-g-github-actions-self-hosted-ci-cache .

When to use

  • bootstrap で CI = Mac Studio self-hosted を Applicable when doing
  • .github/workflows/*.yml when creating or modifying
  • When deciding the runs-on of a job in a reusable workflow
  • When a self-hosted job remains waiting in the queue and does not proceed

Prerequisites

  • On a Mac Studio (Apple Silicon / arm64), dedicated to the repo self-hosted runner
  • 1 repo = 1 runner process.<repo-slug> Specify the runner from the workflow using the label
  • Host operation procedure: ~/projects/_github-selfhosted-actions-runner/README.md

Naming conventions (summary)

Concept Convention Example
<repo-slug> GitHub repository name (kebab-case) gitdoc-v2, hacksaw-shop
<label> <repo-slug> Identical to gitdoc-v2
<runner-name> macstudio-<repo-slug> macstudio-gitdoc-v2
config.sh labels self-hosted,macOS,ARM64,<repo-slug> —
workflow runs-on [self-hosted, <repo-slug>] Required

How to read further

  1. runs-on Description and reusable workflow → workflow-runs-on-label.md
  2. Pre-merge checks and troubleshooting → runner-prerequisites.md
  3. cache bootstrap / mise split → kf-g-github-actions-self-hosted-ci-cache

Common checks

  • The host-side runner registration is before the workflow merge か
  • The all jobsto run on self-hosted (including within reusable) is runs-on: [self-hosted, <repo-slug>] か
  • runner の --labels に <repo-slug> is included (Settings → Actions → Runners)
  • If cache optimization is needed, is there a bootstrap step in the sibling skill?

Parallel execution

  • 1 runner process = 1 concurrent job
  • If processes are separated per repo, repos can run in parallel(e.g. gitdoc-v2 + hacksaw-shop simultaneous CI)
  • Within the same repomultiple jobs will wait in the queue if there is only 1 runner