A great way to understand Reviewpad features is to have a look at some use cases.
The following list of uses cases is based on the feedback and the questions we received from our users 🙌
If you have any other use cases in mind, please let us know at Discord, Twitter, or email 🙏
The ability to configure automatic pull request merge can greatly unblock developers that typically wait for hours, or even days, to receive a LGTM review.
🗃️ Automated Labelling
📄️ Attention set
The Attention Set defines what kind of attention a pull request needs at a certain time.
📄️ Blocking Merge
Reviewpad can be used to ensure pull requests are safely merged and follow the rules of our repository.
📄️ Check issue description
Reviewpad can be used for workflows on both issues and pull requests.
📄️ Comment on pull requests
With Reviewpad, you can automatically add comments to the pull request.
📄️ Enforce branch conventions
To maintain consistency of development and best practices of CI/CD, it is important to enforce a policy of branch naming.
📄️ Enforce conventional commits
Conventional commits is a specification for adding human and machine readable meaning to commit messages.
📄️ Manage issues in GitHub projects
Reviewpad can be used to automatically manage issues in GitHub projects.
🗃️ Reviewer Assignment
Ship/Show/Ask is a methodology to increase the pace of software teams by not having to block developers for each pull request.