Project113

Change Request Policies

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

CR Policy Rules

Each CR policy can define:

  • Merge strategy — Enforce a specific merge strategy for matching CRs.
  • Minimum approvals — Require a minimum number of approving reviews.
  • Require CI to pass — Block merging until CI pipelines succeed.
  • 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 merging.
  • 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 — The target branch (e.g., master, release/%).
  • Merging ref patterns — The source branch (e.g., feature/%, bugfix/%).
  • Title patterns — The CR title (e.g., %hotfix%).

Reviewer Policies

Reviewer policies automatically assign reviewers to change requests when they are created or updated. They can match based on the same patterns as CR policies and can specify whether a reviewer's approval is required.

Priority

When multiple policies match a change request, the one with the highest priority wins. This allows you to create fallback rules — for example, a general policy for all branches with a higher-priority override for master.

Policy Subjects

Policies can be scoped to specific accounts, members, groups, roles, or audiences. This lets you create different rules for different teams or permission levels.