Closed Methuselah96 closed 1 year ago
Hi @Methuselah96 , thanks!
I appreciate you using/testing and submitting PRs for this actions since I personally do not use it so I can't really see what is missing.
Changes look good, I'll merge.
Glad to help, you've already done the hard part in creating dotnet-affected. ❤️
In the status quo, if the dotnet-affected command exits with a failing status code it will be marked as successfully, whether the failing status code is expected (i.e., 166) or a true error (i.e., something other than 166).
This PR resolves the issue by calling
setFailed
if the exit code indicates a true failure.