👷 Mark final check as failed and not skipped #4371
Merged
+14
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our current final job "All checks passed" as considered as OK when skipped. We defined that job to easily capture the fact that all our required jobs passed. Unfortunately GitHub considers that skipped or success are OK statuses for required jobs.
As a consequence, we adopted another pattern made of two jobs. One that should aggregate the status of the required ones into a: success or skipped. And one translating the skip into a failed.
Category:
Potential impacts: