DEV Community

What Makes Reviewpad the Best Pull Request Management System

Ankur Tyagi on April 04, 2023

"Have you ever spent hours reviewing someone else's code only to feel like you're making no progress?" When I first started out as a developer, ...

Read full post

Anthony Fung • Apr 4 '23

Seems like an interesting tool.

I do wonder if using automated PR tooling increases the risk of knowledge silo-ing though. If there's no need for a developer to look through code, they probably wouldn't. If the person who wrote the code becomes ill or leaves the company, there's a chance that nobody else has even seen that code before.

Another question I may have missed the answer for is whether the code being reviewed stays private; I assume the code is sent to Reviewpad's servers for processing?

Marcelo Sousa • Apr 5 '23

Excellent questions!

We typically recommend that you use a strategy like Ship / Show / Ask with Reviewpad. This way each pull request is automatically labelled if it was reviewed or not. A practice that we advise is to take like 20 minutes of mob review a week to go over the PRs that were shipped without review. This way you avoid silos. You can see this practice our pull requests
We do not store any code from private repositories. In fact, we only even analyze the code if you use built-ins like hasCodePattern. Otherwise, there is no need to even check the code.

Anthony Fung • Apr 5 '23

Hi Marcelo

Thanks for the insights! hasCodePattern certainly looks handy for narrowing down what gets analyzed - even if it's only to cut down processing time.

Adriano Martins • Apr 4 '23

Awesome article on Reviewpad 💪 Usefull and well-written, and it's great to hear about real-world examples of how Reviewpad has improved workflows and team collaboration. Thanks for sharing your insights @tyaga001!