GitHub Actions / GitHub Actions

GitHub Actions Runner Bash Script Path Word Splitting with Spaces in Directory Names

Fix GitHub Actions runner bash script handler failing when script path contains spaces due to unquoted path placeholder Includes evidence for GitHub Actions troubleshooting demand.

Source-backed Last updated May 13, 2026 1 source Needs local verification

Category: GitHub Actions
Error signature: Bash script handler doesn't quote script path — word splitting in directories with spaces
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 13, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for GitHub Actions, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Bash script handler doesn't quote script path — word splitting in directories with spaces is a GitHub Actions failure pattern reported for developers trying to fix github actions runner bash script handler failing when script path contains spaces due to unquoted path placeholder. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Open issue on actions/runner. Bash script handler template doesn't quote {0} placeholder, causing word splitting when script path contains spaces. Affects self-hosted runners on Windows/macOS with space-containing paths.

Common causes

GitHub Actions self-hosted runners fail silently when project paths contain spaces. The unquoted {0} placeholder in ScriptHandlerHelpers.cs causes word splitting, breaking CI/CD for teams with spaces in directory names.
Open issue on actions/runner. Bash script handler template doesn't quote {0} placeholder, causing word splitting when script path contains spaces. Affects self-hosted runners on Windows/macOS with space-containing paths.

Quick fixes

Confirm the exact error signature matches Bash script handler doesn't quote script path — word splitting in directories with spaces.
Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Bash script handler doesn't quote script path — word splitting in directories with spaces exactly before applying the quick fix.
Compare the failing environment with GitHub Actions versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Bash script handler doesn't quote script path — word splitting in directories with spaces mean in GitHub Actions?

Bash script handler doesn't quote script path — word splitting in directories with spaces indicates the workflow described by "GitHub Actions Runner Bash Script Path Word Splitting with Spaces in Directory Names" failed in a GitHub Actions context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Bash script handler doesn't quote script path — word splitting in directories with spaces?

Check whether this cause matches your environment: GitHub Actions self-hosted runners fail silently when project paths contain spaces. The unquoted {0} placeholder in ScriptHandlerHelpers.cs causes word splitting, breaking CI/CD for teams with spaces in directory names.

Is the Bash script handler doesn't quote script path — word splitting in directories with spaces guidance source-backed?

The "GitHub Actions Runner Bash Script Path Word Splitting with Spaces in Directory Names" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Bash script handler doesn't quote script path — word splitting in directories with spaces?

For "GitHub Actions Runner Bash Script Path Word Splitting with Spaces in Directory Names", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Bash script handler doesn't quote script path — word splitting in directories with spaces?

For "GitHub Actions Runner Bash Script Path Word Splitting with Spaces in Directory Names", collect the failing GitHub Actions command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.