-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Repo mirroring doesn't mirror LFS data. #849
Comments
This is the same reason with #732. Let's close this and discuss there. |
I'm afraid I have to disagree: #732 is not related. Gitea cannot currently retrieve LFS objects from another server. This would basically require adding a complete LFS client on top of the current implementation. @damomurf: Please see GitHub documentation regarding repository mirroring with LFS |
Seems you are right. |
I'd suggest to tag this as a feature request. Current behaviour is basically expected imho and supporting LFS mirrors will be challenging in some regards:
Just out of interest, does somebody know whether GitHub support automated LFS object mirroring? For future reference: |
Maybe put a notice on migrating UI at first. |
I'll look into adding a note to the UI when LFS support is enabled. |
What is steps for mirroring LFS now? Is there some hook to make LFS pull with cmd ? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
@boskiv Please also see the GitHub docs for manual steps. |
BTW, the GitHub docs is what currently Git LFS recommends as per git-lfs/git-lfs#2342 (comment) @fabian-z Forgive me if I'm hijacking the issue, but could you explain your last comment in more details, in the context explained below? I have a GitHub repo with files in Git LFS. TL;TR: Is it possible? Would something along these lines work?
|
Is there anyone kinda sorta working on it? Or is there anyone who figured out a way how to do this manually/scripted externally for the time being? I'm using Gitea to keep backups of software I use or just find interesting, just in case... Obviously having the LFS objects as well is often very handy, many times necessary. |
No one is working on this. A bounty on bountysource might spur someone to look at it. From a quick glance we would need to implement an LFS client - possibly through vendoring git-lfs/git-lfs. There would need to be significant changes to the mirroring UI too. |
Chipped in 70 bucks into the bounty: https://www.bountysource.com/issues/41700547-repo-mirroring-doesn-t-mirror-lfs-data |
Is it rude for me to ask for a maintainer of the repo to add the bounty tag and maybe declare the bounty value in the title? Cheers and overall many many thanks for this lovely project to everyone who is working on it. It's of great use to me. :) |
@GlassedSilver thanks for your support :) I've just applied the bounty label to make this easier to find. |
[x]
):Description
In a clean install of Gitea I have attempted to mirror a Bitbucket server repository that I know has LFS enabled and stores LFS data. The LFS data appears to not being mirrored in Gitea. (The configured LFS data directory remains empty, even though the repository mirroring appears to be successful).
The text was updated successfully, but these errors were encountered: