title: Azure DevOps release pipeline with git-flow
body: <p>I'm attempting to configure a release pipeline in Azure DevOps (on premises) to support a git-flow strategy.  What I'm trying to achieve:</p>
  
  <ol>
  <li>Commits to 'release/*' trigger a build of the software and publish to a location for QA</li>
  <li>Commits to 'master' take the <strong>same</strong> software build (artifact) from step 1 and publish to Production location</li>
  </ol>
  
  <p>So when I do a git-flow 'start release' the software is made available for testing/QA and when I 'finish release' it's made available to users.</p>
  
  <p>My build pipeline works fine, it's triggered by the release branch and concludes with a Publish Artifact task.  My release pipeline uses this artifact and has stages for QA and Production but the Production stage never triggers.  For QA I've got an artifact filter for 'release/*' and on Production for 'master'.</p>
  
  <p>Is there a way to trigger my second release pipeline stage on a commit to 'master'?</p>