Fix tag-deploy condition to properly check individual job results
Some checks failed
Deploy / detect (push) Successful in 5s
Deploy / deploy-api (push) Failing after 29s
Deploy / tag-deploy (push) Has been cancelled
Deploy / deploy-frontend (push) Has been cancelled

Use explicit job result checks instead of needs.*.result wildcard which
does not work in Gitea Actions. Prevent tagging when any deploy job fails.
This commit is contained in:
DaX
2026-03-05 01:40:03 +01:00
parent 746f0925d0
commit 0741bd0d0e

View File

@@ -281,7 +281,12 @@ jobs:
tag-deploy: tag-deploy:
runs-on: ubuntu-latest runs-on: ubuntu-latest
needs: [detect, deploy-frontend, deploy-api] needs: [detect, deploy-frontend, deploy-api]
if: always() && !contains(needs.*.result, 'failure') && !contains(needs.*.result, 'cancelled') if: >-
always() &&
needs.detect.result == 'success' &&
(needs.deploy-frontend.result == 'success' || needs.deploy-frontend.result == 'skipped') &&
(needs.deploy-api.result == 'success' || needs.deploy-api.result == 'skipped') &&
!(needs.deploy-frontend.result == 'skipped' && needs.deploy-api.result == 'skipped')
steps: steps:
- name: Checkout - name: Checkout
uses: actions/checkout@v4 uses: actions/checkout@v4