title: How to STOP using Git LFS in a repository
body: <p>I recently setup Git LFS in our primary repo and have had nothing be problems with it so far. On top of that, we only set it up to stop a ballooning effect on our separate build repo (which is going away in favor of a new process).</p>
  
  <p>The primary problem at this point (among other issues) is that we are trying to start pushing builds from the primary repo to an Acquia repo (which is required for Acquia deployments). Acquia does not support Git LFS and I don't have time to fight with them on that nor argue the merits of the host solution (this is what we have and have had for awhile) with anyone that can affect such change.</p>
  
  <p>I would like to just remove it and it seems that I have only partially removed it. It seems that online documentation for this is scant at best.</p>
  
  <p>Here is what I have done:</p>
  
  <ol>
  <li>Run <code>git lfs untrack *</code></li>
  <li>Then <code>git lfs uninstall</code></li>
  <li>Finally I reverted my <code>.gitattributes</code> file to it's prior state</li>
  </ol>
  
  <p>I pushed that up and locally it seems to have eliminated a lot of object tracking (by merit of me going into <code>.git/lfs</code> and rooting through the folder structure). Running <code>git lfs ls-files</code> does not show me anything at all.</p>
  
  <p>However, when I pull it down on a separate clone it shows more than a thousand files still tracked by it when I try to push to Acquia and it fails because Acquia does not support it. Charming, I know.</p>
  
  <p>I suspect that removing it entirely would eliminate the <code>.git/lfs</code> directory or at least the contents of it. If nothing else it should eliminate the tracking in the clones the pull down the changes. It does not.</p>
  
  <p>I think that I may be missing a step to change the file pointers back to what they were, but I am unsure of what else I can safely do. I want to keep the files it tracked. My repo is hosted on Bitbucket cloud.</p>