From fae257492a04f06bd51f96cb1f801cf2fb4a0a17 Mon Sep 17 00:00:00 2001
From: Rahil <rahilrshk@gmail.com>
Date: Mon, 10 Aug 2026 16:48:15 +0300
Subject: [PATCH] ci: add stable ci-success status gate job
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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.
---
 .github/workflows/maven.yml | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/.github/workflows/maven.yml b/.github/workflows/maven.yml
index 48c4f59..41cd6ee 100644
--- a/.github/workflows/maven.yml
+++ b/.github/workflows/maven.yml
@@ -26,3 +26,21 @@ jobs:
           cache: maven
       - name: Build and verify
         run: mvn -B verify
+
+  # Aggregation gate: exposes a single, stable status check ("ci-success") that
+  # is independent of the build matrix. Set this as the required status check in
+  # branch protection instead of the matrix-dependent "build (21)" context.
+  ci-success:
+    name: ci-success
+    if: always()
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Verify build job succeeded
+        run: |
+          if [ "${{ needs.build.result }}" != "success" ]; then
+            echo "build job did not succeed: ${{ needs.build.result }}"
+            exit 1
+          fi
+          echo "All required jobs succeeded."
+