title: Pull Request analysis and Quality Gate on SonarQube
body: <p>I have installed SonarQube 7.6 Developer Edition, and starting using it on my development environment pipeline. 
  My coding approch is <a href="https://trunkbaseddevelopment.com/" rel="nofollow noreferrer">Trunk Based Development</a>. We have only one mainline (master or trunk or develop as you prefer to define, but only one mainline)</p>
  
  <p>Actually all changes on code pass through a Pull Request, that as I have understood, into SonarQube is recognized as a <a href="https://docs.sonarqube.org/latest/analysis/pull-request/" rel="nofollow noreferrer">Short Lived Branch</a> and only this <a href="https://docs.sonarqube.org/latest/branches/short-lived-branches/" rel="nofollow noreferrer">hard coded rules</a> are applied</p>
  
  <p>Error conditions:</p>
  
  <ul>
  <li>new open bugs > 0 </li>
  <li>new open vulnerabilities > 0</li>
  <li>new open code smells >
  0</li>
  </ul>
  
  <p>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. </p>
  
  <p>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?</p>
  
  <p><a href="https://i.stack.imgur.com/3BQtQ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/3BQtQ.png" alt="enter image description here"></a>I have tried to define * as long lived branches pattern, but it does not work. attached a screenshot.</p>