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

# Code owners reviews not required before merging to the default branch

## Rule Details

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

## Impact

An actively used repository\* does not require code owners reviews before merging to the default branch. The 'Code owners' feature enables repository owners to assign responsible individuals or teams for reviewing and approving changes to critical files or directories, ensuring that proposed modifications are assessed by knowledgeable developers. This helps reduce the risk of introducing vulnerabilities into the codebase by attackers or mistakes.

* An 'actively used repository' is defined as having at least 2 contributors, over 50 commits, and having been updated in the last 90 days.

## Recommended Solution - Buildtime

Require code owners reviews before merging to the default branch:

1. Create a `CODEOWNERS` file.

   The file location must be as specified in the link below.

   1. In the `CODEOWNERS` file, list the file patterns and the GitHub usernames of the code owners responsible for reviewing and approving changes to the designated files.

      For more information refer to <https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#about-code-owners>.

\*\*Create a branch protection rule. \*\*

1. Navigate to the main page of the repository > **Settings** > click **Branches** under 'Code and automation'.
2. Select **Add branch protection rule** > Check the **Require pull request reviews before merging** section and select **Require review from Code Owners** from the dropdown.

   For more information refer to <https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule>.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.