title: Azure Devops Path Exclude trigger that does NOT seem to be working as documented
body: <p>I have the following trigger defined in an &quot;azure-pipelines.yaml&quot; definition</p>
  <pre><code>trigger:
    batch: true
    branches:
      include:
      - master
    paths:
      exclude:
      - config/luna-tenant-bio-annotation-prod.yaml
      - azure-pipelines-prod.yaml
  </code></pre>
  <p>but When changes are made to the azure-pipelines-prod.yaml listed in &quot;exclude&quot; a new CI is still started for this build definition.</p>
  <p>I'm trying to have a separate pipeline for our production code to do a few extra steps but the regular environment is still triggering on changes to prod only updates which is causing duplicate updates.</p>
  <p>Thankfully the inverse is not happening as I have excludes for the dev, test, stage environments in the azure-pipelines-prod.yaml trigger and it is working as expected.</p>
  <p>I even tried to override the &quot;YAML triggers&quot; in the pipeline definition but it still is starting this pipeline on any change to the master branch and seems to be ignoring the &quot;paths:&quot; section</p>
  <p>what do I have wrong????</p>