fix(ci): repair never-parsed workflow(s) - #16
Conversation
These files were rejected by the workflow parser before any run could be scheduled: the API reported each name as its file path (the never-parsed fallback), and every run failed at 0s with zero jobs and no logs. - .github/workflows/secret-scanner.yml:ILLEGAL_KEY:rust-secrets:if-hashFiles Validated per file: actionlint, yaml.safe_load, duplicate-key check. Co-Authored-By: Claude Opus 5 <noreply@anthropic.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 ✅ ApprovedFixes an invalid syntax key in the secret-scanner GitHub Actions workflow that prevented GitHub from parsing it. No issues found.
OptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
Important Your trial ends in 7 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
These files were rejected by the workflow parser before any run could be
scheduled: the API reported each name as its file path (the never-parsed
fallback), and every run failed at 0s with zero jobs and no logs.
Validated per file: actionlint, yaml.safe_load, duplicate-key check.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
How this was found
GitHub reports a workflow's
nameas its file path when it has neversuccessfully parsed the file. An estate-wide scan of 425 repos found 263
such workflows across 133 repos.
Verification
Each edited file passes actionlint,
yaml.safe_load, and a duplicate-keycheck. For push-triggered workflows, full verification completes after merge:
the decisive proof is the workflow resolving its declared name instead of
its path.
🤖 Generated with Claude Code