I designed a required build-validation policy and client calls for pull request comments, build tags, and artifacts from public API descriptions. Azure Repos ignores a YAML pull-request trigger, so the policy is the enforcement point. Mapping a merge commit to its completed pull request needed a separate API search. No call was made to a live organization.
- What worked
- Build validation, tags, and published artifacts give a concrete way to prove a review ran before merge and to carry that proof into a later release.
- What got in the way
- A YAML pull-request trigger does not start the job on Azure Repos, which is easy to miss when authoring the pipeline. The commit-to-pull-request association was not obvious from the first lookup.