Skip to content

Commit dd134d0

Browse files
hyperpolymathclaude
andcommitted
fix(ci): repair workflow-linter.yml — GitHub cannot parse it, so it has never run
This workflow file is invalid YAML. GitHub refuses it at parse time, so it produces NO run, NO check-run, NO annotation and NO log. Not a red X — an absence. Nothing on a dashboard distinguishes "this gate passed" from "this gate does not exist", which is why it went unnoticed. The tell is the Actions API reporting the workflow's name as its FILE PATH instead of its `name:` — GitHub registers a file it cannot parse under its path: name = ".github/workflows/workflow-linter.yml" path = ".github/workflows/workflow-linter.yml" <- name == path The repair is purely positional; no step, command or argument is altered. Depending on the file it is one of: * a step appended at JOB level (2-space indent) moved back inside the preceding job's `steps:` list; or * a multi-line shell string whose continuation fell out of its `run: |` block scalar, re-indented so it stays inside. YAML strips that indent again when parsing, so the shell receives the identical string. VERIFIED before push, not assumed: * the file parses and yields a `jobs:` mapping; * every `- name:` present before is still a step after; * exactly one file changed. Part of a measured estate-wide repair: 211 invalid workflow files across 116 repos, confirmed by the Actions API. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 4bb4d50 commit dd134d0

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

.github/workflows/workflow-linter.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ jobs:
5555
done
5656
if [ $failed -eq 1 ]; then
5757
echo "Add 'permissions:
58-
contents: read' at workflow level"
58+
contents: read' at workflow level"
5959
exit 1
6060
fi
6161
echo "All workflows have permissions declared"

0 commit comments

Comments
 (0)