Awesome Reviewers

Verification · Intent and spec conformance · Merge readiness

Merge rules

Required checks, approvals and labels as code.

How to build it

  1. Write required checks, approvals and labels in a repository config file.
  2. Set branch protection so the same requirements apply on the platform.
  3. Enable auto-merge only for pull requests that meet every rule.

Signals in a repository

  • .kodiak.toml or a merge queue config file at the repository root.
  • Branch protection rules that list required status checks.
  • Pull requests that merge automatically after the last required approval.

In practice

No scanned repository runs a tool for this check. The steps above are the only guidance.