Ondrej Kmoch

You are correct: only "main" files are reported to SonarQube for found issues. All other LintR issues found on for example test files will be ignored. I can imagine it...

Hi, it would may be make sense to make it configurable. There can be projects where developers care about production files quality mainly and tests could be more relaxed so...

Hi, I have left the company and I created new fork https://github.com/kmoco2am/sonar-r-plugin/ which I would like to use for further development.

It has not been planned yet. If you provide an example of the outputs you want to consume by the plugin I can add it. It should be easy.

So finally I have found some time to look at this. I am sorry for delay. I found out that SonarQube is able to consume "generic" coverage data: https://docs.sonarqube.org/latest/analysis/generic-test/ And...

So, I have added code coverage into sample project. I had to add a piece of R code to remove module name which is included by `to_sonarqube` function and it...

Did you run LintR before actually running SonarQube scanner? The stacktrace is saying that the JSON file for LintR outputs is empty.

We have the plugin deployed, works properly with the fix and cron is working normally too.

@darxriggs Is there anything I can do to make this PR merged?