We are going to take a look at this, the behaviour is indeed strange. Do you observe this behaviour on every PR? Was it working correctly at some point of time for your project?
Yes, this started happening on every PR recently. It was working correctly since we adopted SonarCloud back in December. I think it started happening some time in March. Thank you so much for looking into it
We are looking at all the cases reported here in the forum. We do need the logs of the scanner in debug to look into possible causes. The main thing to check is if SCM is being used to detect new lines and if that’s the case, if the configuration and local references are correct.
I am just running a build with verbose on now. Can you explain a bit more about SCM? How do you go about turning it on and off, or is that something out of our control, what does using it do?
When possible, the scanner checks which lines were changed since the fork point between the base and target branches. It does it by loading information from supported SCMs such as git or svn.
Thanks Kiryl.
Is the commit with sha1 b596a0bd9647c20d10a3d417e9f2a57f4eed916a the correct fork point (last common commit) between master and feature/234453-fix-duplicate-external-provider-services?