From ef961ccb238f0977235ea5e3a77650e5157e47e4 Mon Sep 17 00:00:00 2001
From: Ralph Ursprung <ralph.ursprung@gmail.com>
Date: Sat, 1 Mar 2025 18:26:09 +0100
Subject: [PATCH] CI: use more generic version of `build-results`

this way only the `needs` list needs to be adapted and the step is fully
generic. i wasn't aware of this trick when i first wrote
`build-results`.
---
 .github/workflows/CI.yml | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/.github/workflows/CI.yml b/.github/workflows/CI.yml
index fbcb09a..5042a0f 100644
--- a/.github/workflows/CI.yml
+++ b/.github/workflows/CI.yml
@@ -88,11 +88,12 @@ jobs:
     name: Final Results
     if: ${{ always() }}
     runs-on: ubuntu-latest
-    needs: [lib, stm32f4-event-printer]
+    needs:
+      - lib
+      - stm32f4-event-printer
     steps:
-      - name: check for failed builds of the library
-        if: ${{ needs.lib.result != 'success' }}
-        run: exit 1
-      - name: check for failed builds of the example
-        if: ${{ needs.stm32f4-event-printer.result != 'success' }}
-        run: exit 1
+      - name: "check for failed builds"
+        run: |
+          cat <<EOF | jq -e 'unique | all(. == "success")'
+          ${{ toJson(needs.*.result) }}
+          EOF