Github showing (develop) branch behind master by x commits : <p>I have been searching for the answer to this problem but have not found a solution or explanation. </p>

<p>We just switched to Github for our repo and are still trying to find the best way to use it in a team environment. Our current workflow is like this:</p>

<p>We have two branches <code>develop</code> and <code>master</code></p>

<ol>
<li><p>Developer clones <code>develop</code> branch onto their machine and creates a branch using: <code>git clone https://github.com/username/repo</code></p></li>
<li><p>Developer creates the branch for the feature they are working on using: <code>git checkout -b branchname</code></p></li>
<li><p>Developer finishes branch and pushes to Github using: <code>git pull</code> then <code>git push -u origin branchname</code></p></li>
<li><p>Developer creates pull request and the lead developer will first merge the just pushed branch into <code>develop</code> and then merges <code>develop</code> into <code>master</code></p></li>
</ol>

<p>Now the thing that concerns me and makes me wonder if we are doing something wrong is that when we look at the <code>master</code> branch in Github everything appears fine, but when we view the <code>develop</code> branch inside of Github it says <code>This branch is x commits behind master</code>. Everytime we merge a pull request the number <code>x</code> goes up. Github gives the option on the same line to "Compare" or create a "Pull Request" but when I click either of those options it shows the branches are identical.</p>

<p>I have tried to fixed this previously by merging <code>master</code> into <code>develop</code> which does make the branches both even but as soon as a pull request is merged we get the same problem again. </p>

<p>When we first switched to Github I don't ever recall seeing that <code>develop</code> was behind <code>master</code> but our workflow has not changed. I don't know if maybe I just didn't notice it before or not.</p>

<p>If I compare the commits between the branches I can see that in fact <code>develop</code> is behind <code>master</code> by <code>x</code> number of commits. The commits that are showing up are the ones where I merge <code>develop</code> into <code>master</code>. What I am wondering is if it is something to be concerned about? The branches are identical besides the number of commits. Are we not using Git/Github correctly and is that why we are getting this, or is this a normal thing?</p>
