From 44118fe78d59d76dfa856786dc60e3a0f75f32f5 Mon Sep 17 00:00:00 2001 From: Sjoerd Simons Date: Sun, 18 Jun 2023 16:40:38 +0200 Subject: [PATCH] Use alls-green to signal overall workflow state Setting up each required job by hand is annoying; So similar to what we did with bors have one job that concludes the overall status. As opposed to bors this *always* runs rather then only when everything is good, as that allows github to trigger properly. Signed-off-by: Sjoerd Simons --- .github/workflows/ci.yaml | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index 756c84c5..221e1ad8 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -171,17 +171,19 @@ jobs: ${{matrix.test.variables}} ${{matrix.test.case}}/test.yaml - # Job to key the bors success status against - bors: - name: bors - if: success() + # Job to key success status against + allgreen: + name: allgreen + if: always() needs: - unit-tests - recipe-tests runs-on: ubuntu-latest steps: - - name: Mark the job as a success - run: exit 0 + - name: Decide whether the needed jobs succeeded or failed + uses: re-actors/alls-green@release/v1 + with: + jobs: ${{ toJSON(needs) }} publish-github: name: Publish to GHCR