[11.x] Run Workflows on Windows 2022 and with bash instead of powershell #51958
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for submitting a PR! Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface. Pull requests that are abandoned in draft may be closed due to inactivity. |
Jubeki
changed the title
|
Hah that's great @Jubeki. Thanks! |
1 task
MrPunyapal
added a commit
to MrPunyapal/framework
that referenced
this pull request
Oct 11, 2024
… powershell (laravel#51958)" This reverts commit 94df3d6.
MrPunyapal
added a commit
to MrPunyapal/framework
that referenced
this pull request
Oct 11, 2024
…f powershell (laravel#51958)" This reverts commit 4de8a4c.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Replaces
windows-2019withwindows-2022next version will probably bewindows-2025.This also fixes a long standing issue, where the
^symbol was being escaped in the windows command line / powershell.Solution: explicitly use bash.