Skip to content

ci(sonar): SonarCloud scan workflow + project config#259

Open
hyperpolymath wants to merge 1 commit into
mainfrom
ci/sonarcloud
Open

ci(sonar): SonarCloud scan workflow + project config#259
hyperpolymath wants to merge 1 commit into
mainfrom
ci/sonarcloud

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Wires SonarCloud (SonarQube Cloud) CI analysis for boj-server.

  • .github/workflows/build.yml — the SonarCloud setup-wizard workflow (SHA-pinned actions/checkout + SonarSource/sonarqube-scan-action@v8.1.0), runs on push to main and PRs. Added a top-level permissions: contents: read for Scorecard.
  • sonar-project.properties — org hyperpolymath, key hyperpolymath_boj-server, with sonar.exclusions so only the analysable JS bridge + scripts are scanned (Idris2/Zig/Elixir have no SonarCloud analyser; vendored/generated/build/proof/dep trees excluded).

Prereqs (done/needed): SONAR_TOKEN repo secret (added ✓); the project imported on SonarCloud with CI-based analysis selected (disable Automatic Analysis, or SonarCloud errors that both are running).

The quality-gate badge is added to the README in #256.

🤖 Generated with Claude Code

Adds the SonarCloud setup-wizard workflow (SHA-pinned actions, build.yml) and
sonar-project.properties (org hyperpolymath, key hyperpolymath_boj-server)
with exclusions so only the analysable surface (the JS bridge + scripts) is
scanned — Idris2/Zig/Elixir have no SonarCloud analyser, and vendored,
generated, build, proof, and dependency trees are excluded.

Requires the SONAR_TOKEN repo secret and the project imported on SonarCloud
with CI-based analysis (Automatic Analysis disabled).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant