79456306

Date: 2025-02-21 03:34:22
Score: 0.5
Natty:
Report link

Based on the current information, I am guessing that there may be a YAML file in your "Staging" branch with the same name as the YAML file used to create the pipeline.

If such a file exists in "Staging" branch, please check whether there is a trigger section in the YAML.

  1. If "Disable implied YAML CI trigger" is not enabled and no trigger section is added in the YAML, then the YAML pipeline is configured by default with a CI trigger on all branches.

    You can set trigger to none to disable the CI trigger OR enable "Disable implied YAML CI trigger" settings in your project settings.

    See details from CI triggers. enter image description here

  2. If there is trigger session and "Staging" branch is a trigger branch, please remove it.

If there isn't such YAML file in "Staging" branch, please share a screenshot of the build summary page of the CI triggered build. URL format is https://dev.azure.com/{orgName}/{projectName}/_build/results?buildId={buildId}&view=results.

Reasons:
  • RegEx Blacklisted phrase (2.5): please share
  • Long answer (-0.5):
  • Has code block (-0.5):
  • High reputation (-1):
Posted by: Ziyang Liu-MSFT