---
title: "Write a repository review configuration | Proofline Help"
description: "Start from the root .proofline.yaml or .proofline.yml in the repository whose reviews you want to change. Keep one of those files. Each example below is a complete file; merge the relevant keys into your existing document."
url: https://proofline.sh/help/write-repository-review-configuration/
---

[Help center](/help/)

# Write a repository review configuration

Start from the root `.proofline.yaml` or `.proofline.yml` in the repository whose reviews you want to change. Keep one of those files. Each example below is a complete file; merge the relevant keys into your existing document.

[![Draft YAML in the repository configuration validation modal.](/help-images/configuration-draft-light.png)](/help-images/configuration-draft-light.png)

Validate a draft before committing .proofline.yaml. Validation saves nothing. Fictional demo workspace.

## Choose which changes receive a review

-   [Review pull requests into release branches](/help/yaml-review-release-targets/)
-   [Select pull requests by their GitHub labels](/help/yaml-select-labels/)
-   [Choose between one directory level and its descendants](/help/yaml-match-path-depth/)
-   [Return one path filter to console control](/help/yaml-return-path-filter-to-console/)
-   [Include generated outputs in a repository’s review scope](/help/yaml-include-generated-outputs/)
-   [Repair a review filter with a missing value](/help/yaml-repair-empty-scope-values/)

## Write review instructions

-   [Fit repository guidance within the combined limit](/help/yaml-shorten-combined-guidance/)
-   [Attach a review instruction to database migrations](/help/yaml-rules-for-migrations/)
-   [Separate review rules that share a key](/help/yaml-fix-duplicate-rule-key/)
-   [Set review strictness in a version 2 file](/help/yaml-migrate-file-strictness/)

## Declare architecture boundaries

-   [Assign an overlapping file to one architecture layer](/help/yaml-separate-overlapping-layers/)
-   [Declare a one-way dependency between layers](/help/yaml-declare-one-way-imports/)
-   [Declare a layer with no dependencies on other layers](/help/yaml-isolate-leaf-layer/)
-   [Name an external package in an architecture rule](/help/yaml-name-package-imports/)
-   [Repair architecture rules after a layer rename](/help/yaml-rename-layer-references/)

## Repair YAML structure

-   [Repair a duplicate configuration key](/help/yaml-merge-duplicate-keys/)
-   [Replace YAML anchors and aliases with explicit values](/help/yaml-flatten-yaml-aliases/)
-   [Combine a multi-document configuration](/help/yaml-combine-yaml-documents/)
-   [Replace tagged YAML with ordinary scalars](/help/yaml-remove-yaml-tags/)

## Validate and commit the change

Open the repository’s **Settings → Config file**, choose **Validate a draft config file**, paste the complete file and select **Validate draft**. Commit the validated file through GitHub. A pull request that edits the file is reviewed using the configuration at its merge base. Later reviews can use the changes after they merge.

For dependencies between separate repositories, [record their roles in a repository cluster](/help/repository-clusters/). Architecture layer paths belong to a single repository.

## Related guides

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