---
title: "Confirm gate requirements | Proofline Help"
description: "A delivery target's gate requirements record what changes to it need from the environment: a key that must be set, a network setting, a database connection or a capacity. Proofline proposes entries from code it reviewed, and only a person with write access to the repository on GitHub settles them. Confirmed requirements do not yet change a gate's result; What gates do with them explains."
url: https://proofline.sh/help/gate-requirements/
---

[Help center](/help/)

# Confirm gate requirements

A delivery target's gate requirements record what changes to it need from the environment: a key that must be set, a network setting, a database connection or a capacity. Proofline proposes entries from code it reviewed, and only a person with write access to the repository on GitHub settles them. Confirmed requirements do not yet change a gate's result; [What gates do with them](#what-gates-do-with-them) explains.

## Open the gate requirements

1.  Open the environment's **Setup → Repositories** page and select the repository.
2.  Under **Gate requirements**, select the delivery target. Each link is named for the target's release environment, or for the repository when the target names none.

The section appears once the repository is linked to the environment and the environment's configuration holds a delivery target for it.

When a delivery target has a proposal that nobody has confirmed or dismissed, the Inbox shows a row under the environment's name: **Gate requirements proposed for** the repository **wait for a person to confirm them.** **Since** gives when the oldest open proposal was made. Select **Review gate requirements** to open the target's page. The row stays until each proposal is confirmed or dismissed, and anyone who can see the repository sees it.

## How Proofline proposes an entry

When Proofline reviews a pull request in a repository linked to the environment, it can propose entries from the code the change touches. **Cited lines** under a proposal link to the lines it read, at the reviewed commit.

Proofline proposes a required key with a Cloud Run binding, a Cloud Run ingress or VPC egress setting, or a Cloud SQL connection with its pool size, and only when the code states the value exactly. A key the code names only in words, a binding it does not show or a pool size in prose proposes nothing. The target gets no second entry for a requirement it already holds as proposed or confirmed. ECS entries come only from a person.

## Who can act

Anyone in the organization who can see the repository can read its gate requirements. Only a person with write access to the repository on GitHub can confirm, dismiss, add or withdraw an entry, and Proofline asks GitHub at each change. Without that access, the actions are unavailable and the page says **Needs write access to** the repository **on GitHub.**

Proofline never confirms an entry itself, and API tokens and coding agents cannot change entries. Each confirmed entry names the person who confirmed or added it.

## Settle a proposal

The page lists entries under **Proposed**, **Confirmed** and **Withdrawn**.

-   Select **Confirm** to accept a proposal. It moves to **Confirmed**, and **Confirmed by** names you.
-   Select **Dismiss** to reject it. It moves to **Withdrawn**, and **Withdrawn by** names you.

A withdrawn entry cannot be confirmed again. To require it later, add it.

## Add a requirement

1.  Select **Add requirement**.
2.  Choose the **Requirement** and complete its fields.
3.  Select **Add requirement**.

| Requirement | Fields |
| --- | --- |
| **Required key** | **Key name**, and **Provided as**: **Environment variable** or **Secret Manager secret** on Cloud Run; **Plain environment variable**, **Secrets Manager secret** or **SSM parameter** on ECS. A key name uses letters, digits, `_`, `.` and `-`, and does not start with a digit. |
| **Cloud Run ingress** | **Ingress**: **All traffic**, **Internal only** or **Internal and Cloud Load Balancing**. |
| **Cloud Run VPC egress** | **VPC egress**: **All traffic** or **Private ranges only**. |
| **Cloud SQL connection** | **Connection name** as `project:region:instance`, and **Pool size** in connections. |
| **ECS reach to RDS** | **RDS instance** identifier and **Port**. |
| **ECS capacity** | **Running tasks**, and optionally **CPU units** and **Memory** in MiB. |

Quantities are whole numbers from 1. An entry you add is confirmed at once, and **Added by** names you. Adding a requirement that the target holds as a proposal confirms that proposal; adding one it already holds confirmed changes nothing.

## Change or withdraw a requirement

An entry cannot be edited. To change one, withdraw it and add the new value.

1.  On the confirmed entry, select **Withdraw**.
2.  In **Withdraw this requirement?**, select **Withdraw**.

The entry moves to **Withdrawn** and keeps who proposed or added it and who withdrew it.

## What gates do with them

No gate counts a proposed or withdrawn entry. Confirmed requirements do not yet change a [deployment decision](/help/deployment-protection/) or a [merge gate](/help/merge-gate/) result.

## Related guides

-   [Configure deployment protection](/help/deployment-protection/)
-   [Clear Inbox setup tasks](/help/inbox-setup-tasks/)
-   [Link repositories and environments](/help/repository-environments/)
