1. Confirmed to be working in staging before implementing the change in production, where possible.
1. Confirmed to be working in staging before implementing the change in production, where possible.
1. Confirmed to be working in the production with no new [Sentry](https://about.gitlab.com/handbook/engineering/#sentry) errors after the contribution is deployed.
1. Confirmed to be working in the production with no new [Sentry](https://about.gitlab.com/handbook/engineering/monitoring/#sentry) errors after the contribution is deployed.
1. Confirmed that the [rollout plan](https://about.gitlab.com/handbook/engineering/development/processes/rollout-plans) has been completed.
1. Confirmed that the [rollout plan](https://about.gitlab.com/handbook/engineering/development/processes/rollout-plans) has been completed.
1. If there is a performance risk in the change, I have analyzed the performance of the system before and after the change.
1. If there is a performance risk in the change, I have analyzed the performance of the system before and after the change.
1.*If the merge request uses feature flags, per-project or per-group enablement, and a staged rollout:*
1.*If the merge request uses feature flags, per-project or per-group enablement, and a staged rollout:*
