> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/flow-control-mechanism/appsec-cicd-152.md).

# Repository does not dismiss pull request approvals on the default branch when new commits are pushed

## Rule Details

|                       |                        |
| --------------------- | ---------------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_152      |
| Category              | Flow Control Mechanism |
| Severity              | MEDIUM                 |

## Impact

When a pull request is approved, it means that the code changes have been reviewed and can be merged into the target branch. However, if new commits are added to the request after it has been approved, those commits are not automatically required to be reviewed again. This can lead to bypassing a branch protection rule by merging unreviewed commits into the default branch, potentially introducing malicious code.

## Recommended Solution - Buildtime

It is recommended to configure branch protection rules to dismiss pull request approvals when new commits are pushed.

1. In GitHub, browse to the repository **Settings** > **Branches**.
2. Ensure or add a branch protection rule on the default branch.
3. Under **Protect matching branches**, select **Requires a pull request before merging**.
4. Check **Dismiss stale pull request approvals when new commits are pushed**.

   Note: This option is available after performing step 3 above.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/flow-control-mechanism/appsec-cicd-152.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.