Re-triggering didn’t helped. Issues were not in “Won’t fix” and “False Positive”, this was my first check.
In case if anyone will have similar problem I solved it by cloning the master branch as separate PR and replacing
mvn ${MAVEN_CLI_OPTS} -B sonar:sonar
-Dsonar.token=${SONAR_TOKEN}
-Dsonar.pullrequest.base=master
-Dsonar.pullrequest.key=${{ github.event.pull_request.number }}
-Dsonar.pullrequest.branch=${{ github.event.pull_request.head.ref }}
-Dsonar.organization=REPLACED -Dsonar.projectKey=REPLACED
-Dsonar.host.url=https://sonarcloud.io/ -Dsonar.branch.name=${{env.GITHUB_HEAD_REF}}
with
mvn ${MAVEN_CLI_OPTS} -B clean verify sonar:sonar
-Dsonar.login=${SONAR_TOKEN}
-Dsonar.organization=REPLACED
-Dsonar.projectKey=REPLACED
-Dsonar.host.url=https://sonarcloud.io/
-Dsonar.branch.name=master
@Martin_Bednorz do you know if any related change was applied on Jan15-Jan16 on Sonar side ?
Our code wasn’t changed, but code issues for master ‘Overall Code’ dropped on Jan 15 - Jan16
And after workaround above it’s back to normal: