Announcing €1M Funding to Streamline Code Reviews with Artificial Intelligence
Introducing Reviewpad Summarize - an AI feature that summarizes changes on GitHub Pull Requests (and Issues), making code review more efficient and enjoyable
Optimize your code review process with Reviewpad’s auto-merge feature. Focus on other vital things rather than waiting for merge requests to be accepted.
The Reviewpad team has decided to stop updating the Reviewpad and actively recommends that current users migrate to the Reviewpad GitHub App.
Streamline your code reviews with Reviewpad. Our advanced algorithm suggests the best reviewers for your pull requests, making your workflow faster and more efficient.
Exciting News! We're proud to announce that Freddy Mallet, former Co-founder of SonarSource, has joined our team as Chief Product Officer!
Pull Requests have become the backbone of the DevOps movement: the faster, the safer, the better. But the code review step, this systematic and synchronized communication task between humans, inherited from ancient times, slows down the overall development lifecycle for an illusion of safety. It’s time to introduce the Fluid Pull Requests paradigm.
This guide shows how you can set up GitHub workflow templates to automate common GitHub pull requests workflows!
For the old guard software developers, trunk-based development is the way to go. For younger developers, used to GitHub pull requests, it is unlikely that they know what trunk-based means. This article shows how we use automation to combine TBD principles with pull requests and get the best of both worlds.
Humans tend to overcomplicate, and devs are no exception (on the contrary!). We were paying 99$ a month for a Readme subscription and feeling a lot of friction. Along comes an intern looking for project ideas, and we couldn't be happier.
Explain to your grandparents what GitHub Actions are in 5 minutes. This is a topic that is getting thrown around more and more with the rise of Pull Request Automation, we have found out that even software engineers don’t fully understand what they are, but here’s a quick fix.
We are looking to build a true repository of code review tips for all devs everywhere. So now it’s up to you guys to help us make it all it can be!
The time has come to remind everyone of the fundamental benefits of making whatever knowledge you’ve acquired available to your colleagues.
If you are leading a team, and you need your code reviews to be better, more effective, and a more perfect tool for team-building, what can you actually do?
Reviewers should find their footing and engage with reviews in the way that works best for them. We do believe, however, that there are principles that are key.
João is a friend of Reviewpad and he asked us how we started the project. Here’s the story in his words.
What do you expect a code review to go? Managing these expectations can be daunting. Here are some thoughts on how to manage this.
The confusion between Code Reviews and Pull Requests is very common. So what are pull requests? And why are they called that way?
Not all devs need a checklist for code reviews, nor one will suit all code reviews. With that in mind, here's a suggestion of checks that should always be made.
It's hard to agree exactly how long the ideal code review is. There are too many variables but, hopefully, there are some guidelines we can follow.
Step back and take a good look at code reviews: the basics, why it matters, and how it’s become a cornerstone of software development
Let us tell you how collaborating on a book usually happens, and you will understand how Git works.
A comprehensive overview of how we ensure the synchronization between Reviewpad and code hosts is flawless.
The right branching model will improve any team's collaboration, quality, and speed. The wrong model will do exactly the opposite. These are the 3 most used branching models.
Reviewpad's key design decisions, architecture, and some lessons learned while coliving with GitHub, GitLab, and Bitbucket.
Here is a perfected analogy to perfectly explain the Code Review process to non-developers in less than 5 minutes.
Code reviews are (still) complex. We started this series in a previous article and we are back to complete it with six more recommendations.
Code reviews are one of the best ways to ensure code quality. A recent survey has found that 36% of the companies that do code reviews (84% of the total) think it is the best way to improve code quality. Too often, however, they are understood as an individual task, instead of a team effort. This article will delve into the status quo of code reviews and where the roadblocks lie.
Code reviews require good time management, high emotional intelligence, knowledge of the codebase, and technical expertise. We share six tips to elevate the quality of code reviews.
Interns are adapting to the job market in a series of unprecedented circumstances. We sat down with our own interns to see how they are dealing with this new experience.
Nowadays, GitHub is the home of open source. The adoption of pull requests has been incredible. But what happens when we move away from open source? What is the most widely used code review tool?
Here are some best practices that we find work well in practice to measure your team's code reviews.
What machines can do for us, and why they will never completely replace human interactions in code reviews.
This article is part of a series on how senior developers think about code reviews and their approach in their teams.
Pull requests are not the only (or even the best) way to do code reviews. Asynchronous high-quality reviews can be done without PRs with the right tooling.
One of the major roadblocks for quality code reviews is how complexity can quickly get overwhelming. Without solving this issue we can’t unlock the full benefits of code reviews.
The cost of going back and forth during code reviews and between code reviews and other tasks is standing between us and excellence.
An overview of the most common concerns and a vision to the future of code reviews. Spoiler: it’s not a fancy AI tool that replaces developers.
We present and analyze the ≈ 2.6M merged pull requests from January to March of 2020, on GitHub.
In the 2nd part of this series, we'll deep dive into the merged pull requests from 283 034 starred public projects.
We are continuously testing semantic code reviews with Github’s Pull Requests from our internal projects and public repositories. In Part I we'll look into the duration of pull requests.
Copyright © 2023 Reviewpad