Skip to content

fix: Use working PowerShell custom shell invocation - #305

Merged
pavelzw merged 2 commits into
mainfrom
fix-pwsh-custom-shell
Nov 1, 2026
Merged

pavelzw merged 2 commits into
mainfrom
fix-pwsh-custom-shell

Conversation

@pavelzw

@pavelzw pavelzw commented Nov 1, 2026 •

Copy link
Copy Markdown
Collaborator

shell: pixi run pwsh -Command {0} never actually executed the script. GitHub Actions only appends .ps1 to the temporary script file if the shell command starts with pwsh. With pixi run pwsh ... the file has no extension, so pwsh -Command <file> tries to start it as a native program. execve fails with ENOEXEC and .NET falls back to shell-execute (xdg-open on Linux):

pixi run pwsh -File {0} (suggested in #78) works on Linux/macOS but fails on Windows because of the missing .ps1 extension.

Investigation and variant matrix in #304. pixi run pwsh -NoProfile -Command "Invoke-Expression (Get-Content -Raw '{0}')" works on all platforms.

Changes:

  • README: recommend the working invocation
  • Tests: use the working invocation, drop the ubuntu-arm skip, assert the script actually ran (marker file) and that a failing script fails the step

closes #78, closes #198, closes #304

If updating documentation:

@pavelzw
pavelzw enabled auto-merge (squash) November 1, 2026 17:03
@pavelzw
pavelzw disabled auto-merge November 1, 2026 17:03
@pavelzw
pavelzw merged commit 7c6c31c into main Nov 1, 2026
206 checks passed
@pavelzw pavelzw added the documentation Improvements or additions to documentation label Nov 1, 2026
@pavelzw
pavelzw deleted the fix-pwsh-custom-shell branch November 1, 2026 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Investigate why ubuntu-24.04-arm with pixi-shell pwsh behaves weirdly Custom shell wrapper doesn't work with powershell

1 participant