I've found this article before and have to say, it put me off going any further when I got to...
> # tl;dr
>
> Here’s how getting code reviewed and submitted with Gerrit is different from doing the same with GitHub:
>
> - You need to add a commit-msg hook script when you clone a repo for the first time using a snippet you can find e.g. here (link)
It adds a 'Change-Id: <hash>' line to commits which let's you track a logical "change" across iterations, rebases, and branches. It's sort of the whole way Gerrit works.
> # tl;dr > > Here’s how getting code reviewed and submitted with Gerrit is different from doing the same with GitHub: > > - You need to add a commit-msg hook script when you clone a repo for the first time using a snippet you can find e.g. here (link)
Well, that was enough to make me think twice.