Code review workflows

The last three posts on code review workflows show that there's more than one way to do a code review, and that the approach you take will depend upon what you want to achieve with your reviews and the type of team you're working with. In this post, we'll cover how Upsource aims to make your workflow, whatever it looks like, simpler by automating as much of it as possible. We'll show the types

In the last two posts we talked a bit about how effective those approaches are for the author to learn and improve, because those two approaches focus on getting the code correct. The Design Evolution approach additionally mentions the value of the whole team seeing the evolution of the code. This third approach for code reviews puts learning at the centre of the process — the purpose is not to

In the last post we covered a review process where the code review is performed after all the code is written with the goal of approving the suggested changes. If getting the design right is important to your team, then a collaborative and iterative approach may be appropriate — the code can be checked frequently while it's being built, so design feedback comes at the right time. In this exa

We've talked a lot about what to look for in a Code Review, but we haven't covered the process at all. There are many different reasons to perform code reviews in your team or organisation, and the process you choose should be driven by what you're trying to achieve with the reviews. The first example we're going to explore is Code Review as a Gateway. In this process, a developer picks up or i