[TT-15111] Added visor code review - #408
Merged
Merged
probelabs / Visor: performance
succeeded
Sep 23, 2025 in 4m 4s
✅ Check Passed (Warnings Found)
performance check passed. Found 1 warning, but fail_if condition was not met.
Details
📊 Summary
- Total Issues: 2
- Warning Issues: 1
🐛 Issues by Category
⚡ Performance (2)
⚠️ .github/workflows/visor.yaml:8 - The workflow is configured to trigger on every issue comment (issue_comment: types: [created]). In an active repository, this can lead to excessive CI/CD resource consumption and create queues that delay other critical jobs.- ℹ️ .github/workflows/visor.yaml:22 - The workflow uses
probelabs/visor@main, which pulls the latest commit from themainbranch of the action's repository. This can introduce instability and unpredictable performance, as a new commit in the upstream action could introduce a performance regression or breaking change without warning.
Generated by Visor - AI-powered code review
Annotations
Check warning on line 10 in .github/workflows/visor.yaml
probelabs / Visor: performance
performance Issue
The workflow is configured to trigger on every issue comment (`issue_comment: types: [created]`). In an active repository, this can lead to excessive CI/CD resource consumption and create queues that delay other critical jobs.
Raw output
To conserve CI resources and avoid unnecessary runs, consider making the trigger more specific. If the action is intended to be invoked by a specific command within a comment, add a condition to the job to check for that command. For example, `if: startsWith(github.event.comment.body, '/visor')`.
Check notice on line 22 in .github/workflows/visor.yaml
probelabs / Visor: performance
performance Issue
The workflow uses `probelabs/visor@main`, which pulls the latest commit from the `main` branch of the action's repository. This can introduce instability and unpredictable performance, as a new commit in the upstream action could introduce a performance regression or breaking change without warning.
Raw output
For predictable performance and stability, it is recommended to pin the action to a specific version, such as a release tag (e.g., `@v1`) or a full commit SHA. This ensures that the workflow's execution remains consistent and is not affected by upstream changes unless explicitly updated.
Loading