action VS reviewpad

- He implemented a couple of automation tools - gitStream and ReviewPad - that auto assign PRs, add estimated review times, automate some easy code checks, etc.

3) Use an automation/merging tool, probably gitStream or ReviewPad, that mitigates common hurdles/bottlenecks in the review process around PRs.

At the moment, you can enforce pull request workflows to deal with this separation of concerns using the GitHub Reviewpad Action.

This is why we are seeing increased adoption of tools such as ReviewPad that automate the review process and instill confidence in code changes. Reducing the need for manual intervention and overall reducing the time it takes for customers to see value in the applications you are developing.

By the way, PRs can be also automated. At work we are using Reviewpad for that: https://reviewpad.com/ But also we are using some custom GHA workflows as well.

Depending on the code submitted, we could imagine that developers are free to merge if they consider there’s no risk and need to assign a reviewer, and they should ask for two reviewers if the code changes are critical. That’s the idea promoted by the Ship Show Ask model. With solutions like Reviewpad, you can implement your assignment and merge rules depending on the content of the review.

reviewpad.yml that runs Reviewpad;