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
{{ message }}
This repository has been archived by the owner on Oct 4, 2023. It is now read-only.
We'd love to integrate ataru into our CI process but we're kind of blocked from doing this because of two reasons:
1.) ataru does not set any exit status depending on what the check actually resulted in.
Meaning that this
echo $?
0
will always be the same. Which makes it not suitable for CI integration since there's no automated way of knowing when the checks failed.
2.) When something goes wrong, e.g. a syntax error in the source code ataru still prints on STDOUT. Not on STDERR. So there is no way of telling the difference between output that one can ignore and legitimate failures.
Am I missing something here or is [1] and [2] something we just have to live with?
We'd love to integrate ataru into our CI process but we're kind of blocked from doing this because of two reasons:
1.) ataru does not set any exit status depending on what the check actually resulted in.
Meaning that this
will always be the same. Which makes it not suitable for CI integration since there's no automated way of knowing when the checks failed.
2.) When something goes wrong, e.g. a syntax error in the source code ataru still prints on STDOUT. Not on STDERR. So there is no way of telling the difference between output that one can ignore and legitimate failures.
Am I missing something here or is [1] and [2] something we just have to live with?
P.S.: Discussion started initally here: troessner/reek#540
The text was updated successfully, but these errors were encountered: