Add stable CI result check for branch protection - #2076
Merged
vladimir-pecanac-main merged 1 commit intoAug 3, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add stable CI result check for branch protection
Adds a final
CI resultjob to.github/workflows/pr-build.ymlthat always runs (if: always()) afterdetect-changesandbuild-and-test, and only fails if one of those actually failed or was cancelled. This gives the workflow one job name that stays the same on every PR, unlikebuild-and-test, whose displayed name includes the matrix folder and therefore changes per PR. A required status check needs a name that doesn't move around, so this is what should be set as required in branch protection going forward. A PR that touches no buildable folders (empty matrix) still passes, since a skipped job isn't treated as a failure.