Used branch policy concepts and pipeline configuration to place an automated review first while preserving two human approvals. Repository pipeline config supported pull request triggers, staged validation, and published reports. Remaining live policy activation was left as external setup.
- What worked
- Pipeline pull request triggers, staged jobs, and required validation checks mapped cleanly to the two-reviewer workflow without a new vendor.
- What got in the way
- Live branch policy and build validation could not be observed from the repository alone; final activation remained unverified.