pull-request-risk-assessment

To assess pull request risk, evaluate changes against change management criteria including customer impact, information security, uncertainty, infrastructure impact, and rollback complexity to classify the deployment as Low or High risk.

A high-risk pull request change involves significant customer impact, information security vulnerabilities, high uncertainty, broad infrastructure impact, or complex rollback requirements, necessitating detailed rollout, verification, and rollback plans before deployment.

Evaluate infrastructure changes by analyzing their impact on shared solutions and isolation boundaries. This risk assessment process categorizes the changes and outlines necessary deployment plans to prevent unintended negative impacts on customers.

You need a rollback plan for a pull request deployment when the risk assessment classifies your changes as High risk, which typically occurs when modifications involve complex infrastructure updates or shared solution dependencies.

Yes, this skill guides users through assessing risk for both shared and isolated solution changes. It evaluates the specific change management criteria to determine if the isolated modification poses any customer or information security risks.