fix(ci): harden release job condition (avoid stuck 'blocked')
A bare `if: github.ref_type == 'tag'` on a needs-dependent job can
leave `release` stuck in "blocked" instead of skipped for
workflow_dispatch runs on Gitea. Use the explicit
${{ github.event_name == 'push' && github.ref_type == 'tag' }} form.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
@@ -55,7 +55,10 @@ jobs:
|
||||
# Requires a GITEA_TOKEN secret with repo write permissions.
|
||||
release:
|
||||
needs: build
|
||||
if: github.ref_type == 'tag'
|
||||
# Tag pushes only. Explicit ${{ }} + event gate: a bare
|
||||
# `if: github.ref_type == 'tag'` can leave the job stuck "blocked"
|
||||
# (instead of skipped) on Gitea for workflow_dispatch runs.
|
||||
if: ${{ github.event_name == 'push' && github.ref_type == 'tag' }}
|
||||
runs-on: windows-build
|
||||
|
||||
steps:
|
||||
|
||||
Reference in New Issue
Block a user