How Reviewpad Protect Works

Reviewpad Protect is the most advanced mechanism to protect pull request merges. Apply rules to your repositories to block merges that break your code reviews policies, code quality, compliance and security standards.
All the magic with a GitHub App and a single file in your repository.

Reviewpad Protect Sneak Peek

Setup Reviewpad Protect to Block Merges's icon

Setup Reviewpad Protect to Block Merges

Configure branch protection for Reviewpad to block the merge button.
Onboard New Developers Faster's icon

Onboard New Developers Faster

Require approval of senior developers from the author's team.
Extra Security Made Easy's icon

Extra Security Made Easy

Require approvals in sequence based on the author and sensitivity of the changes.
Code Freezes Made Simple's icon

Code Freezes Made Simple

Programmatically block merges in code freezes.
Best Practices on Autopilot's icon

Best Practices on Autopilot

Enforce git conventions such as commit message format, branch naming and more.
Enforce Checklist Completion's icon

Enforce Checklist Completion

Require every task to be checked off.
Require Green CI Checks's icon

Require Green CI Checks

Declare which CI checks must be green based on changes made in the pull request.
Centralized Merge Protection Rules's icon

Centralized Merge Protection Rules

Configure once - apply everywhere! Manage protection rules across all repositories in a single place.
Setup Reviewpad Protect to Block Merges
Setup a branch protection rule in your GitHub repository for Reviewpad to block the merge button.
Onboard New Developers Faster
Reviewpad Protect is new way to onboard new developers faster and to balance the code review workloads. Require approval of senior developers from the author's team. Reuse the existing GitHub teams or define them in Reviewpad to customize their permissions to your needs.
Extra Security Made Easy
Combine multiple criteria such as PR author, code changes and even timing of the pull requests for an advanced merge approval workflow. Automatically block merges from developers that are not part of the team or to require extra approvals for sensitive code changes. Ensure bots and automated tools are not merging code without human approval.
Code Freezes Made Simple
Programmatically block merges in code freezes. With Reviewpad, you can automatically use labels or comments in the pull requests to block merges. When you setup Reviewpad branch protection rule, require branches to be up to date before merging so that a change in the configuration is automatically applied to all pull requests.
Best Practices on Autopilot
Ensure that pull requests strictly adhere to the specified requirements that maintain a well-organized and consistent codebase for good traceability of issues. Available rules include conventional commit messages, git history, branch names, titles and descriptions.
Enforce Checklist Completion
Customize dynamic pull request checklists and let Reviewpad enforce that every item is completed before the merge.
Require Green CI Checks
Not all pull requests require the same level of scrutiny when it comes to CI checks. For example, running unit tests and integrations tests is a waste of resources of pull requests that only change documentation. With Reviewpad, you can declare which CI checks must be green based on changes made in the pull request.
Centralized Merge Protection Rules
Configure once - apply everywhere! Reviewpad Protect allows you to manage protection rules across all repositories by extending central configurations.

Frequently Asked Questions

What is the difference between Reviewpad and GitHub Actions?

Why is GitHub CODEOWNERS not enough?

Why are native GitHub Branch Protection Rules not enough?

How complementary is Reviewpad to the CI system?

Why not developing my own GitHub Action?

Disrupting software developers collaboration

Copyright © 2023 Reviewpad