-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Scorecard returns a non-zero exit code if any check has a runtime error #2133
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2133 +/- ##
==========================================
- Coverage 42.46% 42.42% -0.04%
==========================================
Files 94 94
Lines 7840 7846 +6
==========================================
Hits 3329 3329
- Misses 4253 4259 +6
Partials 258 258 |
Integration tests success for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with comment. Thanks for picking this up @spencerschrock!
Integration tests success for |
Integration tests success for |
Integration tests success for |
What kind of change does this PR introduce?
Scorecard now returns a non-zero exit code if any checks return a runtime error.
What is the current behavior?
Scorecard returns an exit code of 0 if most checks have runtime errors
What is the new behavior (if this is a feature change)?**
Scorecard now returns an exit code of 1 in the same scenarios
Which issue(s) this PR fixes
Fixes #2124
Special notes for your reviewer
Had to modify a few existing checks to conform to the new semantics.
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)