Add pwsh as pixi shells to the tests and documentation
#79
Conversation
|
Or we just don't mention |
|
Lets do that @pavelzw, you made my day a little better with that comment. The jobs that still fail aren't an issue for this pr right? |
the |
| ```yml | ||
| - run: | # everything here will be run inside of the pixi environment | ||
| python --version | Select-String "3.11" | ||
| shell: pixi run pwsh -Command {0} # pwsh works on all platforms |
There was a problem hiding this comment.
I'm wondering why this even works 🤔 shouldn't it be -File? The thing in {0} will be replaced by a path to the script at runtime...
There was a problem hiding this comment.
I started with -File but changed to -Command because that is what github uses: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell
There was a problem hiding this comment.
GitHub appends the extension .ps1 to your script name.
interesting... we unfortunately don't have the power to do this :(
There was a problem hiding this comment.
let's also change the bash shell to bash -e while we're at it
There was a problem hiding this comment.
I also find it super weird that there is different bash behavior when specifying bash or not specifying anything on unix...
There was a problem hiding this comment.
yeah no clue this whole shell thing isn't the most ergonomic feature.
Co-authored-by: Pavel Zwerschke <[email protected]>
pavelzw
changed the title
pwsh and cmd as pixi shells to the testpwsh as pixi shells to the test
pavelzw
changed the title
pwsh as pixi shells to the testpwsh as pixi shells to the tests and documentation
Co-authored-by: Pavel Zwerschke <[email protected]>
closes #78