Question Regarding Local Code Scanning Without Committing to Repository

Hello SonarQube Community!

I have a question regarding local code scanning without committing to the repository. I understand that committing to the repository is recommended for accurate and comprehensive results, but I’m curious if there are alternative approaches for testing or experimenting with code scanning locally without committing.

I’ve encountered scenarios where I’d like to scan code locally without making a commit first, and I’m interested in understanding the implications and limitations of this approach. Are there specific configurations or best practices for achieving this? Any insights from the community would be greatly appreciated!

Thank you in advance for your assistance.


that’s what the Sonarlint IDE plugin is for.
see documentation

switch for other IDEs



1 Like