fix(actions): replace heredoc with env var to fix YAML parsing error - #61
Merged
Conversation
The heredoc syntax (cat <<'EOF') in the composite action caused GitHub Actions to fail with 'could not find expected :' because the unindented EOF delimiter was interpreted as a YAML key by the action manifest parser. Replace with a COMMENT_BODY environment variable using YAML block scalar (|), which is properly parsed and avoids Markdown indentation issues. Signed-off-by: uwe-mayer <uwe.mayer01@sap.com>
There was a problem hiding this comment.
Pull request overview
This PR fixes a YAML parsing failure in the issue-triage composite action by removing a bash heredoc from the run: block and moving the welcome-comment text into a YAML block-scalar environment variable, which GitHub Actions’ manifest loader can parse reliably.
Changes:
- Replaced
cat <<'EOF' ... EOFheredoc usage with a multilineCOMMENT_BODYenv var (|block scalar). - Updated the
gh issue commentinvocation to use--body "$COMMENT_BODY".
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
abhijith-darshan
approved these changes
Jun 17, 2026
This was referenced Jun 18, 2026
IvoGoman
pushed a commit
to cloudoperators/greenhouse
that referenced
this pull request
Jun 23, 2026
…error The previous SHA (f87e1e6b) contained a heredoc syntax that caused the GitHub Actions manifest parser to fail with 'could not find expected :'. Update to c7ec5c47 which fixes the heredoc by using a YAML block scalar env variable instead. See: cloudoperators/common#61 Signed-off-by: uwe-mayer <uwe.mayer01@sap.com>
IvoGoman
pushed a commit
to cloudoperators/greenhouse
that referenced
this pull request
Jun 23, 2026
…error (#2085) The previous SHA (f87e1e6b) contained a heredoc syntax that caused the GitHub Actions manifest parser to fail with 'could not find expected :'. Update to c7ec5c47 which fixes the heredoc by using a YAML block scalar env variable instead. See: cloudoperators/common#61 Signed-off-by: uwe-mayer <uwe.mayer01@sap.com>
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
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.
Problem
The issue-triage workflow is failing across all repositories with:
Root Cause
The heredoc syntax (
cat <<'EOF') in the composite action'srun:block causes the GitHub Actions manifest parser to fail. The unindentedEOFdelimiter at column 1 is interpreted as a YAML key by the parser.Fix
Replace the heredoc with a
COMMENT_BODYenvironment variable using YAML block scalar (|). This is properly parsed by both the YAML parser and the GitHub Actions manifest loader, and avoids Markdown indentation issues in the rendered comment.