24 ms·
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 w
by weebull 3y ago
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)
Well, that was enough to make me think twice.
- bvrmn 3y agoThere is a "Clone with commit-msg hook" copy-pastable url or `git review` setups hook automatically.
- verall 3y agoIt 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.
- misnome 3y agoPresumably if you use Gerrit a lot you can just add it to your git-template and it will be automatic (I use this for the pre-commit hook script)