generated from actions/typescript-action
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is there any way to run tmate using the standard MSYS2 environment set by msys2/setup-msys2@v2? #86
Labels
enhancement
New feature or request
Comments
You could of course introduce support for a new input, say, if (process.platform === "win32") {
process.env.MSYS2_ROOT = core.getInput("msys2-root-directory") || "C:\\msys64"
} Then, in the call to the MSYS2 Bash, you would use that environment variable, something like this: spawn(`${process.env.MSYS2_ROOT}\\usr\\bin\\bash.exe", ["-lc", cmd], [...] @hradec do you feel up to the task? |
What about the WSL? :) |
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I running into a difficult situation where my action runs on windows using
msys2/setup-msys2@v2
, but tmate runs it's own mingw enviroment.I'm using
msys2/setup-msys2@v2
pip to install pywin32, but it's failing during the build. In tmate, when I runpip install pywin32
, it finds it and installs correctly.Is there any way to run tmate using
msys2/setup-msys2@v2
environment instead?The text was updated successfully, but these errors were encountered: