Why merged pull request in GitHub creates duplicate commit?
<p>At my company we ask developers to squash commits on <code>feature</code> branches before merging into <code>develop</code>. Once squashed, the developer pushes to GitHub and logs into GitHub to create a pull request.</p>

<p>When the pull request is merged, we end up seeing <em>two</em> commits in the history of the <code>develop</code> branch:</p>

<ol>
<li>A commit saying "merged pull request"</li>
<li>The single, squashed commit from the <code>feature</code> branch</li>
</ol>

<p>Why does this happen? And how can we avoid it? I've read a similar <a href="https://stackoverflow.com/questions/16358418/how-to-avoid-merge-commit-hell-on-github-bitbucket">Q&amp;A about avoiding "merge commit hell"</a> but my goal is to use the GitHub UI to create, track, and discuss pull requests.</p>