Concurrent code reviews
When teams start using Code Review, the number of open changes starts to increase and the chances of having more than one change running concurrently get higher. Because of the intrinsic latency introduced by the review workflow, it is likely that more changes will need to be based on other code that belongs to other non-approved changes.
Changes dependency tracking
Gerrit understands the branching structure of dependent changes and creates an acyclic dependency graph between them, where every change points to its successors and vice versa. The following diagram shows an example of Gerrit dependent changes:
Gerrit also detects ...