---
title: "Verify the GitHub protection rule on a delivery target | Proofline Help"
description: "Open the environment’s linked repository to check whether GitHub currently lists Proofline as an enabled protection rule for the mapped environment."
url: https://proofline.sh/help/deployment-check-protection-rule/
---

[Help center](/help/)

# Verify the GitHub protection rule on a delivery target

Open the environment’s linked repository to check whether GitHub currently lists Proofline as an enabled protection rule for the mapped environment.

## Read the rule status and recheck it

Open the environment's **Setup → Repositories** page and select the linked repository. Under **Deployment protection**, map the **Release environment** to the **GitHub deployment environment** and select **Save**. Proofline checks GitHub for that saved mapping; an unsaved mapping must be saved before it can be checked.

Read **GitHub protection rule** and its **Checked** time:

-   **Enabled** means GitHub listed Proofline as an enabled protection rule on the mapped GitHub Environment at that time. Each deployment job still needs to declare that Environment; this check does not approve a deploy or verify a revision.
-   **Not enabled** means GitHub listed no enabled Proofline rule on that Environment. Select **Open GitHub Environment settings**, enable Proofline under the Environment's deployment protection rules, then return and select **Check again**.
-   **Not verified** means the check could not establish the rule's state. Read the reason beside it, address any reported setup problem, and select **Retry** when offered. If the saved mapping changed, reload the page as instructed.

Saving the mapping does not enable the rule in GitHub. After changing the rule there, use **Check again** to refresh the result in Proofline.

## Related guides

-   [Configure deployment protection](/help/deployment-protection/)
-   [Create an environment](/help/create-environment/)
