I have installed SonarQube 7.6 Developer Edition, and starting using it on my development environment pipeline. My coding approch is Trunk Based Development. We have only one mainline (master or trunk or develop as you prefer to define, but only one mainline)
Actually all changes on code pass through a Pull Request, that as I have understood, into SonarQube is recognized as a Short Lived Branch and only this hard coded rules are applied
• new open bugs > 0
• new open vulnerabilities > 0
• new open code smells > 0
That is a subset of my Quality Gates conditions. It means that PullRequest could pass quality gate (becouse is recognised like Short-Lived Branch) and when it is merged into mainline (master/trunk) is applied my Quality Gates rules and could fail on merge. How could I know if it break quality gate before PR approvement, or more easy, how to identify a Pull Request as a Long Lived Branch?
I have tried to define * as long lived branches pattern, but it does not work. attached a screenshot.