fix(ci): re-key the a2ml lockfile entry so dogfood-gate can start - #139
Conversation
The runner refuses to start .github/workflows/dogfood-gate.yml: "Unable to resolve action `hyperpolymath/a2ml-ecosystem`: the repository has been renamed or transferred. Run `gh actions-lock` to update the lockfile." The action itself resolves (raw.githubusercontent returns 200 for the old slug by following the rename); what fails is that GitHub resolves the caller to the canonical repo and then looks for THAT slug in this repo's actions.lock, which still keys hyperpolymath/a2ml-ecosystem@main. Re-keying the entry (and the uses: line, so lock and workflow agree without relying on the redirect) restores the gate. Untouched: every other a2ml string here (.a2ml manifests, the a2ml-validate job name, the missing-manifest warnings) is A2ML-language tooling, not a renamed repository.
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (29)
🔇 Additional comments (1)
📝 SummarySummary by CodeRabbit
WalkthroughThe A2ML manifest validation step now uses ChangesValidation action update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the workflow gate Comment |
|



Cause, quoted from the runner
.github/workflows/dogfood-gate.ymltherefore has never run on this repo: the job dies in Set up job, the run reportsfailurewith zero usable steps and no annotation, and nothing in the repo's UI says why.Fix
Two lines:
actions.lockkeyshyperpolymath/deed-ecosystem@mainand theuses:linenames the canonical slug. Verified before writing:
deed-ecosystem/main/validate-action/action.yml-> 200, so the action exists and the gate is worth keeping.
Deliberately not done
a2ml-validatejob. Instandardsthe removal was correct because that stepcalled
secrets-check-action, a path that exists at no commit in that repo; here the path isreal, so re-keying is the fix and deleting would drop a working check.
.a2mlmanifest prose or the missing-manifest warnings: that is the A2MLlanguage, not the renamed repository.
gh actions-lockrun: it rewrites unrelated workflow bytes (symbolic./refs, headercomments) and this repo's lock needs exactly one slug changed.
Found by the estate ghost-app audit (2026-09-21), which measured 17 repos in this class.