Currently all repositories mirror without LFS data by default.
If you want to mirror LFS data, you have to manually activate it post migration and do a sync job.
This is quite dangerous, as many users might backup their repositories only to find out later that they are missing the LFS pointers.
Originally created by @ArmainAP on GitHub (Aug 15, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/74
Currently all repositories mirror without LFS data by default.
If you want to mirror LFS data, you have to manually activate it post migration and do a sync job.
This is quite dangerous, as many users might backup their repositories only to find out later that they are missing the LFS pointers.
@ArmainAP This I did not realise this thanks. will check it out. But I am quite busy at the moment with other issues. Would appreciate a Community PR on this issue.
<!-- gh-comment-id:3193435025 -->
@arunavo4 commented on GitHub (Aug 16, 2025):
@ArmainAP This I did not realise this thanks. will check it out. But I am quite busy at the moment with other issues. Would appreciate a Community PR on this issue.
No worries! At least it is visible for now. I might try to look into it tomorrow.
Any tips or advice for starting out considering I am not familiar with the code base?
<!-- gh-comment-id:3193444132 -->
@ArmainAP commented on GitHub (Aug 16, 2025):
No worries! At least it is visible for now. I might try to look into it tomorrow.
Any tips or advice for starting out considering I am not familiar with the code base?
There is readme and the docs also a contribution markdown file. that should be a good start.
<!-- gh-comment-id:3193755914 -->
@arunavo4 commented on GitHub (Aug 16, 2025):
There is readme and the docs also a contribution markdown file. that should be a good start.
@ArmainAP I have added it by adding the lfs flag to the api call when creating the mirror on gitea as provided on thier docs. But i have not had the time to test it.
you need to have LFS turned on (LFS_START_SERVER = true in Gitea config) feel free to test it out v3.3.0
<!-- gh-comment-id:3233910728 -->
@arunavo4 commented on GitHub (Aug 28, 2025):
@ArmainAP I have added it by adding the `lfs` flag to the api call when creating the mirror on gitea as provided on thier docs. But i have not had the time to test it.
you need to have LFS turned on (`LFS_START_SERVER = true` in Gitea config) feel free to test it out v3.3.0
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ArmainAP on GitHub (Aug 15, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/74
Currently all repositories mirror without LFS data by default.
If you want to mirror LFS data, you have to manually activate it post migration and do a sync job.
This is quite dangerous, as many users might backup their repositories only to find out later that they are missing the LFS pointers.
@arunavo4 commented on GitHub (Aug 16, 2025):
@ArmainAP This I did not realise this thanks. will check it out. But I am quite busy at the moment with other issues. Would appreciate a Community PR on this issue.
@ArmainAP commented on GitHub (Aug 16, 2025):
No worries! At least it is visible for now. I might try to look into it tomorrow.
Any tips or advice for starting out considering I am not familiar with the code base?
@arunavo4 commented on GitHub (Aug 16, 2025):
There is readme and the docs also a contribution markdown file. that should be a good start.
@arunavo4 commented on GitHub (Aug 28, 2025):
@ArmainAP I have added it by adding the
lfsflag to the api call when creating the mirror on gitea as provided on thier docs. But i have not had the time to test it.you need to have LFS turned on (
LFS_START_SERVER = truein Gitea config) feel free to test it out v3.3.0