Skip to content

Commit

Permalink
Use alls-green to signal overall workflow state
Browse files Browse the repository at this point in the history
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 <[email protected]>
  • Loading branch information
sjoerdsimons committed Jun 19, 2023
1 parent 340cd7c commit 44118fe
Showing 1 changed file with 8 additions and 6 deletions.
14 changes: 8 additions & 6 deletions .github/workflows/ci.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 44118fe

Please sign in to comment.