GitHub拉取请求触发Azure DevOps中的所有管道

GitHub拉取请求触发Azure DevOps中的所有管道,git,github,azure-devops,Git,Github,Azure Devops,我在Azure DevOps中有3个管道,每个分支都在上,代码在GitHub上 每当我做任何拉动请求时,我的3条管道都会被触发。我怎样才能避免呢 消息上写着“PR自动为” 我的3条管道使用分离的支管: 开发管道 trigger: branches: include: [develop] paths: include: - backend/* trigger: branches: include: [staging] paths: i

我在Azure DevOps中有3个管道,每个分支都在上,代码在GitHub上

每当我做任何拉动请求时,我的3条管道都会被触发。我怎样才能避免呢

消息上写着“PR自动为”

我的3条管道使用分离的支管:

开发管道

trigger:
  branches:
    include: [develop]
  paths:
    include:
      - backend/*
trigger:
  branches:
    include: [staging]
  paths:
    include:
      - backend/*
trigger:
  branches:
    include: [master]
  paths:
    include:
      - backend/*
分段管道

trigger:
  branches:
    include: [develop]
  paths:
    include:
      - backend/*
trigger:
  branches:
    include: [staging]
  paths:
    include:
      - backend/*
trigger:
  branches:
    include: [master]
  paths:
    include:
      - backend/*
生产线

trigger:
  branches:
    include: [develop]
  paths:
    include:
      - backend/*
trigger:
  branches:
    include: [staging]
  paths:
    include:
      - backend/*
trigger:
  branches:
    include: [master]
  paths:
    include:
      - backend/*
我在文档中找到了如何禁用所有PRs的运行添加:

pr: none
它的根是这样的:

trigger:
  branches:
    include: [develop]
  paths:
    include:
      - backend/*

pr: none
此外:

重要的

YAML PR触发器仅在GitHub和Bitbucket云中受支持。如果 如果使用Azure Repos Git,则可以为生成配置分支策略 验证以触发生成管道进行验证


你看过YAML文档了吗?具体来说,就是让您定义和控制GitHub PR构建行为的部分?我将在中尝试
PR:none
。@DanielMann tx,我昨天找不到它。谢谢您在这里分享您的解决方案,请接受您的解决方案作为答案?因此,它将有助于其他成员谁得到同样的问题,找到解决办法容易。祝你今天愉快:)