title: Why merge commits for git flow release finish instead of fast-forward HEAD update?
body: <p>Does git flow avoid fast forward merges for better reporting?</p>
  
  <p>While testing git flow I see not only the commits from my release branch on master &amp; develop but also merge commits.  I thought I'd only see release branch commits and then a fast-forward as git adjusted master &amp; develop to point to the new commits.</p>
  
  <p>As a very simple case, I expected no merge commit requirement since no other changes appeared between the time of release branch start and finish.</p>
  
  <p><strong>What drives the merge commit requirement or did I miss something?</strong></p>
  
  <p>Thanks</p>
  
  <p>Peter</p>
  
  <p><strong>Scenario: Release Stabilization</strong></p>
  
  <ol>
  <li>Create release branch (<strong>git flow release start 100.0.0 develop</strong>)</li>
  <li>Push for collaboration (<strong>git flow release publish 100.0.0</strong>) (it's just me, so I'm collaborating with myself)</li>
  <li>make and commit 1 change on release/100.0.0</li>
  <li>Finish release (<strong>git flow release finish</strong>)</li>
  </ol>
  
  <p><strong>RESULT</strong></p>
  
  <pre><code>local develop +3 commits to remote
    HEAD    merge tag to develop e191707
    HEAD -1 e0040cb merge from release branch
    HEAD -2 e7cdc02 release branch change
  
  local develop +3 commits to remote
    HEAD    merge tag to develop e191707
    HEAD -1 e0040cb merge from release branch
    HEAD -2 e7cdc02 release branch change
  
  local master + 2 commit to remote
    HEAD e0040cb merge commit 
    HEAD -1 e7cdc02 stabilization change 
  </code></pre>