79098678

Date: 2024-10-17 15:01:40
Score: 2.5
Natty:
Report link

I was able to solve it in a really easy way.

Just adding "pr: none" to my pipeline after the trigger.

So when there is a pull request it doesn't trigger before the end of the merge. Just when the merge is completed it triggers the pipeline after the branch receives the new changes.

I followed the microsoft documentacion from this link: https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#pr-triggers

enter image description here

trigger:
- <branch_name>

pr: none
Reasons:
  • Blacklisted phrase (1): this link
  • Probably link only (1):
  • Has code block (-0.5):
  • Low reputation (1):
Posted by: Pedro Duque