Replaces unsupported failure()/cancelled() with explicit needs.<job>.result checks in publish gates #7

Merged

Sluijsens merged 2 commits from feature/gitea-workflow-optimizations into master 2026-07-31 21:20:02 +02:00

Conversation 0 Commits 2 Files Changed 1

+35 -8

2 Commits

Author	SHA1	Message	Date
SluijsensandClaude Sonnet 5	de06578444	Logs workflow_dispatch input values and skips publish-test on a manual run without deploy_test checked ... Gitea's UI has no reliable way to see a past run's dispatch input values, so the config job now echoes them into the log. publish-test previously always built and uploaded the test artifact regardless of the deploy_test/deploy_production selection, wasting a build on manual runs that were never going to deploy to test; it now mirrors publish-production by skipping when workflow_dispatch didn't check deploy_test. Push and pull_request runs are unaffected. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VhySVFARKAP89WqQ3Kff8M	2026-07-31 20:17:55 +02:00
SluijsensandClaude Sonnet 5	12b1df6ede	Replaces unsupported failure()/cancelled() with explicit needs.<job>.result checks in publish gates ... Gitea Actions only implements always() from GitHub Actions' status-check functions; success(), failure(), and cancelled() aren't supported. publish-test/publish-production relied on !failure() && !cancelled() to let a run through when an unaffected gate job was skipped by the path filter while still blocking on an actual failure — rewritten to check needs.<job>.result explicitly instead, which Gitea does support. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VhySVFARKAP89WqQ3Kff8M	2026-07-31 16:53:46 +02:00