redirect error messages to STDERR#31
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #31 +/- ##
==========================================
- Coverage 47.92% 47.48% -0.44%
==========================================
Files 7 7
Lines 217 219 +2
==========================================
Hits 104 104
- Misses 113 115 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
@giovanni-guidini this is fine, but can we have a run showing what it would actually look like on CI? I'm pretty sure stderr also logs on GHA, but I just want to make sure |
thomasrockhu-codecov
left a comment
There was a problem hiding this comment.
Just do a run that shows that stderror actually does print out to the GHA console
According to Shell Style Guide, all error messages should go to stderr (see [here](https://google.github.io/styleguide/shellguide.html#stdout-vs-stderr))
d4899ff to
8b9bf39
Compare
https://github.com/codecov/codecov-ats/actions/runs/7348125288/job/20005671013 |
According to Shell Style Guide,
all error messages should go to stderr (see here)