Hi,
We have enabled the following setting to ignore code coverage for changes with fewer than 20 lines, but still failing for 1 line code change in PR
Hey there.
Maybe a dumb question, but have you reanalyzed your PR since configuring “Ignore duplication and coverage on small changes”? Changing it after the fact won’t retroactively update an existing QG failure.
Hi Colin,
Yes, we’ve reanalyzed the PR multiple times, but we’re still seeing the same results.
FYI, this is an older repository, and there have been no changes to our configurations.
However, the issue has started occurring only in the past few days. Could you please let us know if there have been any updates on the SonarCloud side (Team Plan)?
I can reproduce this, so I’m flagging this urgently for the team.
Thank you, Colin.
Hey @Kiran_Pansare
We flipped a flag – can you give this another try? You’ll have to reanalyze.
Seems working now, Thanks
Hello,
While reading the previous comments, the problem seems to have been solved, but we are currently experiencing the same issue on one of our projects.
Has there been a regression?
Hi, I’m seeing this in my project as well in January 2026:
total lines: 5
to cover lines: 3
On the settings page I see settings ‘{“ignoreSmallChanges”:true}’
@Colin Is there some more information we can provide to debug this ? I’m using analysis method manual “You are currently running analysis through your CI”, with mvn org.sonarsource.scanner.maven:sonar-maven-plugin:5.0.0.4389:sonar
on a githubproject with “GitHub repository binding Bound” and triggering the build in githubaction on
"
on:
pull_request:
”
running with mvn -X, I didn’t find much…
2026-01-21T11:01:54.6035086Z [DEBUG] SCM reported 2 files changed in the branch
In the github UI, the PR is reported as
+1-1Lines changed: 1 addition & 1 deletion
+6-2Lines changed: 6 additions & 2 deletions
In the sonar background tasks I don’t see much info either, at least it confirmes the scanner version:
Thanks in advance,
Jon