mirror of
https://github.com/RayLabsHQ/gitea-mirror.git
synced 2026-04-24 23:05:53 +03:00
[GH-ISSUE #68] Release,PR,Issues,etc not syncing/mirror correctly #36
Labels
No labels
bug
documentation
enhancement
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/gitea-mirror#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Tailscale-VPS on GitHub (Aug 8, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/68
Originally assigned to: @arunavo4 on GitHub.
Dont know is its a bug or a user config error from my side...., If anything else is needed pls ask
@arunavo4 commented on GitHub (Aug 9, 2025):
@Tailscale-VPS Hey this was missed out in the last update. I have opened a new PR to address this. Will update you after I test it.
@Tailscale-VPS commented on GitHub (Aug 9, 2025):
Tested latest image v3.2.2 after cleaning the data dir.
Still results in same
But this time there was error in logs
@arunavo4 commented on GitHub (Aug 9, 2025):
@Tailscale-VPS I have tried to make a fix for this, as i cannot recreate this issue on my end. please try v3.2.4 once the CI completes
@Tailscale-VPS commented on GitHub (Aug 9, 2025):
Tested latest image v3.2.4 after cleaning the data dir.
Still results in same
But this time got some more info in the log
Don't understand why its saying this because i have given every permission to token and user exists -
@arunavo4 commented on GitHub (Aug 9, 2025):
@Tailscale-VPS
v3.2.5try this one@Tailscale-VPS commented on GitHub (Aug 9, 2025):
@arunavo4 Tested latest image v3.2.5 after cleaning the data dir.
Not complete but a bit of success here -
Still missing Issues,PR,Release content(APK,ZIPS,BInary)
LOGS
@arunavo4 commented on GitHub (Aug 9, 2025):
@Tailscale-VPS added the assets for release content. This was never added before. v3.2.6 and can you make sure issues and PR are are actually turned on? I have added some more logs for it
@Tailscale-VPS commented on GitHub (Aug 9, 2025):
@arunavo4 Tested latest image v3.2.6 after cleaning the data dir.
Success for Releases (with an error don't know why as it worked)
Also as u can see Full content is on so issues and PR are are actually turned on but not working currently (if u need logs tell me , but there's nothing currently related to those as far as i read the logs).
SUGGESTION
I believe when u are mirroring the releases using API there would be page numbers like page 1, page 2?
I think we should keep releases to the Page 1 only OR an env variable where user can choose how many release to keep, either page wise or number of release directly.
Why - the reason is that
1 - we are already mirroring full code with history so if anyone wants very very old release they can build it.
2 - Even page 1 contains more than enough releases approx 10.
3 - Its good we are mirroring all release but this will take a big toll on the storage as many repos contains 100 or 1000 of release and even multi-arch (https://github.com/xpipe-io/xpipe/releases?page=1).
WHAT TO DO WITH OLD RELEASES
As u already have cleanups we can remove then from gitea, for eg if the user chooses to keep only page 1 or 10 releases then remove the extra, while mirroring it will already check and compare then releases the extra release found on gitea will be deleted
@arunavo4 commented on GitHub (Aug 9, 2025):
@Tailscale-VPS Thank you for the feedback will pick up tomorrow.
@arunavo4 commented on GitHub (Aug 28, 2025):
@Tailscale-VPS have a look at v3.3.0 and also PR mirroring is not supported so its been implemented using just issues but it still has some issues so will have to test more and figure it out. for now I have added your release limit feature that u suggested and also issues are able to mirror like it should
@Tailscale-VPS commented on GitHub (Aug 28, 2025):
Sure ill test in within 24hrs.
@Tailscale-VPS commented on GitHub (Aug 29, 2025):
@arunavo4 Here are the new findings
Release are mirroring fine , Also liked how you implemented the release limit option (Currently only from UI, need to update the new ENV variables for this and other new stuff).
Issues mirroring is also fixed in v3.30.
PR mirroring as Issues have some error below is the snippet while it tries to mirror PR.
@arunavo4 commented on GitHub (Aug 29, 2025):
Thanks for the update looking into this today
@arunavo4 commented on GitHub (Aug 29, 2025):
@Tailscale-VPS I have fixed the PR mirroring in v3.4.0 and I have tested it myself please check and let me know
@Tailscale-VPS commented on GitHub (Aug 29, 2025):
@arunavo4 PR mirroring is working correctly in 3.4.0