Repository navigation
fix(ci): adopt the Actions lockfile — every workflow was startup_failure - #71
Conversation
Every workflow in this repo returns startup_failure in 0s, and has for its entire recent history, so it has had no working CI at all. Workflow-lockfile enforcement is active on this account and this repo had no .github/workflows/actions.lock. Applied the cure proven on haec #50 and trope-particularity-workbench #45. It takes four steps because each one's failure is invisible until the previous is fixed — they surface strictly one at a time: 1. gh actions-lock generates the lockfile and normalises pins to tags. 2. Hoist SPDX back to line 1. actions-lock inserts its own banner there and the workflow linter requires SPDX first, so the tool that cures the startup failures reddens every workflow file unless this is undone. 3. Hand-author an empty [] lockfile entry per reusable-workflow caller. gh actions-lock SKIPS callers, so without this they stay startup_failure while everything else goes green. 4. Re-pin those callers to standards bd0df9ead7fa, the commit that made the governance check lockfile-aware, verified via the commits API. Expect previously-unseen failures. Nothing here has been checked in a long time, so the first green run is a starting point rather than a result. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
|
|
Note Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime. Code Review ✅ ApprovedAdopts the GitHub Actions lockfile and resolves reusable caller entries to fix persistent startup failures across all CI workflows. No issues found.
OptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
Important Your trial ends in 5 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more. Was this helpful? React with 👍 / 👎 | Gitar |
![gitar-bot[bot]](https://avatars.githubusercontent.com/in/827041?s=60&v=4){kind=small}
1 participant
Every workflow in this repo returns
startup_failurein 0s, so nothing here has been checked.Workflow-lockfile enforcement is active on this account and this repo had no
.github/workflows/actions.lock.Applied the cure proven on haec#50 and trope-particularity-workbench#45. It takes four steps because each failure is invisible until the previous is fixed — they surface strictly one at a time, which makes this look intermittent when it is not:
gh actions-lock— generates the lockfile, normalises pins to readable tags.actions-lockputs its banner there and the workflow linter requires SPDX first, so the cure reddens every workflow file unless this is undone in the same commit.[]lockfile entry per reusable caller (5 here) —actions-lockskips callers, so without this they staystartup_failurewhile everything else goes green.bd0df9ead7fa, verified via the commits API.Expect previously-unseen failures. The first green run is a starting point, not a result.
Found during the 2026-08-05 estate CI/CD census.
🤖 Generated with Claude Code