[TT-16977] fix: trigger release workflow on PR labeled event #8088
+1
−0
probelabs / Visor: performance
succeeded
Apr 17, 2026 in 17s
✅ Check Passed (Warnings Found)
performance 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
Performance (1)
⚠️ .github/workflows/release.yml:19 - The workflow is configured to trigger on everylabeledevent for a pull request. This will cause the entire workflow to run each time any label is added or removed, leading to unnecessary consumption of CI/CD resources. The pull request description mentions this is for thedeps-reviewedlabel, but the current implementation triggers on all labels.
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: performance
performance Issue
The workflow is configured to trigger on every `labeled` event for a pull request. This will cause the entire workflow to run each time any label is added or removed, leading to unnecessary consumption of CI/CD resources. The pull request description mentions this is for the `deps-reviewed` label, but the current implementation triggers on all labels.
Raw output
To prevent unnecessary workflow runs, add a conditional check at the job level to ensure that jobs only run for the `labeled` event if the specific label is `deps-reviewed`. This will preserve the behavior for other event types like `opened` and `synchronize` while correctly scoping the `labeled` trigger.
Example of a job-level conditional:
```yaml
jobs:
some-job:
if: github.event.action != 'labeled' || github.event.label.name == 'deps-reviewed'
runs-on: ubuntu-latest
steps:
...
```
Loading