You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I've got a couple of git repos that have `git lfs` turned on and I'd like to move them to a new project in Bitbucket. However bitbucket is telling me that I cann't move them because of `git lfs` support, why is that and what can I do about it.
BTW, I'm not really sure that these repos really need `git lfs` support as the files in lfs are only a couple of MB each.
Hi, @Matt Schuckmann!
Thank you for reaching out to Atlassian Community!
Currently, the transfer of repositories with Git LFS files is disabled, this is a limitation for Git LFS. However, we have a workaround for that:
Instead of transferring the repo, you can clone the repo to your local machine, then create a repo in Bitbucket, and push to that.
When you do this, all files and the Git history will be available in the new repo, but the metadata for such things as issues, pull requests won't be copied over. Furthermore, you'll have to set up users and access permissions for the new repo.
Clone the Git LFS repo to your local machine as usual:
Fetch the Git LFS history:
git lfs fetch --all origin
Create a new repo in Bitbucket.
Add a remote locally that points to the new repo:
git remote add new-origin <URL to new repo>
Now push to the new repo:
git push -u new-origin --all
This pushes the repo and its refs for the first time.
Push Git LFS data to the new repo:
git lfs push --all new-origin
Finally, update the remotes for the new repo:
git remote set-url origin <URL to new repo>
git remote set-url --push origin <URL to new repo>
Please let me know how it goes and feel free to share any additional questions or concerns regarding this case.
Kind regards,
Caroline
And if you have multiple branches, don't forget to include them when you clone!
Add `--mirror`
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.