Repository navigation
An unquoted colon broke every workflow run since the launch commit - #47
Merged
Merged
Conversation
The configure-pages step was named 'enable Pages if it is not already (build_type: workflow)' — a colon-space inside a plain YAML scalar, which fails the whole file's parse. GitHub then records an instant zero-job failure run on EVERY push while a broken workflow file is in the tree, which is why four 'demo to pages' runs failed in zero seconds including three on pushes that predate the push trigger. The name loses its parenthetical; all three workflow files now yaml-parse locally, which should have been checked before the launch commit and is exactly the class of error 'assert on every string edit' exists for. This merge touches the workflow file, so its own push starts the first real deploy. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A4dBsLoHroiPssTXX1L1E6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
One step name in
demo-pages.yml. It wasenable Pages if it is not already (build_type: workflow)— a colon-space inside a plain YAML scalar, which fails the parse of the whole file. GitHub records an instant zero-job failure run on every push while a broken workflow file is in the tree, which is why fourdemo to pagesruns failed in zero seconds, including three on pushes that predate the push trigger. The parenthetical is gone; all three workflow files now yaml-parse locally.This merge touches the workflow file, so its own push starts the first real deploy — the thing PR #46 was for.
Does it add a spatial prior?
No. One YAML scalar.
Numbers
python3 -c "yaml.safe_load(...)": demo-pages.yml BROKEN → OK; demo-aws.yml OK; ci.yml OK. The class of error is the repo's own "assert on every string edit" lesson, applied to CI config: a workflow edit should be yaml-parsed locally before pushing, and wasn't.Checklist
src/, not incanalisation.html— neither touchednode build.jsand committed the regeneratedcanalisation.html— n/anode test/smoke.mjspasses — unaffected🤖 Generated with Claude Code
https://claude.ai/code/session_01A4dBsLoHroiPssTXX1L1E6
Generated by Claude Code