Prompt Buddy logoPrompt Buddy

github · GitHub Actions Docs

Actions Migrating from self-hosted runners to GitHub-hosted runners - GitHub Docs

A guide for transitioning CI/CD workloads from self-hosted runner infrastructure to GitHub-hosted runner environments.

Import to Prompt Buddy

Derived skill

Files assembled from official documentation

Viewing SKILL.md

Actions Migrating from self-hosted runners to GitHub-hosted runners - GitHub Docs

A guide for transitioning CI/CD workloads from self-hosted runner infrastructure to GitHub-hosted runner environments.

When To Use

Use when you need to transition your CI/CD workflows from managing your own runner infrastructure to using GitHub-managed runner environments.

Reference Files

FileContainsUse For
SKILL.mdEntry point: scope, routing table, and workflow.Start here.
docs/actions-migrate-to-github-runners-migrating-from-self-hosted-docs-workflow-guide.mdA tutorial guide outlining the steps to assess CI infrastructure, map requirements, and estimate capacity when migrating from self-hosted to GitHub-hosted runners.Questions about a tutorial guide outlining the steps to assess CI infrastructure, map requirements, and estimate capacity when migrat...
examples/actions-migrate-to-github-runners-migrating-from-self-hosted-docs-github.textA YAML workflow configuration demonstrating the transition from self-hosted runners to GitHub-hosted runners by updating the runs-on property.Exact payloads, commands, or snippets shown in A YAML workflow configuration demonstrating the transition from self-hosted runners to GitHub-hosted runners by updat...

What This Skill Covers

    • GitHub Actions / - Tutorials / - Migrate to GitHub runners
  • Main sections: In this article, 1. Assess your current CI infrastructure, 2. Map your processing requirements to GitHub-hosted runner types, 3. Estimate capacity requirements, 4. Configure runner groups and policies.

Workflow

  1. Open the most relevant file under docs/ for the exact documented workflow and wording.
  2. Open schemas/ files for exact structured contracts.
  3. Open examples/ files for concrete requests, commands, snippets, and manifests.
  4. Do not add behavior or configuration that is not present in the attached source files.

Canonical source: https://docs.github.com/en/actions/tutorials/migrate-to-github-runners