Skip to content

[TT-16977] fix: trigger release workflow on PR labeled event #975

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
buger merged 1 commit into from
Apr 17, 2026
+1 −0

fix: trigger release workflow on PR labeled event

bf9fd9b
Select commit
Loading
Failed to load commit list.
Merged

[TT-16977] fix: trigger release workflow on PR labeled event #975

fix: trigger release workflow on PR labeled event
bf9fd9b
Select commit
Loading
Failed to load commit list.
probelabs / Visor: quality succeeded Apr 17, 2026 in 53s

✅ Check Passed (Warnings Found)

quality 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:20 - The pull_request trigger with type labeled will cause this workflow to run every time any label is added to a pull request. According to the pull request description, the intent is to trigger the workflow only for the deps-reviewed label. This broad trigger could lead to excessive and unnecessary workflow runs, consuming CI resources.

Powered by Visor from Probelabs

💡 TIP: You can chat with Visor using /visor ask <your question>

Annotations

Check warning on line 20 in .github/workflows/release.yml

See this annotation in the file changed.

@probelabs probelabs / Visor: quality

performance Issue 

The `pull_request` trigger with type `labeled` will cause this workflow to run every time any label is added to a pull request. According to the pull request description, the intent is to trigger the workflow only for the `deps-reviewed` label. This broad trigger could lead to excessive and unnecessary workflow runs, consuming CI resources.
Raw output 
To ensure the workflow only runs when a specific label is added, add a condition to the relevant job(s) in this workflow. For example: `if: github.event.action == 'labeled' && github.event.label.name == 'deps-reviewed'`.
View more details on probelabs