-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewriting repo history to use Git LFS #12
Comments
I ran the following commands: # https://rtyley.github.io/bfg-repo-cleaner/
# https://confluence.atlassian.com/bitbucket/use-bfg-to-migrate-a-repo-to-git-lfs-834233484.html
# Outside of original repository
git clone --mirror git@github.com:hetio/hetionet.git hetionet-bfg.git
java -jar ~/Downloads/bfg-1.13.0.jar \
--convert-to-git-lfs "*.{bz2,gz,xz,zip}" \
hetionet-bfg.git
cd hetionet-bfg.git
git reflog expire --expire=now --all && git gc --prune=now --aggressive
git lfs fetch --all
git lfs push --all origin master
# From within original repository
git checkout -b master-bfg
git remote add bfg /home/dhimmel/Desktop/hetionet-bfg.git
git fetch bfg
git reset --hard bfg/master
git push --set-upstream origin master-bfg The bfg command produced the following output:
When running I kept getting
I added So this repo now has a |
The |
I have decided to undo this, but keep the BFG rewrite around in a
So I'm going back! |
In 23f6117, we began using LFS to store large files. While this commit uses LFS, the history still contains non-LFS files. Therefore, we can use the BFG Repo Cleaner to create a history where all files use LFS. We will keep the pre-LFS history available in branches, but not
master
.The text was updated successfully, but these errors were encountered: