Skip to content

fix: prevent shell interpretation of special chars in commit messages#3

Merged
christiangda merged 2 commits intomainfrom
fix/workflow-commit-message-escaping
Feb 14, 2026
Merged

fix: prevent shell interpretation of special chars in commit messages#3
christiangda merged 2 commits intomainfrom
fix/workflow-commit-message-escaping

Conversation

@christiangda
Copy link
Contributor

Summary

  • Moves github.event.head_commit.message and github.event.head_commit.author.name into env vars in the main workflow's Summary Information step
  • Prevents bash from interpreting special characters (like <os> as a redirect) when commit messages contain angle brackets or other shell metacharacters

Root cause

GitHub Actions expands ${{ }} expressions before passing the script to bash. When a commit message contains machineid-<os>-<arch>, the <os> is interpreted as an input redirect, causing No such file or directory.

Test plan

  • Merge and verify the main workflow passes on the next push to main

🤖 Generated with Claude Code

christiangda and others added 2 commits February 14, 2026 19:19
GitHub Actions expands ${{ github.event.head_commit.message }} inline
before bash executes, so angle brackets like <os> in commit messages
are interpreted as shell redirects. Move the commit message and author
into env vars so bash handles them as properly quoted strings.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@christiangda christiangda self-assigned this Feb 14, 2026
@christiangda christiangda merged commit 70c4579 into main Feb 14, 2026
5 checks passed
@christiangda christiangda deleted the fix/workflow-commit-message-escaping branch February 14, 2026 18:31
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.

1 participant

Comments