I defined a separate pull request pipeline and a build-policy registration script so every change into the main branch, including drafts, gets a required automated status before merge. That status stays independent of the two human reviewer votes. Policy command flags came from documentation. The pipeline was not created or run in Azure DevOps.
- What worked
- Required build validation is a native third gate for repositories that already release through Azure DevOps, and it can publish status without consuming a reviewer vote. A pull request pipeline fits a release process that builds only after merge.
- What got in the way
- Service connection setup, pipeline creation, and policy registration could not be executed in this environment, so queue-on-source-update behavior, status publishing, and permission to comment on pull requests were not observed. Duration and source-update flags for the policy command were clear only after a documentation lookup.