| Repo | Needs review | Merge pending | Auto-merged | Total tracked |
|---|---|---|---|---|
| qualogy-solutions/jira-ticket-analysis | 0 | 0 | 2 | 6 |
| qualogy-solutions/qualogy-scraper | 0 | 0 | 0 | 2 |
| qualogy-solutions/qualogy-websites | 1 | 0 | 4 | 10 |
| qualogy-solutions/sales-insights-dashboard | 1 | 0 | 0 | 1 |
🔺 Needs your review — across all repos (2)
Large sprawling PR (146 files, ~2400 lines changed) touching almost every marketing/content page and shared component (hero sections, cases pages, homepage, footer, nav) for mobile UI fixes. No backend, auth, payments, or schema changes are involved, but the sheer breadth means a CSS/layout regression or a broken import (e.g. PullQuote component usage across dozens of files) could visually break many public-facing pages simultaneously.
- <item>146 files changed across nearly all onze-cases pages, homepage, diensten, footer, nav, and shared UI components — very wide surface area</item> <item>Repeated structural changes (hero markup, spacing, new PullQuote component, image markup) applied consistently across many pages, increasing risk of a systemic layout bug affecting the whole site</item> <item>Includes a new client-side search/filter behavior (FilterWrapper using useSearchParams) which changes interactive behavior, not just styling</item> <item>Purely front-end/UI/content changes — no auth, database, payments, infra, or security-sensitive code touched, which caps this below 'high'</item> <item>Given the scale and cross-cutting nature of the diff, visual regressions could be broad even if each individual change is low-risk, warranting careful review rather than auto-approval</item> </reasons>
Large mechanical mobile-responsiveness PR touching mostly Tailwind classes, hero section layout, and refactoring inline quote blocks into a shared PullQuote component. The diff is very large but repetitive/low-risk in nature (styling adjustments, spacing, hero restructuring). I spotted a couple of correctness concerns worth a second look, but nothing that clearly breaks functionality; flagging as warnings rather than blocking issues, with one moderate one around the mainImage duplicate-check heuristic potentially hiding legitimate images.
Replaces the "Dupliceren" (clone) feature with a manual duplicate-set linking mechanism, changing business logic and data flow for assignments (archiving/unlinking via is_active, superseded_by, alert_new_duplicate columns). Affects the Aanvragen list, detail pane, and pipeline view across the whole assignment workflow used by Sales, and reuses shared columns that also drive existing supersession/alert UI, so a bug could mis-archive or mis-link real aanvraag records.
- Removes an existing feature (duplicateAssignment) and replaces with new bulk mutation logic touching shared DB columns (is_active, superseded_by, archived_at) used elsewhere in the app
- Moderate-large diff (627+/329-) spanning 10 files including services, hooks, and multiple UI components
- Business logic change affecting core Aanvragen workflow (archiving, unlinking, duplicate detection) with direct writes to production data via Supabase
- Good test coverage included for new service functions, which reduces but doesn't eliminate risk
- No schema migration or auth changes, keeping it out of 'high' territory, but affects a widely-used feature across list, detail, and pipeline views
Solid, well-documented change that replaces the "Dupliceren" clone feature with a manual duplicate-set linking mechanism, reusing existing supersession columns. Logic looks consistent with tests covering the new service functions. A few edge cases worth flagging, none blocking.