Skip to content

Database governance built for humans and agents — controlling changes and access across every major database.

chore: exclude parallel issue/plan detail clones from CPD

Dannyac048330eeb5
diff --git a/.sonarcloud.properties b/.sonarcloud.properties
index a5242d542b..544ef67d42 100644
--- a/.sonarcloud.properties
+++ b/.sonarcloud.properties
@@ -76,8 +76,16 @@ sonar.issue.ignore.multicriteria.fp_role_sql.resourceKey=backend/plugin/db/*/rol
# backend/plugin/db/** and the per-engine parser completers are intentionally
# parallel per-engine implementations (one folder per database engine), so
# cross-engine similarity is by design, not copy-paste debt.
+# The issue-detail and plan-detail route modules are intentionally parallel
+# (the issue view is the legacy sibling of the plan-first flow); the file
+# pairs below are acknowledged clones of each other, so same-shaped edits to
+# both sides trip new-code CPD without introducing new debt.
sonar.cpd.exclusions=\
action/**/*_test.go,\
+ frontend/src/routes/project/issue-detail/components/IssueDetailTaskRolloutActionPanel.tsx,\
+ frontend/src/routes/project/plan-detail/components/PlanDetailTaskRolloutActionPanel.tsx,\
+ frontend/src/routes/project/issue-detail/hooks/useIssueDetailSpecValidation.ts,\
+ frontend/src/routes/project/plan-detail/hooks/usePlanDetailSpecValidation.ts,\
backend/**/*_test.go,\
backend/**/testdata/**,\
backend/**/test-data/**,\