Project113

Change Request Policies

CR policies automate merge requirements and reviewer assignments based on branch patterns, title patterns, and other conditions.

CR Policy Rules

Each CR policy can configure:

  • Merge strategy — Enforce merge, squash, or rebase.
  • Minimum approvals — Require a minimum number of approving reviews.
  • Require CI to pass — Block merging until CI succeeds.
  • Require all threads resolved — Block merging until all discussions are resolved.
  • Allow force merge — Permit merging even when requirements are not met.
  • Auto-delete source branch — Remove the source branch after merge.
  • Auto-merge — Automatically merge when all conditions are met.

Pattern Matching

Policies match change requests using SQL LIKE patterns (% matches any sequence, _ matches exactly one character):

  • Merge ref patterns — Target branch (e.g., master, release/%).
  • Merging ref patterns — Source branch (e.g., feature/%, bugfix/%).
  • Title patterns — The CR title (e.g., %hotfix%).

Reviewer Policies

Reviewer policies automatically assign reviewers when CRs are created. They match using the same patterns and can specify whether a reviewer's approval is required.

Priority

When multiple policies match, the highest priority policy wins. This lets you create general rules with specific overrides.

Subjects

Policies can be scoped to specific accounts, members, groups, roles, or audiences for different rule sets per team.

See the Permissions Reference for all change request permissions and configurable settings.