SonarQube: 8.3, Scanner: 220.127.116.114
We currently use SonarQube to track release code coverage. We use separate branches for each release. Since we want to track code coverage trends across releases, we currently do analysis on the release branch, but we specify branch as
master and tag it with a release version when we upload code coverage data.
Now we are working on using SonarQube for GitHub PR analysis.
- How does SQ calculate estimated code coverage after merge?
- Documentation only refers to analysis of the feature branch. Do we need to set up a regular analysis of the
masterbranch for SQ to be able to calculate coverage after merge to
- Does our current implementation of release code coverage affect PR analysis?