Remove LLM code review stage from the scan pipeline — code review findings were being stored in the findings DB but lacked PR context, making them useless in the dashboard
Remove "Code Review" option from the findings type filter dropdown
Code review feedback continues to be posted as inline PR comments (GitHub, Gitea, GitLab) via the existing PR review webhook pipeline
Test plan
Trigger a scan and verify no code review findings are created in the DB
Check the findings page filter dropdown no longer shows "Code Review"
Open/update a PR and verify inline review comments still appear
## Summary
- Remove LLM code review stage from the scan pipeline — code review findings were being stored in the findings DB but lacked PR context, making them useless in the dashboard
- Remove "Code Review" option from the findings type filter dropdown
- Code review feedback continues to be posted as inline PR comments (GitHub, Gitea, GitLab) via the existing PR review webhook pipeline
## Test plan
- [ ] Trigger a scan and verify no code review findings are created in the DB
- [ ] Check the findings page filter dropdown no longer shows "Code Review"
- [ ] Open/update a PR and verify inline review comments still appear
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Code review findings are not actionable in the findings dashboard — they
lack PR context and clutter the list. The PR review pipeline already
posts inline comments directly on PRs (GitHub, Gitea, GitLab), which is
the appropriate place for code review feedback.
- Remove LLM code review stage from the scan pipeline (orchestrator)
- Remove "Code Review" option from the findings type filter dropdown
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
sharang
merged commit a9d039dad3 into main2026-03-18 15:18:07 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Test plan
🤖 Generated with Claude Code