mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
The retrigger sent only whitelist and priority, so entry-manual.yml applied its own distros default of 'debian'. A run that swept five distros came back as one, and a failure that only reproduces on centos returned green with nothing fixed. The dispatch inputs are not recoverable from the API - it answers inputs: null for a finished workflow_dispatch - so they are read back from the run title. The title format is not copied here: run_name.py parses the workflow's own run-name declaration and derives the literals framing an input, and the tests build their titles through the same helper instead of spelling one out. Known gap: a run from another entry point carries an unrelated title and yields no distros, leaving the retrigger on the workflow default. Job step names carry the list for every entry point and arrive in the same gh call, so that is where to look when it matters. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>