Skip to content

Conversation

@vivekr-splunk
Copy link
Collaborator

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

Description

Related Issues

  • Related to #

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)
  • Performance improvement
  • Test improvement
  • CI/CD improvement
  • Chore (dependency updates, etc.)

Changes Made

Testing Performed

  • Unit tests pass (make test)
  • Linting passes (make lint)
  • Integration tests pass (if applicable)
  • E2E tests pass (if applicable)
  • Manual testing performed

Test Environment

  • Kubernetes Version:
  • Cloud Provider:
  • Deployment Method:

Test Steps

Documentation

  • Updated inline code comments
  • Updated README.md (if adding features)
  • Updated API documentation
  • Updated deployment guides
  • Updated CHANGELOG.md
  • No documentation needed

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published
  • I have updated the Helm chart version (if applicable)
  • I have updated CRD schemas (if applicable)

Breaking Changes

Impact:

Migration Path:

Screenshots/Recordings

Additional Notes

Reviewer Notes

Please pay special attention to:


Commit Message Convention: This PR follows Conventional Commits

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>
@coveralls
Copy link

Pull Request Test Coverage Report for Build 19477525204

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 36.822%

Totals Coverage Status
Change from base Build 19476510204: 0.0%
Covered Lines: 2336
Relevant Lines: 6344

💛 - Coveralls

@vivekr-splunk vivekr-splunk merged commit 13421f1 into main Nov 18, 2025
8 checks passed
@vivekr-splunk vivekr-splunk deleted the fix-yaml-line-continuation branch November 18, 2025 19:00
Copilot AI review requested due to automatic review settings November 18, 2025 19:00
Copilot finished reviewing on behalf of vivekr-splunk November 18, 2025 19:01
Copy link

Copilot AI left a 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 printf command 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.

Comment on lines +104 to 105
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
Copy link

Copilot AI Nov 18, 2025

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

Suggested change
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

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants