sharang/compliance-scanner-agent
1
0
Fork 0
Code Issues 51 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

fix: stop storing code review findings in dashboard #22

Merged
sharang merged 1 commits from fix/remove-code-review-from-findings into main 2026-03-18 15:18:07 +00:00
Conversation 0 Commits 1 Files Changed 2 -17
sharang commented 2026-03-18 13:25:39 +00:00
Owner
Copy Link

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

## 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)
sharang added 1 commit 2026-03-18 13:25:39 +00:00
fix: stop storing code review findings in dashboard, use PR comments only
All checks were successful
CI / Check (pull_request) Successful in 10m59s
Details
CI / Detect Changes (pull_request) Has been skipped
Details
CI / Deploy Agent (pull_request) Has been skipped
Details
CI / Deploy Dashboard (pull_request) Has been skipped
Details
CI / Deploy Docs (pull_request) Has been skipped
Details
CI / Deploy MCP (pull_request) Has been skipped
Details
8af810cdd2 
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 main 2026-03-18 15:18:07 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
critical
enhancement
high
infrastructure
performance
security
v0.3.0
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
sharang
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sharang/compliance-scanner-agent#22
Delete Branch "fix/remove-code-review-from-findings"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?