Open taufik-rama opened 2 years ago
For the third checklist, I'll try to see how it could be done on the source code
Seems more complicated than I imagine :sweat_smile: , I don't usually use current build system
Other approach that I thought might be possible is to add an input that points to the raw $ cargo clippy
output file instead, and we could just read that file instead of doing the exec
of cargo
inside the script
Do the checklist before filing an issue:
actions-rs
Actions? If you think it's a problem related to Github Actions in general, use GitHub Community forum instead: https://github.communityMotivation
Basically what the title said, I think it's nice to add support so that the raw output of
cargo clippy
is stored in a fileWorkflow example
Additional context
Currently I'm trying to integrate some rust projects with SonarQube action. It needs the clippy output to be parsed & sent into the server
Currently I'm only able to do that by basically re-running the
cargo clippy
command & storing the outputIt would be nice if this action could store the raw output somewhere. For the implementation I could think that a simple
tee
command could do the trick, like:Would basically produce the same output as usual into stdout & also into a file
clippy.json