> ## Documentation Index > Fetch the complete documentation index at: https://docs.cysmiq.com/llms.txt > Use this file to discover all available pages before exploring further. # Review PR results > Understand Cysmiq statuses and managed comments in GitHub, GitLab, and Bitbucket Cloud. Use the statuses and managed comment on a pull request to understand whether the security scan completed, what changed, and whether a policy requires action. ## Prerequisites * Connect the repository to Cysmiq. * Enable repository scanning. * Enable **VCS status checks** and **PR decoration** for the repository or an inherited scope. ## Understand the results GitHub shows three independent Cysmiq results with the other checks for the pull request revision: * **Cysmiq Scan** shows whether the scan ran successfully and whether unresolved actionable findings meet the configured blocking threshold. * **Cysmiq PR Assessment** shows whether the pull request introduced, reopened, fixed, or changed actionable findings. * **Cysmiq Policies** shows whether the revision has blocking or warning-only policy violations. GitLab receives the same three Cysmiq results as commit statuses and summarizes their combined outcome in the merge request pipeline area: * **Cysmiq Scan** shows whether the scan ran successfully and whether unresolved actionable findings meet the configured blocking threshold. * **Cysmiq PR Assessment** shows whether the merge request introduced, reopened, fixed, or changed actionable findings. * **Cysmiq Policies** shows whether the revision has blocking or warning-only policy violations. Bitbucket Cloud shows the same three Cysmiq results as build statuses on the pull request revision: * **Cysmiq Scan** shows whether the scan ran successfully and whether unresolved actionable findings meet the configured blocking threshold. * **Cysmiq PR Assessment** shows whether the pull request introduced, reopened, fixed, or changed actionable findings. * **Cysmiq Policies** shows whether the revision has blocking or warning-only policy violations. A completed scan can have a failed assessment or policy result. This means the analysis finished, while the pull request still requires attention. The VCS may still allow the pull request to be merged unless the Cysmiq results are configured as required checks. ## Review statuses Open the pull request and review the checks near the merge controls. GitHub shows whether all checks passed or which checks require attention. GitHub pull request overview showing failed Cysmiq checks Open an individual Cysmiq check when you need its complete summary and a direct link to the matching Cysmiq result. GitHub Cysmiq pull request assessment check with a link to the result in Cysmiq Open the merge request's pipeline and review the **external** group. GitLab shows the three Cysmiq commit statuses together with their individual outcomes. GitLab pipeline showing the three Cysmiq commit statuses in the external group Open the pull request and review its build statuses. Bitbucket Cloud shows each Cysmiq result and its outcome in the builds panel. Bitbucket Cloud pull request showing the three Cysmiq build statuses ## Review the comment Read the managed Cysmiq comment for the findings, policy violations, and links that contributed to the result. GitHub pull request with a managed Cysmiq security result comment Read the managed Cysmiq comment for the findings, policy violations, and links that explain the status. GitLab merge request with a managed Cysmiq security result comment Read the managed Cysmiq comment for the findings, policy violations, and links that explain the build statuses. Bitbucket Cloud pull request with a managed Cysmiq security result comment ## Act on the result For a failed assessment or policy result, use the managed comment or status link to open the matching scan, finding, assessment, or policy violation in Cysmiq. Confirm that its revision matches the pull request head before remediation. For a passing result, verify that every required Cysmiq status has completed successfully before merging. For configuration options, thresholds, and comment triggers, see [VCS status updates](/scanning/vcs-status-updates). For the difference between scan status and result labels, see [Scan list view](/scanning/scan-list-view).