You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This simplifies life for the contributor because they don't have to dig through logs to find what they broke and why.
This simplifies life for any mentors because this makes it easier to have a conversation about whats going wrong.
For maintainers that don't want warnings, etc to break their build, this provides them an avenue to still keep abreast on what warnings are occurring.
Proposal
A cargo wrapper that will invoke the specified cargo command with --message-format=json that then takes the file/line information and creates a review calling out these sections of the file
Open Questions
What should it do for messages without file/line?
How does it identify the PR that started it?
How does it avoid spamming for the same issue?
The text was updated successfully, but these errors were encountered:
Original discussion: https://users.rust-lang.org/t/handling-warnings-in-a-ci/15669/12
This simplifies life for the contributor because they don't have to dig through logs to find what they broke and why.
This simplifies life for any mentors because this makes it easier to have a conversation about whats going wrong.
For maintainers that don't want warnings, etc to break their build, this provides them an avenue to still keep abreast on what warnings are occurring.
Proposal
A cargo wrapper that will invoke the specified cargo command with
--message-format=json
that then takes the file/line information and creates a review calling out these sections of the fileOpen Questions
The text was updated successfully, but these errors were encountered: