fix(review): remove expression syntax from a run-block comment - #24
Merged
Conversation
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.
Hotfix. Every PR in the org is blocked behind
.github/workflows/claude-pr-review.yml — Please close and reopen the PR to trigger this workflow.A shell comment in the context step spelled out the Actions expression delimiters to explain that PR title and body deliberately avoid them. Actions parses those delimiters inside a
run:block's string value, comments included, and an empty pair is a syntax error — so the workflow was unparseable, every run started with zero jobs, and the required check never reported.The identical-looking comment that predates this (line 183, under
env:) is harmless because it is a YAML comment, stripped by the YAML parser before Actions sees the file. That difference is why this survived review and local YAML validation.actionlintcatches it; the previous suite could not, becauseyaml.safe_loadaccepts the file andtests/context-step-test.shexplicitly exempted comments from its delimiter check. Test hardening follows separately — this change is only the reword, to unblock the org.