title: How to avoid triggering build if there is a local NuGet package in project dependencies in Azure DevOps
body: <p>I am new to Azure DevOps, we use Azure DevOps pipelines in our projects. When we have a pull request for a branch that is using a local NuGet package from another project, the build will fail until we bump up that package, which is resource consuming.</p>
  <p>Is there a way to check the content of .Net project dependencies and avoid triggering the build if some local NuGet package is there (considering that we have some custom naming for local packages)? I read about <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/conditions?view=azure-devops&amp;tabs=yaml" rel="nofollow noreferrer">conditions</a> but couldn't find something specific that can do what I need.</p>