-
Notifications
You must be signed in to change notification settings - Fork 19
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
Command "dotnet tool update" fails if root directory contains several projects #482
Comments
This branch could be used for the repro |
@kkostenkov After version 1.11.13, workingDirectory parameter is executed on the begining of the action. Is your problem is solved? |
Thank you so much for the reply. Meanwhile I did the investigation on my own and it appears that the Yesterday I did another iteration to solve the matter and it appears that those changes help:
I personally have no idea why 1 & 2 are needed since I managed to make it work without using workingDirectory parameter in the end, but without those changes the workflow kept failing. So to answer your question directly: no. Simply moving the execution of workingDirectory parameter won't help to solve the issue. |
This issue is closed as it is not active. |
Command
dotnet tool update
is run as soon as Action starts and due to a very old bug in the tool it fails if the directory contains multiple projects.In my case this is a game changer because some Unity projects have
.sln
and.csproj
files in the root of the repo.Maybe the parsing and execution of workingDirectory parameter could be moved to the beginning of the action? Then maybe that parameter could be used as a workaround with the value of
./..
The text was updated successfully, but these errors were encountered: