fix: resolve all YAML template literal issues in merge-bot workflow #22
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.
Summary
This PR completely fixes all YAML syntax errors in the merge-bot workflow by replacing problematic template literals with array-based string construction.
Problem
After PR #21 was merged, the workflow still has multiple YAML parsing errors caused by template literals with backticks inside YAML string literals. GitHub Actions fails to parse the workflow file at multiple locations:
Error pattern:
Root Cause
YAML parser struggles with:
\``bash`script:blocksSolution
Replace all problematic template literals with array-based string construction:
Before (❌ Causes YAML errors):
After (✅ Clean and valid):
Changes Made
Validation
✅ Python YAML parser: Validates successfully
✅ Node.js syntax check: JavaScript is valid
✅ act (GitHub Actions local runner): Workflow parses correctly
All three validation methods pass!
Testing
After merge, test with PR #20:
/updateon PR docs: enhance module docstring (TEST PR for /update command) #20Related
/updatecommand on PR docs: enhance module docstring (TEST PR for /update command) #20🤖 Generated with Claude Code