🤖 fix: use process substitution to avoid quoting issues

eval "$(...)" had nested quote conflicts with commands containing
double quotes like --format="%(refname:short)".

Use process substitution instead: bash <(echo BASE64 | base64 -d)
This creates a file descriptor containing the decoded script, so:
- Bash reads script from file descriptor (not stdin or quoted arg)
- No quoting conflicts because script content isn't in quotes
- Script can still redirect stdin freely (exec </dev/null works)

Author: ibetitsmike

src/node/utils/main/bashPath.ts

@@ -398,12 +398,13 @@ export function getSpawnConfig(runtime: BashRuntime, script: string, cwd?: strin
         // 2. The decode happens inside bash, so PowerShell never sees the script
         // 3. Single quotes in PowerShell pass the string literally to WSL
         //
-        // IMPORTANT: Use eval "$(echo ... | base64 -d)" instead of "echo ... | base64 -d | bash"
-        // The latter pipes to bash's stdin, which breaks if the script contains "exec </dev/null"
-        // (that redirects stdin to /dev/null, cutting off the script mid-read).
-        // Using eval with command substitution captures the entire decoded script first.
+        // Use process substitution: bash <(echo BASE64 | base64 -d)
+        // This creates a file descriptor containing the decoded script, so:
+        // - Bash reads the script from the file descriptor (not stdin)
+        // - The script can redirect stdin however it wants (e.g., exec </dev/null)
+        // - No quoting issues because the script content is never in a quoted string
         const wslArgs = runtime.distro ? `-d ${runtime.distro}` : "";
-        const psCommand = `wsl ${wslArgs} bash -c 'eval "$(echo ${base64Script} | base64 -d)"'`.trim();
+        const psCommand = `wsl ${wslArgs} bash -c 'bash <(echo ${base64Script} | base64 -d)'`.trim();
 
         return {
           command: psPath,