title: Git remote head refers to feature branch instead of master
body: <p>Prior warning, I'm a bit of a Git newbie, so sorry if some of this is in distinctly non-tech speak (or I just use the wrong terminology).</p>
  
  <p>Last week I noticed a bit of an oddity on my company's Git repo, it appears that the remote HEAD has been moved from pointing at master to pointing at a feature branch instead.</p>
  
  <p>So, it used to be </p>
  
  <pre><code>remotes/origin/HEAD -&gt; origin/master
  remotes/origin/featureBranch1
  remotes/origin/featureBranch2
  remotes/origin/master
  </code></pre>
  
  <p>and is now</p>
  
  <pre><code>remotes/origin/HEAD -&gt; featureBranch1
  remotes/origin/featureBranch1
  remotes/origin/featureBranch2
  remotes/origin/master
  </code></pre>
  
  <p>I cloned the repo into anew, and sure enough, the default branch that was cloned was <code>featureBranch1</code>, not <code>master</code>.</p>
  
  <p>The feature branches on this project generally have a lifetime of a week or two, and in the next few days, <code>featureBranch1</code> is going to be merged into <code>master</code> and deleted.</p>
  
  <p>Being a Git newbie, I'm not entire sure what the effects of the remote HEAD pointing to that branch will be, if any, so what I'd like to know is is this an issue, and if so, how much of one?</p>
  
  <p>Will the feature branch merge and delete ok? Will this cause issues with the repo if the remote HEAD branch is deleted? Will it automatically revert to <code>master</code>? Will we all be given a day off because no one can do any dev work?</p>
  
  <p>We're using Git version 2.9.3.windows.2.</p>
  
  <p>(Note: I'm also vaguely interested in how this happened, seeing as developers don't generally have permissions to change anything on the server, but that's less important at the moment than any possible knock on effects)</p>