We can now experiment with a real-life review cycle by putting into practice the workflow already described. The only action we will not explore at this stage is the CI Build integration, which will be covered later in a dedicated Appendix.
The first action that triggers a Code Review is the initial commit pushed to Gerrit. Gerrit introduces a new Git reference namespace completely dedicated to the Code Review prefixed by refs/for
before the branch path (for example, for pushing a change for review on the master branch we need to use refs/for/master
).
We can then create our first change on the hello-project
we cloned in our initial sandbox.
$ git clone \ ssh://[email protected]:29418/hello-project […] Receiving objects: 100% (2/2), done.