title: How to prevent Gitlab from creating extra merge commit on branch merge
body: <p>I use GitLab in my project. I'm exploring Merge Requests feature. </p>
  
  <ol>
  <li>I created a <code>topic_branch</code> from <code>master</code>.</li>
  <li>Made a bunch of commits on <code>topic_branch</code>. </li>
  <li>Pushed <code>topic_branch</code> to remote. </li>
  <li>Created a merge request on <code>master</code> to pull changes from <code>topic_branch</code>. </li>
  <li>On accept merge in Gitlab, <code>master</code> pulled all the commits and also created a merge commit which is horrible to see duplication of code. </li>
  </ol>
  
  <p>I should have created a squash of commits on branch and then created merge request. But still <code>master</code> would have two new commits, one from the branch and another one would be merge commit. I'm assuming, if I do this from command line i.e,</p>
  
  <ol>
  <li>checkout <code>master</code></li>
  <li>merge <code>topic_branch</code> into <code>master</code></li>
  <li>commit / push <code>master</code>
  In this case, there would be only 1 commit on <code>master</code>.</li>
  </ol>
  
  <p>How to achieve this from GitLab ?</p>