About `SonarSource/sonarcloud-github-c-cpp` action
Regarding this action, it seems that it can be quite inefficient to workaround, especially since much of the tests and code-coverage can be already processed in other workflows. Instead it would be...
View ArticleClik here to view.
About `SonarSource/sonarcloud-github-c-cpp` action
Hey @LecrisUT Keep in mind that using compilation commands is not a replacement for the build-wrapper in our eyes. Many users want (and need) to continue using the build wrapper. Where do you feel the...
View ArticleAbout `SonarSource/sonarcloud-github-c-cpp` action
The issue is that as we navigate from the main action, we are directed to use the C/C++ action which is where the documentation is lacking. Firstly, the naming is misleading, the convention for those...
View ArticleClik here to view.
About `SonarSource/sonarcloud-github-c-cpp` action
Hello @LecrisUT Cristian Le: Firstly, the naming is misleading, the convention for those actions is setup-sonarcloud similar to setup-python, setup-github-cli, etc. Aligning the names also allows for...
View ArticleAbout `SonarSource/sonarcloud-github-c-cpp` action
About the documentation, can you please tell me what you feel is missing if you read the pointed SonarCloud C++ analysis documentation? I did mention some points in another thread but: Usage of...
View ArticleClik here to view.
About `SonarSource/sonarcloud-github-c-cpp` action
Thanks for sharing that. Cristian Le: Usage of sonar.projectVersion is confusing. From another thread it seems that you should not change it for PRs, tag pushes, etc. I will see with our documentation...
View Article