One way we use Gerrit is to hook the CI (Jenkins) up to it and make sure that the repo as patched passes a number of tests (static analyses, compilation with fu

One way we use Gerrit is to hook the CI (Jenkins) up to it and make sure that the repo as patched passes a number of tests (static analyses, compilation with full warnings, unit and regression tests, build on multiple platforms, etc). If it doesn't pass the CI tests, Gerrit won't allow it to be merged. We let the machine do the dirty work, so we can focus on the semantics of a change.