> 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-34.md).

# Pull request reviews not required before merging to the default branch

## Rule Details

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

## Impact

User accounts granted with Write permissions on an actively used repository\* can directly push code to the default branch, not required for pull request reviews before code is merged. Attackers compromising such a user account can directly push code to the default branch, which is likely to flow through the pipeline and be used in production systems.

* An actively used repository has at least two contributors, over 50 commits, and was updated in the last 90 days.

## Recommended Solution - Buildtime

It is recommended to restrict direct pushes to the default branch, and to require pull request approvals to ensure the code is reviewed before merged. To configure require required pull request reviews:

1. Select a repository > **Settings**.
2. Under **Branches**, select **add branch protection rule** > edit the rule that applies to the default branch.
3. Check the **Require a pull request reviews before merging** rule.
4. Select the required request approvals from the options that are displayed.

Recommended: Select the **Require review from Code Owners** rule that is displayed when executing *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-34.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.