-
Notifications
You must be signed in to change notification settings - Fork 0
fix: remove line continuation backslashes in printf command #54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The backslash line continuation characters in the printf command were causing YAML parsing issues. GitHub Actions YAML parser has trouble with backslash continuations in multi-line commands. Changes: - Combine printf command into single line (no backslashes) - Functionally identical, just formatted differently - Line 104 is now a complete single-line command This is a formatting-only change with no logic changes. Fixes: YAML syntax error on line 104 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Pull Request Test Coverage Report for Build 19477525204Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes a YAML formatting issue in the GitHub Actions workflow by removing line continuation backslashes from a printf command that were causing parsing problems.
- Consolidated multi-line
printfcommand into a single line to avoid YAML parser issues with backslash continuations - No functional changes to the workflow logic
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| printf "Release %s\n\nAutomated release created from GitHub Actions workflow.\n\nCommit: %s\nCreated: %s\nCreated by: %s\nPre-release: %s\n\nRelease Notes:\n%s\n\nGenerated with Claude Code\n" "$TAG" "$COMMIT_SHORT" "$TIMESTAMP" "$ACTOR" "$PRERELEASE" "$COMMIT_MSG" > /tmp/tag_message.txt | ||
Copilot
AI
Nov 18, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The printf command is very long (over 200 characters) and difficult to read on a single line. Consider using a heredoc (<<EOF) or multi-line YAML literal string (|) to improve readability while avoiding backslash continuation issues. For example:\n\nyaml\ncat > /tmp/tag_message.txt <<EOF\nRelease $TAG\n\nAutomated release created from GitHub Actions workflow.\n\nCommit: $COMMIT_SHORT\nCreated: $TIMESTAMP\nCreated by: $ACTOR\nPre-release: $PRERELEASE\n\nRelease Notes:\n$COMMIT_MSG\n\nGenerated with Claude Code\nEOF\n
| printf "Release %s\n\nAutomated release created from GitHub Actions workflow.\n\nCommit: %s\nCreated: %s\nCreated by: %s\nPre-release: %s\n\nRelease Notes:\n%s\n\nGenerated with Claude Code\n" "$TAG" "$COMMIT_SHORT" "$TIMESTAMP" "$ACTOR" "$PRERELEASE" "$COMMIT_MSG" > /tmp/tag_message.txt | |
| cat > /tmp/tag_message.txt <<EOF | |
| Release $TAG | |
| Automated release created from GitHub Actions workflow. | |
| Commit: $COMMIT_SHORT | |
| Created: $TIMESTAMP | |
| Created by: $ACTOR | |
| Pre-release: $PRERELEASE | |
| Release Notes: | |
| $COMMIT_MSG | |
| Generated with Claude Code | |
| EOF |
The backslash line continuation characters in the printf command were causing YAML parsing issues. GitHub Actions YAML parser has trouble with backslash continuations in multi-line commands.
Changes:
This is a formatting-only change with no logic changes.
Fixes: YAML syntax error on line 104
🤖 Generated with Claude Code
Description
Related Issues
Type of Change
Changes Made
Testing Performed
make test)make lint)Test Environment
Test Steps
Documentation
Checklist
Breaking Changes
Impact:
Migration Path:
Screenshots/Recordings
Additional Notes
Reviewer Notes
Please pay special attention to:
Commit Message Convention: This PR follows Conventional Commits