Files
computer-playbook/scripts/github
kevinveenbirkenbachandClaude Opus 5 00c02251c0 Merge branch 'feature/swarm-nfs' into feature/svc-net-tor
Every conflicted hunk resolves onto the swarm-nfs side, because on all six
files it is the strict superset: it carries the display-name codec
(utils/roles/display.py) the CI role selections now encode through, and the
sequencing glyph move from 910748ec4. svc-net-tor holds no unique content on
any of them -- runs.py even had non-conflicted hunks already calling `codec`,
so keeping its side would have left a NameError.

The lint fallout is settled in the same commit, as 4afc9b770 did for the
previous merge: the shell-or-true lint lives on svc-net-tor (c505ce746) and
swarm-nfs brings two unmarked `|| true` sites with it. Both get a nocheck
reason rather than a rewrite, because neither swallows anything -- the
slaptest call is the measured exception of c4bbbba93 and has_cn_config decides
right below it, and the dockerd restart is followed by an is-active poll that
fatals. In both the exit code was never the authority.

make quality green end to end.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-07 07:47:15 +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.