Repository navigation
ci: add a Pre Merge job that gates on every pre-merge job - #86
Merged
Merged
Conversation
A ruleset can only require a check. GitHub Actions reports one check per job, never one per workflow. A required "Pre Merge" check stayed pending forever because no check carried that name. The new job needs every pre-merge job. It fails when one of them failed or was cancelled. Every repository names it "Pre Merge", so a single ruleset can require it everywhere. The job runs with always(). Without it, a failed job would skip this one, and a skipped required check counts as passed.
anthony-treuillier-scality
approved these changes
Nov 13, 2026
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
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.
A ruleset can only require a check. GitHub Actions reports one check per job, never one per workflow. A required "Pre Merge" check stayed pending forever because no check carried that name.
The new job needs every pre-merge job. It fails when one of them failed or was cancelled. Every repository names it "Pre Merge", so a single ruleset can require it everywhere.
The job runs with always(). Without it, a failed job would skip this one, and a skipped required check counts as passed.