[miguelenes]

Adds the digest-pinned github-actions-runner service preset to both service indexes. The preset has no host ports or runner credentials. The companion lerd-add-actions-runner skill installs one short-named gh-runner container and private Docker sidecar per Lerd host, then restricts organization runner-group access to explicitly selected trusted private repositories. Multiple repositories can use the same container; existing workflows remain unchanged until maintainers opt them in.

[miguelenes]

I reviewed the preset changes and moved the runner definition to the base schema because it uses only schema 1 fields. The schema renderer produces no diff, unit checks pass, and the published runner digest resolves to a multi-architecture OCI index.

[Copilot]

🟡 Changes recommended

The unsupported icon breaks logo generation, and the setup documentation omits essential access and platform details.

2 open findings

• Add missing gear service mark or supported glyph · New
• Link companion skill and document platform and security constraints · New

What changed in this PR

Adds a digest-pinned GitHub Actions runner preset and documents its skill-managed setup.

Changes:

• Registers the runner in both service indexes.
• Adds persistent runner configuration.
• Documents setup and credential boundaries.

File	Description
services/​index.json	Registers the preset.
services/​github-actions-runner.yaml	Defines runner storage and runtime settings.
schema/​2/​services/​index.json	Registers the schema-2 entry.
README.md	Documents the runner workflow.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[geodro]

Hey @miguelenes, thanks for the work on this, the digest pinning and the docs are exactly how a preset should be done.

I'm going to pass on it for the store though, and it's not about the quality. The store holds the services most Lerd users will reach for, databases, caches, search, mail, and a runner that pulls an image from one organization doesn't fit that, however well it's built. Same answer I'd give for any image that belongs to a single team.

The good news is that plugins land in 1.38, and a plugin can ship its own services, written in exactly this YAML. Your preset moves over almost as is, the skill goes with it, and it shows up in the service picker for anyone who installs the plugin. Docs are here: https://github.com/lerd-env/lerd/blob/main/docs/features/plugins.md and the catalog is at https://github.com/lerd-env/plugins. If you turn this into a plugin I'll help with whatever's unclear, it's new and you'd be one of the first in.