Sonar Community Roundup, March 30 - April 5

Hello Sonar Community!

It’s been a big week here in the Community, with lots of help and guidance from you, our members, to improve our products and your experience with them. We’re grateful when you take the time to do that, so like every week we want to spend some time acknowledging everyone who prompted interesting discussions and gave us feedback to help us continuously improve.



  • Thanks to @Akash_Jaiswal and @sohara for helping us nail down an issue with SonarCloud projects when a GitHub organization name changes. A workaround is documented here and there are a few improvements we have in mind.

  • Thanks also to @huyz and @Latz who pointed out that we’ve forgotten to update the default GitHub Actions template for analysis. SCSCANGHA-1


The release, late last week, of SonarLint for IntelliJ 10.4.2 and this week’s release of SonarLint for VS Code of 4.4.2 seem to have solved most of the problems users were facing in the newer versions. We really regret the unanticipated growing pains you all experienced in the last few weeks. We tried something new here, with a unified engine across IDEs. It sets us up to go faster in the future, and we appreciate everyone’s continued patience and support and error reports(!) as we iron out the last few kinks.

Rule and Language Improvements

Once more, we extend our thanks to everyone mentioned here - and those we may have missed - for their efforts in strengthening this community and enhancing our Sonar products.

Please leave your own recognitions below – whether for another community member or a SonarSourcer who assisted you this week. If there’s someone you think should be acknowledged in next week’s roundup, don’t hesitate to let us know.

Ann, @Colin, and @leith.darawsheh