title: GitHub Branches: Case-Sensitivity Issue?
body: <p>I seem to be having an issue with a repository continually recreating branches locally because of some branches on remote. I'm on a Windows machine, so I suspect that it's a case sensitivity issue.</p>
  
  <p>Here's an example couple commands:</p>
  
  <pre><code>$ git pull
  From https://github.com/{my-repo}
   * [new branch]          Abc -&gt; origin/Abc
   * [new branch]          Def -&gt; origin/Def
  Already up to date.
  
  $ git pull -p
  From https://github.com/{my-repo}
   - [deleted]             (none)     -&gt; origin/abc
   - [deleted]             (none)     -&gt; origin/def
   * [new branch]          Abc -&gt; origin/Abc
   * [new branch]          Def -&gt; origin/Def
  Already up to date.
  </code></pre>
  
  <p>When doing a <code>git pull</code>, the branches in question are capitalized. When I do a <code>git pull -p</code> (for pruning), it first tries to delete lowercased versions of the branches, then create capitalized versions.</p>
  
  <p>The remote branches are capitalized (<code>origin/Abc</code> and <code>origin/Def</code>).</p>
  
  <p>I have tried to temporarily change my Git config such that <code>ignorecase=false</code> (it is currently <code>ignorecase=true</code>). But I noticed no change in behavior. I'm guessing there's something local on my end that's currently holding onto those lowercased branches. But <code>git branch</code> does not show any version of these branches locally.</p>
  
  <p>Short of completely obliterating the repository (a fresh <code>git clone</code> in a separate folder does not pull these phantom branches when trying pulls/fetches), is there anything I can do?</p>