fix(ci): repair flake-sync commit message YAML#5
Merged
Conversation
The commit-message body in the Commit + push step sat at column 0, under-indented relative to its run: | block, so YAML ended the block early and parsed the body as mapping keys. The workflow has been invalid since it was added, failing validation on every trigger. Indent the body lines into the block (the literal scalar strips the block indent, so the message still renders at column 0) and replace the non-ASCII arrows with ->.
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
1 participant
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.
The flake-sync workflow has been failing validation on every trigger with "Invalid workflow file ... line 117". It has been invalid since it was first added.
Cause
In the Commit + push step, the git commit message body was written at column 0:
A YAML literal block (run: |) ends at the first line indented less than the block. The body lines at column 0 therefore terminated the block, and YAML tried to parse "Auto-generated..." and "- version:" as mapping keys, which fails.
Fix
Indent the message body lines into the block. The literal scalar strips the common block indentation, so the rendered commit message still starts at column 0 exactly as before. Also replaced the two non-ASCII arrow characters with ->.
Verification
All six workflow files parse cleanly after the change. Confirmed the rendered run block keeps the commit message body at column 0, so the produced commit is unchanged.