Our recommendation is to exclude them from the analysis by marking them as auto-generated.
That is what we did for now, and that is working.
Did you see them in SonarQube Cloud, see issues on them?
We did exclude them using by adding them to sonar.exclusions. but this did not exclude them from being analysed (as your performance article mentioned) we did not see them in SQ Cloud.
What was the update you did?
we updated to the then (10/10/2024) latest version of
- dotnet/sdk:8.0
- openjdk-17-jre
- dotnet-coverage
- dotnet-sonarscanner