ci: SonarCloud advisory (non-blocking main CI)

[KooshaPari]

User description

SonarCloud advisory: sonar-project.properties disables autoscan App check; sonarcloud.yml uses continue-on-error.

---

Note

Low Risk
CI-only change with read-only permissions and non-blocking behavior; requires a repo secret for Sonar uploads but does not alter application runtime code.

Overview
Adds SonarCloud as an advisory CI check on pushes and pull requests targeting main, master, and develop.

A new workflow checks out the repo with full history (fetch-depth: 0), runs the official Sonar scan action, and uses continue-on-error: true so scan failures do not block merges. Concurrency cancels in-progress runs per ref; job permissions are read-only on contents.

sonar-project.properties wires the scan to organization kooshapari and project key KooshaPari_heliosBench. SONAR_TOKEN (and default GITHUB_TOKEN) must be configured in GitHub for uploads to succeed.

^{Reviewed by Cursor Bugbot for commit 6dbb64c. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Add a non-blocking SonarCloud check for main branch changes

What Changed

• Runs SonarCloud scans on pushes and pull requests targeting main, master, and develop
• Scan results are advisory only, so failures do not block merges
• Limits each new scan run to the latest update for the same branch or pull request
• Sets up the project for SonarCloud uploads with the repository’s organization and project key

Impact

✅ Earlier code-quality feedback on main branch changes
✅ Fewer blocked merges from SonarCloud issues
✅ Less wasted CI time from repeated scan runs

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[kilo-code-bot]

WARNING: The job is set to continue-on-error: true, which means that if the SonarCloud scan fails, the job will still be marked as successful. This could hide failures. Consider removing this setting or setting it to false unless there is a specific reason to continue on error.

[kilo-code-bot]

SUGGESTION: Consider adding a step to set up Python before running the SonarCloud scan to ensure proper analysis of Python code.

[kilo-code-bot]

Code Review Summary

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	1

Issue Details (click to expand)

CRITICAL

None

WARNING

File	Line	Issue
.github/workflows/sonarcloud.yml	15	The job is set to continue-on-error: true, which means that if the SonarCloud scan fails, the job will still be marked as successful. This could hide failures. Consider removing this setting or setting it to false unless there is a specific reason to continue on error.

SUGGESTION

File	Line	Issue
.github/workflows/sonarcloud.yml	16	Consider adding a step to set up Python before running the SonarCloud scan to ensure proper analysis of Python code.

Other Observations (not in diff)

None

Files Reviewed (2 files)

• .github/workflows/sonarcloud.yml - 2 issues
• sonar-project.properties - 0 issues

---

_{Reviewed by nemotron-3-super-120b-a12b-20230311:free · 979,261 tokens}