[TT-16977] fix: trigger release workflow on PR labeled event #975
+1
−0
probelabs / Visor: architecture
succeeded
Apr 17, 2026 in 24s
✅ Check Passed (Warnings Found)
architecture check passed. Found 1 warning, but fail_if condition was not met.
Details
📊 Summary
- Total Issues: 1
- Warning Issues: 1
🔍 Failure Condition Results
Passed Conditions
- global_fail_if: Condition passed
Issues by Category
Architecture (1)
⚠️ .github/workflows/release.yml:19 - Thepull_requesttrigger is configured to run on thelabeledevent, which will fire every time any label is added to a pull request. The pull request description states the intent is to react specifically to thedeps-reviewedlabel. This broad trigger could lead to numerous unnecessary workflow runs, consuming resources and cluttering the Actions tab.
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check warning on line 19 in .github/workflows/release.yml
probelabs / Visor: architecture
architecture Issue
The `pull_request` trigger is configured to run on the `labeled` event, which will fire every time any label is added to a pull request. The pull request description states the intent is to react specifically to the `deps-reviewed` label. This broad trigger could lead to numerous unnecessary workflow runs, consuming resources and cluttering the Actions tab.
Raw output
Add a condition to the relevant job(s) within this workflow to ensure they only execute for the intended `deps-reviewed` label. A condition like `if: contains(github.event.pull_request.labels.*.name, 'deps-reviewed')` would ensure the job runs only when this specific label is present, which covers both initial PR creation and the `labeled` event.
Loading