Gerrit always rebase before submit patchset to avoid a merge commit
===

I found that when clicking "Submit Patch Set" in the **Gerrit** web interface, it'll either simply add a commit to that branch, or create a merge commit if another commit was submitted just before.

Example that creates 2 commit: The actual commit and a merge commit:

 0. User submits patchset A depending on commit O
 0. User submits patchset B depending on commit O
 0. Submit Patch Set A
 0. Submit Patch Set B --> Creates merge commit between O -> A and O -> B

There is a "Rebase Change" button which is great but it means that to submit a patch set everyone should always do:

 0. Click **Rebase Change**
 0. Click **Submit Change Set**

The only reason I see a merge commit useful is to keep dates of the commits (but I do understand why it is required without a rebase).

Isn't there an **automatic rebase** or at least a check to avoid creating an undesired merge commit?