Sonar Community Roundup, February 3 - February 9

Hello Sonar Community!

What a week – we released SonarQube v10.4 with one of the coolest features folks have been waiting on for a while: Pull requests will now show issues that will be fixed by the merge. :tada:

While SonarLint already gives developers instant feedback when fixing an issue, this will allow other reviewers to see your hard work as well. This also fills in the gaps on languages/rules/IDEs not supported by SonarLint!

Okay, enough geeking out–or is it only the start? Like every week we want to spend some time saying thanks to everyone who prompted interesting discussions and gave us feedback on Sonar products that will help us continuously improve.



  • When analyzing a pull request, SonarCloud can use a cache of the target branch to speed up the analysis. But what happens when you force a branch analysis on a pull request (when the pull request closes, for example)? @Jordi-Pineiro found out and it led to really wonky analysis results. We’ll fix this with SonarSource/sonar-scanner-msbuild #8170

Rule & Language Improvements:

In other Community news, @daniel happened to come across our intern’s website from last year and gave some kudos. It’s true – every year at SonarSource a bunch of French teenagers invade the office to be led by @JBL_SonarSource and learn about what we do! :heart: We’ll have our next cohort soon.

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.

Colin, @ganncamp, and @leith.darawsheh