Files
computer-playbook/scripts/github
kevinveenbirkenbachandClaude Opus 5 71888d86af refactor(ci): prefix workflows by trigger
The workflow directory mixed entry points, reusable stages and scheduled jobs into one flat list sorted by topic, so the first question about any file - what starts it - was the one the name did not answer. Every workflow now carries one of three prefixes, derived from its on: block: cron- for a schedule trigger, call- for one only reachable through workflow_call, entry- for everything a repository event or a human starts. Scheduled workflows additionally carry an alarm clock as the first character of their name.

Two lints keep it that way. One derives the expected prefix from the triggers and compares it against the file name; it flagged all 17 offenders before the rename and none after. The other resolves every .github/workflows/<file> string in the repository against the directory, which is what a rename silently breaks in Markdown links, Python constants and shell API URLs alike.

Renaming pulled 69 pre-existing comments into the comment lint's changed-file scope. The vendored CodeQL template got the nocheck marker its scorecard sibling already carried, two workflow headers moved above name: where they count as file headers, and the remaining banners were deleted.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-07 17:05:51 +02:00
..
2026-06-27 21:36:30 +02:00

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.