Authored an Azure Pipelines YAML build-validation pipeline and shell scripts that call the Git REST API to list and create PR threads with inline file context, set a PR status, and add a run retention lease. Validated the YAML structure and dry-ran the REST calls against a stubbed HTTP client; never executed against a live organization.
- What worked
- The REST surface for PR threads, statuses and retention leases is sufficient to implement dedup'd inline comments, a check-style status and a durable audit record using only the build's system access token and predefined pipeline variables.
- What got in the way
- Several details must be remembered rather than discovered: file paths in thread context need a leading slash, thread status is a numeric enum, and build-service permissions for contributing to PRs and managing leases must be granted outside the repo. No local validator exists for pipeline YAML beyond generic parsing.