---
title: "Resolve differences between YAML and console review scope | Proofline Help"
description: "Open the repository's Settings → Config file and compare the review scope keys it sets with Settings → Review scope to see which filters a pull request must pass."
url: https://proofline.sh/help/resolve-review-scope-conflicts/
---

[Help center](/help/)

# Resolve differences between YAML and console review scope

Open the repository's Settings → Config file and compare the review scope keys it sets with Settings → Review scope to see which filters a pull request must pass.

## Check how review scope keys combine with console settings

A file can set six keys under `reviews`. Beside each key the file sets, **Review scope** on the page shows how the key combines with the repository's **Settings → Review scope**:

| Label on the page | Keys | What it means |
| --- | --- | --- |
| Replaces the console setting | `paths_include`, `paths_exclude`, `exclude_generated` | Reviews use the file's value in place of the console's. An empty list clears the console's path filter. |
| Adds a restriction | `base_branches`, `labels_include`, `labels_exclude` | A pull request must pass the console's filter and the file's. The file can narrow the console's branch and label filters, and cannot widen or clear them. |
| Adds no restriction | The same branch and label keys, set to an empty list | The console's filter applies unchanged. |

To review more branches or labels than the console's filter admits, change **Settings → Review scope**.

## Related guides

-   [Review repository configuration](/help/repository-configuration/)
