mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Opus 5
f482b979bd
test-environment.yml and test-guide.yml become test-workspace.yml and test-instructions.yml. Orchestrator job ids, the distros-SPOT matrix lint, the act example, the diagnostics slug and the rescue artefact names follow. Replace the roles_only input with per-job workspace/instructions tri-state inputs (auto|true|false). 'auto' derives the former roles_only skip straight from whitelist: both jobs run on a global scope (whitelist empty or __ALL__) and are skipped on a role-scoped run, which keeps the PR behaviour identical because the diff resolver never emits an empty whitelist. entry-manual exposes both as choice dropdowns defaulting to false, so a manual run opts in explicitly. The now redundant roles_only output is dropped from pr_affected_roles.sh and subset_roles.py. Branch-protection required-status-check names change along with the job renames. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
GitHub Workflow Helpers 🔧
This directory holds the shell helpers that GitHub Actions workflows under .github/workflows/ call. Helpers are grouped by responsibility into subfolders so each workflow file pulls only from the clusters it actually needs.
Subfolders 🗂️
| Subfolder | Responsibility |
|---|---|
| runner/ | Host-runner hygiene around image builds and deploys (disk, swap, Docker daemon, diagnostics). |
| cancel/ | Cancellation of in-progress workflow runs on PR-close and branch-delete events. |
| cleanup/ | Scheduled repository maintenance that prunes stale GitHub resources. |
| resolve/ | Derivation of structured workflow inputs and outputs from repository state. |
| sync/ | Ref synchronization before workflow jobs derive CI scope from git history. |
| update/ | The scheduled Update: Versions pipeline (version bumps and PR open/refresh). |
| release/ | Release-time gates that decide whether a tagged commit may be released. |
A new helper MUST live in the subfolder that matches its responsibility. New responsibilities MAY motivate a new subfolder, but MUST NOT flatten back into the top level.
For the workflow catalog see workflows.md. For the repository Make target index see make.md.