0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-11 21:26:44 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 b1ca39e9dd feat(cli): stop retriggering CI suites the source run already passed

A retrigger carried the workspace and instructions toggles over from the
run title, so a suite that had already gone green was dispatched again
and spent runners on work with a known answer.

Derive each toggle from the source run's job record instead: a suite is
turned off only when every one of its jobs reports success. A suite that
was skipped, cancelled or never dispatched has not passed, so it is still
asked for; absence of a failure is not evidence of a success. One failing
shard keeps the whole suite on.

Match against the job path rather than the run title by dropping the
workflow-name segment, and fail open when nothing matches, so an unknown
job layout re-runs the suite rather than silently skipping it.

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

2026-08-11 19:28:35 +02:00

status

fix(ci): discover host-mode deploy jobs in the failed-run trigger/status

2026-07-20 12:48:56 +02:00

trigger

fix(ci-trigger): read the priority input from the job log

2026-08-08 19:33:20 +02:00

__init__.py

…

README.md

…

runs.py

feat(cli): stop retriggering CI suites the source run already passed

2026-08-11 19:28:35 +02:00

README.md

CI Deploy Runs 🚦

Inspect and trigger the compose and swarm deploy-test runs for the branch you are on. status summarises each role's per-mode result (docker, swarm, and an aggregated all) from the last run; trigger dispatches a fresh manual run for all roles, only the ones that failed last time, or an explicit list.