title: Multiple separate triggers in azure-pipelines.yml
body: <p>I currently have a monorepo with services in subdirectories that I'm leaning towards turning into a multirepo with a metarepo.</p>
  
  <p>One of the reasons I decided to give Azure DevOps a try was someone told me you can have triggers on the subdirectories like:</p>
  
  <pre><code>trigger:
    branches:
      include:
      - master
    paths:
      include:
      - client
  </code></pre>
  
  <p>Tested and it works.</p>
  
  <p>However, what I'm wondering is if it possible to have multiple independent triggers, or does this require either a polyrepo or multiple <code>.yml</code>? The reason being if there are only changes in the <code>client</code> service, it only triggers that set of tests, build, and deployment, while not triggering the <code>api</code> service to run tests, build, and deploy.</p>
  
  <p>For example:</p>
  
  <pre><code>trigger:
    branches:
      include:
      - master
    paths:
      include:
      - client
  
    stages:
      ...
      Run tests
      If tests pass, build and push to ACR
      Deploy to AKS
      ...
  
  trigger:
    branches:
      include:
      - master
    paths:
      include:
      - api
  
    stages:
      ...
      Run tests
      If tests pass, build and push to ACR
      Deploy to AKS
      ...
  </code></pre>
  
  <p>That way, changes in one doesn't cause the entire application to be rebuilt, just what changed.</p>
  
  <p>However, does this require multiple <code>.yml</code> files (not even sure if anything other than <code>azure-pipelines.yml</code> is recognized), does this necessitate a polyrepo, or is this doable in a single <code>azure-pipelines.yml</code> that I'm just not seeing?</p>