Closed othmane-kinane-nw closed 1 year ago
The fix is to replace join
by resolve
. I can create a PR if you agree:
hi @othmane-kinane-nw, thank you for the report and the proposed solution. We will take a look at it
hi @othmane-kinane-nw, would you be willing to provide the PR for this issue? :)
hi @othmane-kinane-nw, just to double check are you willing to provide the PR? If you don't have time I can provide the PR :)
Any news on this? I still get error when only global-json-file:
is specified.
hi @othmane-kinane-nw, just to double check are you willing to provide the PR? If you don't have time I can provide the PR :)
Sorry for the late reply. I will try to create the PR this week. The fix is a one liner but I have to go through the contributor guidelines and eventually add tests.
hi @othmane-kinane-nw, just to double check are you willing to provide the PR? If you don't have time I can provide the PR :)
@panticmilos I just created the PR: https://github.com/actions/setup-dotnet/pull/396
@othmane-kinane-nw, thank you for the update! :) I have reviewed it, I will require a few more reviews but generally, all seems to be fine to me.
Description:
setup-dotnet
does not handle correctly absolute paths as value for theglobal-json-file
input. The action always join the provided value with the github workspace (aka respository's root) instead of using it as-is if it's an absolute path.Task version: v3
Platform:
Runner type:
Repro steps:
Pass an absolute path as value for the
global-json-file
input that points to aglobal.json
file in a subfolder. Do not use thedotnet-version
input. ex:Expected behavior: The action finishes with success and the provided
global.json
is used.Actual behavior: The action fails with this error: