What should you use to implement the code quality restriction on the release pipeline for the investment planning applications suite?
When a release is created from a release pipeline that defines approvals, the deployment stops at each point where approval is required until the specified approver grants approval or rejects the release (or re-assigns the approval to another user). Scenario: Code quality and release quality are critical. During release, deployments must not proceed between stages if any active bugs are logged against the release. Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/approvals