---
title: "Set up an automatic fix rule for confirmed scan problems | Proofline Help"
description: "Configure the organization's rule for the environment and repository where confirmed scan problems should produce draft fix pull requests. Check the repository scope and limit before enabling it."
url: https://proofline.sh/help/enable-automatic-scan-fixes/
---

[Help center](/help/)

# Set up an automatic fix rule for confirmed scan problems

Configure the organization's rule for the environment and repository where confirmed scan problems should produce draft fix pull requests. Check the repository scope and limit before enabling it.

## Configure the fix rule

When automatic fixes are on, Proofline writes a fix for each problem that a confirmation records as **Confirmed** in the chosen environment and repository. The fix starts from the commit the confirmation recorded. Proofline opens it as a draft pull request into the repository's default branch and never merges it. Other outcomes start no fix. In an environment where the check is not qualified, confirmations end **No qualified check**, so the rule opens no pull request there. When a confirmed problem starts none, its confirmation says why.

You need to be an administrator of the organization in GitHub, with a sign-in to Proofline from the last 24 hours. Members who can read review settings see the page but cannot change it. Proofline administrators and API tokens cannot change it either. The rule opens no fix until **Generate fixes** is on under **Settings → Review policy → Automation**, and that setting starts off.

1.  Open **Settings → Review policy → Automatic fixes**.
2.  Choose the **Environment**.
3.  Choose the **Repository**. The list offers only repositories linked to that environment.
4.  Under **Findings**, keep **Scan findings**. **Investigation findings** opens no pull request yet, because Proofline does not confirm investigation findings.
5.  Choose **Open pull requests at most**. Fixes still being written and draft pull requests count toward this limit.
6.  Select **Turn on**.

If Proofline refuses the change, the reason appears under the form. When your sign-in is older than 24 hours, select **Sign in again** and retry.

The organization has one rule. Select **Change** to choose another environment, repository, kind of finding or limit, then select **Save** and confirm. Select **Turn off** and confirm to stop. Saving any change, even to the limit alone, replaces the rule. After either, each automatic fix in progress stops before its next write, and the draft pull requests the earlier rule opened stay open, but Proofline will not mark them ready for review. Removing the environment, or unlinking the repository from it, also turns automatic fixes off; turn them on again to continue.

## Related guides

-   [Schedule latent-risk scans](/help/latent-risk-scans/)
