> 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/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans/references/reference-f-pull-request-scan-configuration-settings.md).

# Reference F: Pull request scan configuration settings

The repository scan configuration controls whether pull request scanning runs and how it behaves. Configure these settings under **Settings** → **Data Sources & Integrations**.

| Setting                   | Default  | Description                                                                                                                                                                                                                                       |
| ------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Scan PR**               | Enabled  | Triggers a security scan automatically when a pull request opens or receives a new commit. When disabled, the repository produces no pull request scans and no status checks.                                                                     |
| **Fail PR on scan error** | Disabled | Fails the pull request when a scanner fails, rather than permitting the merge on an incomplete scan.                                                                                                                                              |
| **IaC scanner**           | Enabled  | Determines whether the pull request diff is evaluated for IaC misconfigurations.                                                                                                                                                                  |
| **SCA scanner**           | Enabled  | Determines whether the pull request diff is evaluated for CVE vulnerabilities, license miscompliance, and package operational risk.                                                                                                               |
| **Secrets scanner**       | Enabled  | Determines whether the pull request diff is evaluated for hardcoded credentials.                                                                                                                                                                  |
| **Exclude Path**          | Empty    | Specifies the files and directories omitted from scanning, entered as a comma-separated list of directory names and wildcard patterns without leading slashes. An excluded path is not evaluated in a pull request scan and cannot block a merge. |

> **Note:** **Git History Scan** and **Secrets Validation** apply to repository scanning. **Tagging Bot** supports code-to-cloud tracing, not merge gating. 


---

# 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/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans/references/reference-f-pull-request-scan-configuration-settings.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.