Improve CLI Error Messages#16
Conversation
The CLI's error messages for failed `dotnet` commands were too generic. This change makes them more specific by including the command that failed and its exit code. - Updated `ExecuteTestAsync` to provide specific error messages for `dotnet restore`, `clean`, `build`, and `run`. - Included the exit code in the error message for better debugging.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
This change improves the error messages in the CLI for failed
dotnetcommands. Instead of a generic "failed with exit code" message, the new messages specify which command failed (e.g.,dotnet restore,dotnet build) and include the exit code for easier debugging.PR created automatically by Jules for task 4414132777856426699 started by @sator-imaging