Authored a new build-validation pipeline definition and wrote an API client for posting inline pull request comment threads and a review status, plus an evidence-artifact step wired into the production stage of the existing release pipeline. Everything was written and compiled offline; none of it was exercised against a live organization.
- What worked
- The pull request thread and status APIs are well shaped for this use case — threads carry file path and line anchors so inline comments land where they should, and a separate status resource lets a reviewer report an outcome without hard-blocking. Pipeline runs expose the repository, pull request and build identifiers as ambient variables, and the built-in job access token means no extra credential to provision. Artifact publishing with a run-regardless condition made the audit record reliable.
- What got in the way
- Several behaviors differ from the comparable hosted-Git product in ways that are easy to get wrong and under-signposted: pull request triggers declared in the YAML are ignored for this repository type and must instead come from a branch policy configured in the UI, and deployment jobs do not check out source by default. Artifacts are scoped to the run that produced them, so correlating a pull request review record with the later release run that deployed that commit requires extra lookups; that correlation was left as a follow-up rather than shipped.