fix: resolve Claude Code Action failure with non-ASCII branch names in PR comments #617
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.
Replace
$template literal with Bun.spawn() array format in git commands handling PR branch names to avoid Bun shell template bug with non-ASCII characters.Claude Code Action fails when the source branch name of a triggering PR contains "/{non-ASCII characters}". This is caused by a Bun template literal ($) bug (oven-sh/bun#15929), where variables are converted to "__bunstr_0" format when commands contain "/{non-ASCII characters}".
This issue causes the command:
to fail when {branchName} contains "/{non-ASCII characters}", as {fetchDepth} gets converted to "__bunstr_0".
While this change affects code consistency, we use Bun.spawn() because avoiding the bug while maintaining template literals proved difficult. The spawn() array format bypasses shell parsing and safely handles all non-ASCII characters including Japanese.
fix: #616