-
Notifications
You must be signed in to change notification settings - Fork 19
Migrate to Git LFS
NOTE: we are not moving to Git LFS just yet so don't follow any of these instructions.
Git Large File Storage (Git LFS) allows repositories to remain a manageable size while still providing versioning for large files. Details can be found at https://git-lfs.github.com
Skip to Begin Using New History if you just want instructions for migrating your local repository to the new repository history.
##Background Several large files have been added to this repository at different points of it's history causing the repository to quickly grow in size. With the introduction of Git LFS we are taking steps to clean up the repository history and make things more efficient.
##Begin Using New History Here are instructions of what you (the developer) need to do on your end if you have cloned an old copy of this repository.
Want to do things the easy way? Delete your local code base and re-clone this repository! Then you can skip to step 2.
- Rebase any branches you created off of the old repository history.
- Now perform a force push to your fork on github.
- You're done!
Now for an actual example of what most developers will need to do:
todo place example here
That's it! You're all done and ready to go!
##Missing the Big Files?
- Install Git LFS and follow the commands to initialize it.
- Then follow the instructions in http://manuel.manuelles.nl/blog/2011/12/22/shrinking-your-git-repository/.
Normally you would just need to run git lfs pull
to download the large files, but because you didn't have this tool install before you cloned this repository you have to do things the hard way (but just the first time).