Page History

...

The Developer may request feedback by adding additional reviewers via the Gerrit web GUI or alternatively by specifying details on the command line when pushing changes to Gerrit. Component owners/reviewers/approvers, defined as specific groups in the external LDAP system, will be added by default.

Note: Optionally, additional reviewers can be added using ``%r=user@mail.com`` syntax during the push operation on the command line.

...

Only authorised users, i.e. component owners, component approvers or admins, can submit the change allowing Gerrit to merge it to the target branch as soon as possible. A change can be submitted, having satisfied the approval conditions described earlier, by clicking the 'Submit Patch Set n' button within the Gerrit UI. When a change has been Submitted, it is automatically merged to the target branch by Gerrit.

9. Abandon change

A concious decision is made Depending on the review outcome, it might be decided to abandon the change based on the review outcome. The component owner or an authorised user may abandon the change by clicking the "Abandon Change" button. The abandoned changes are not removed from the Git repository Gerrit database and could can be restored at a later stage.

10. Submitted, Merge Pending

The If a change depends on another change that is still in review. In this case the change , it will enter this state. It will be merged automatically by Gerrit once all its dependencies are submitted and merged.

...

Note: The 'change number' referenced above is different to underlying Git commit ID.
Note: Patch-sets are numbered (starting from 1) for each review, and incremented whenever a change is amended with another Git commit.
Note: FETCH_HEAD is a Git symbolic reference and shorthand for the head of the last branch fetched and is valid only immediately after the fetch operation.

12. When a change has been Submitted, it is automatically merged to the target branch by Gerrit.13. Gerrit merge failure as a result of a conflict

...