0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-08 03:38:23 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 4.8 6b71d3e8bb feat(ci): deploy branch-new roles first on the push priority line

A push resolves the application roles that exist under roles/ locally but
not at origin/main and passes them as the orchestrator priority line, so
brand-new roles deploy and gate ahead of the regular matrix. The resolver
is stdlib-only (git ls-tree plus an application_id line scan) so it runs
on a bare runner without installing the resolver stack, and yields an
empty set when the baseline ref cannot be resolved.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-23 20:01:32 +02:00

container

refactor(structure): nest prefix-grouped sibling files into subfolders

2026-07-14 20:00:03 +02:00

docker

refactor(structure): nest prefix-grouped sibling files into subfolders

2026-07-14 20:00:03 +02:00

git

refactor(structure): nest prefix-grouped sibling files into subfolders

2026-07-14 20:00:03 +02:00

github

refactor(guide): reuse the rescue-diagnostics collector and extract the compose replay

2026-07-23 20:01:31 +02:00

image

…

install

…

inventory

…

lint

chore(lint): add the lint-dockerfile alias and the script execute bit

2026-07-18 20:36:19 +02:00

make

fix(ci): retry-harden every egress path (curl filter, shell downloads, package managers)

2026-07-23 20:01:31 +02:00

README.md

Script Collection

This directory contains automation scripts used across the project.

system/ contains host and system-facing helpers.
container/ contains helpers that run inside the local container.
github/ contains GitHub workflow helper scripts.
For the canonical Make target index, see make.md.
🛠️ Organize operational helpers for development, CI, release, and maintenance
🧭 Separate responsibilities into focused subdirectories with clear scope
📚 Keep script-based workflows discoverable and easier to navigate

The scope of this folder is script organization at the repository level. Detailed responsibilities belong in the README files of the respective subdirectories.