From 0c136fffb96b6caaae367e28efc3f2582654244f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zolt=C3=A1n=20Papp?= Date: Tue, 5 May 2026 15:10:23 +0200 Subject: [PATCH] [ci] Add sonar-project.properties to exclude the Wails React frontend MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sonar's default scanner picks up TypeScript / JSX from the frontend tree but applies rules that don't fit a UI codebase reviewed visually (component dead-code detection, hook-shape conventions, ...). Skip client/ui-wails/frontend from both analysis and coverage so neither the rules engine nor the coverage gate trips on UI changes. The Go side of the Wails UI (client/ui-wails/*.go, services/) is left in scope on purpose — same Go standards as the rest of the repo. --- sonar-project.properties | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 sonar-project.properties diff --git a/sonar-project.properties b/sonar-project.properties new file mode 100644 index 000000000..948557321 --- /dev/null +++ b/sonar-project.properties @@ -0,0 +1,11 @@ +sonar.projectKey=netbirdio_netbird +sonar.organization=netbirdio + +# Exclude the React frontend from analysis. The Go side of the Wails UI +# (client/ui-wails/*.go and services/) is intentionally kept in scope — +# it's regular Go code with the same standards as the rest of the repo. +sonar.exclusions=client/ui-wails/frontend/** + +# Mirror the same paths under coverage so missing coverage on UI code +# doesn't drag the overall coverage metric down. +sonar.coverage.exclusions=client/ui-wails/frontend/** \ No newline at end of file