depot-github-runners

Configure and migrate GitHub Actions workflows to Depot-managed runners.

357|255|Updated Nov 1, 2019
One-click install
npx skills add https://github.com/Agoric/agoric-sdk --skill depot-github-runners
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: depot-github-runners
Source: https://github.com/Agoric/agoric-sdk/tree/main/.agents/skills/depot-github-runners
Command: npx skills add https://github.com/Agoric/agoric-sdk --skill depot-github-runners

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Depot-backed GitHub Actions runners give teams a managed, predictable, cost-efficient alternative to GitHub-hosted runners, eliminating self-hosted maintenance headaches.

Core Features & Use Cases

  • Drop-in replacement by changing runs-on labels in workflows.
  • Supports multiple OS runners (Ubuntu, Windows, macOS) with configurable CPU/RAM.
  • Includes Depot Cache integration and Dagger/Dependabot compatibility.
  • Provides egress filtering and Tailscale private endpoint access.

Quick Start

Connect Depot to your GitHub organization and update your workflows to use a Depot runner label such as depot-ubuntu-24.04-4.

Frequently Asked Questions about depot-github-runners

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I replace GitHub-hosted runners with Depot-managed runners in my Actions workflows?

To replace GitHub-hosted runners with Depot-managed runners, you simply change the runs-on labels in your existing GitHub Actions workflows to use a Depot runner label such as depot-ubuntu-24.04-4, functioning as a drop-in replacement.

What operating systems are supported when configuring Depot runners for GitHub Actions?

Depot runners for GitHub Actions support multiple operating systems including Ubuntu Linux, Windows, and macOS environments, allowing you to configure workflows across these platforms with customizable CPU and RAM resources.

Can I use egress filtering and Tailscale networking with Depot GitHub Actions runners?

Yes, you can apply egress filtering and Tailscale networking to configure private endpoint access for Depot GitHub Actions runners, ensuring secure network controls within your CI/CD automation pipeline.

Does Depot runner configuration support Depot Cache integration and Dependabot compatibility?

Yes, Depot runner configuration supports both Depot Cache integration and Dependabot compatibility, alongside Dagger compatibility, to enhance your GitHub Actions workflow performance and dependency management.

Why use Depot-managed runners instead of maintaining self-hosted GitHub Actions runners?

Depot-managed runners provide a predictable, cost-efficient alternative to GitHub-hosted runners, eliminating self-hosted maintenance headaches while offering managed infrastructure for your CI/CD automation.

What is the quick start process for migrating GitHub Actions workflows to Depot runners?

The quick start process for migrating GitHub Actions workflows to Depot runners involves connecting Depot to your GitHub organization and then updating your workflow files to specify a Depot runner label.