PullApprove 5
CODEREVIEW.toml
Concepts
Self-Hosted
Log in

Large Scale Change

Large scale changes (LSCs) are systematic modifications that touch many files across your repository, typically for infrastructure improvements, refactoring, or technical debt cleanup.

When a PR is detected as a large scale change (currently triggered by a diff so large that the platform API returns an HTTP 406), PullApprove can't tell which files changed, so it can't match them to scopes. Instead, the whole PR is reviewed as a single scope named Large-scale change, built from this config. It shows up in the status comment, next steps, and the PullApprove UI like any other scope.

These changes typically require review from more senior team members who can assess the overall impact and approach.

[large_scale_change]
reviewers = ["admin1", "admin2", "admin3"]
alternates = ["migrator1"]
require = 2
request = 2
labels = ["large-change"]

Properties:

  • reviewers - List of users who can review large scale changes. Supports aliases and teams.
  • alternates - Users who can approve a large scale change but won't be requested automatically. See alternates.
  • require - Number of approvals required (default: 1).
  • request - How many reviewers to request automatically (default: 0, no requests). Works the same as a scope's request.
  • labels - Labels to automatically apply when detected. These replace any scope labels PullApprove added, since scopes aren't matched for a large scale change.

If a PR turns out to be a large scale change and no reviewers or alternates are configured, PullApprove reports a configuration error on that PR.