ci: add stable ci-success status gate job - #71
Closed
rahilsh wants to merge 1 commit into
Closed
Conversation
The branch ruleset required a status check named 'Java CI with Maven' (the workflow name), but Actions reports checks per job as 'build (21)'. That context was never produced, so PRs got stuck forever on 'Expected — Waiting for status to be reported'. Add an aggregation job 'ci-success' that depends on 'build' and exposes a single, matrix-independent required check. The ruleset now requires 'ci-success' instead.
Owner
Author
|
Superseded — pushing the ci-success gate directly onto the PR branch (#65) instead. |
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.
Problem
Every PR was stuck on
Java CI with Maven — Expected — Waiting for status to be reported.The branch ruleset required a status check context named
Java CI with Maven(the workflow name), but GitHub Actions reports checks per job, i.e.build (21)(jobbuild+ matrix21). The workflow name is never emitted as a status context, so the required check never arrived and merging was blocked indefinitely.Fix
ci-successthatneeds: buildand reports a single, matrix-independent status check.ci-successinstead ofJava CI with Maven.Follow-up
Existing open PRs need to be rebased onto
mainto pick up theci-successjob (e.g. comment@dependabot rebaseon dependabot PRs).