I would like to define different quality gate on a single project because I did not have the same requirement between my PR and my main branch.
For example, I would like that all my PR reach 90% of code coverage on new code and at the same time, I would ensure that code coverage on my main branch reach 60% on new code (with new code definition configured at âprevious versionâ)
It would be valuable for my teams starting to use SonarQube on legacy projects.
Youâre right, on coverage the impact will be limited unless developers bypass quality gate status and merge anyway.
I can see more discrepancies on duplication (I could introduce only 1% on my PR but it could result in more than 3% in the target branch) and number of code smell.