[GH-ISSUE #68] Release,PR,Issues,etc not syncing/mirror correctly #166

New Issue

Closed

opened 2026-04-11 09:03:53 -05:00 by GiteaMirror · 15 comments

GiteaMirror commented 2026-04-11 09:03:53 -05:00

Owner

Copy Link

Copy Source

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

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    

GiteaMirror added the bug label 2026-04-11 09:03:53 -05:00

GiteaMirror closed this issue 2026-04-11 09:03:54 -05:00

GiteaMirror commented 2026-04-11 09:03:56 -05:00

Author

Owner

Copy Link

Copy Source

@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.

<!-- gh-comment-id:3170193848 --> @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.

GiteaMirror commented 2026-04-11 09:03:56 -05:00

Author

Owner

Copy Link

Copy Source

@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

Created new job f767f7c9-6c08-4d6f-b7cb-2bf7720f677a with 2 items
Registered active job: f767f7c9-6c08-4d6f-b7cb-2bf7720f677a (1 total active jobs)
Starting mirror for repository: AdrenoToolsDrivers
Starting mirror for repository: winlator
Repository AdrenoToolsDrivers will be mirrored to owner: starred
Repository winlator will be mirrored to owner: starred
[Org Creation] Attempting to get or create organization: starred (attempt 1/3)
[Org Creation] Attempting to get or create organization: starred (attempt 1/3)
[Org Creation] Organization starred already exists with ID: 3
[Org Creation] Organization starred already exists with ID: 3
Mirroring repository AdrenoToolsDrivers to organization starred
Mirroring repository winlator to organization starred
Error while mirroring repository AdrenoToolsDrivers: HTTP 401: Unauthorized - {"message":"user does not exist [uid: 0, name: ]","url":"https://site.example.com/api/swagger"}
Publishing event to channel mirror-status:aNHbyWiR2LW8kqshqtM2BSBzkY8H5ds7 for user aNHbyWiR2LW8kqshqtM2BSBzkY8H5ds7
Event published successfully with ID fa83a66a-7d0a-4c17-8d55-ccb11b3144e2
Retrying repository AdrenoToolsDrivers (attempt 1): Failed to mirror repository: Failed to mirror repository: HTTP 401: Unauthorized - {"message":"user does not exist [uid: 0, name: ]","url":"https://site.example.com/api/swagger"}
Starting mirror for repository: AdrenoToolsDrivers
Repository AdrenoToolsDrivers will be mirrored to owner: starred
[Org Creation] Attempting to get or create organization: starred (attempt 1/3)
[Org Creation] Organization starred already exists with ID: 3
Repository AdrenoToolsDrivers already exists in Gitea organization starred. Updating database status.
Publishing event to channel mirror-status:aNHbyWiR2LW8kqshqtM2BSBzkY8H5ds7 for user aNHbyWiR2LW8kqshqtM2BSBzkY8H5ds7
Event published successfully with ID 0021ade8-980a-4aab-9d5b-e5c76ef4480f
Repository AdrenoToolsDrivers database status updated to mirrored in organization starred
Mirroring progress: 50% (1/2)
Successfully mirrored repository: AdrenoToolsDrivers

<!-- gh-comment-id:3170388272 --> @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 ``` Created new job f767f7c9-6c08-4d6f-b7cb-2bf7720f677a with 2 items Registered active job: f767f7c9-6c08-4d6f-b7cb-2bf7720f677a (1 total active jobs) Starting mirror for repository: AdrenoToolsDrivers Starting mirror for repository: winlator Repository AdrenoToolsDrivers will be mirrored to owner: starred Repository winlator will be mirrored to owner: starred [Org Creation] Attempting to get or create organization: starred (attempt 1/3) [Org Creation] Attempting to get or create organization: starred (attempt 1/3) [Org Creation] Organization starred already exists with ID: 3 [Org Creation] Organization starred already exists with ID: 3 Mirroring repository AdrenoToolsDrivers to organization starred Mirroring repository winlator to organization starred Error while mirroring repository AdrenoToolsDrivers: HTTP 401: Unauthorized - {"message":"user does not exist [uid: 0, name: ]","url":"https://site.example.com/api/swagger"} Publishing event to channel mirror-status:aNHbyWiR2LW8kqshqtM2BSBzkY8H5ds7 for user aNHbyWiR2LW8kqshqtM2BSBzkY8H5ds7 Event published successfully with ID fa83a66a-7d0a-4c17-8d55-ccb11b3144e2 Retrying repository AdrenoToolsDrivers (attempt 1): Failed to mirror repository: Failed to mirror repository: HTTP 401: Unauthorized - {"message":"user does not exist [uid: 0, name: ]","url":"https://site.example.com/api/swagger"} Starting mirror for repository: AdrenoToolsDrivers Repository AdrenoToolsDrivers will be mirrored to owner: starred [Org Creation] Attempting to get or create organization: starred (attempt 1/3) [Org Creation] Organization starred already exists with ID: 3 Repository AdrenoToolsDrivers already exists in Gitea organization starred. Updating database status. Publishing event to channel mirror-status:aNHbyWiR2LW8kqshqtM2BSBzkY8H5ds7 for user aNHbyWiR2LW8kqshqtM2BSBzkY8H5ds7 Event published successfully with ID 0021ade8-980a-4aab-9d5b-e5c76ef4480f Repository AdrenoToolsDrivers database status updated to mirrored in organization starred Mirroring progress: 50% (1/2) Successfully mirrored repository: AdrenoToolsDrivers ```

GiteaMirror commented 2026-04-11 09:03:57 -05:00

Author

Owner

Copy Link

Copy Source

@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

<!-- gh-comment-id:3170437052 --> @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

GiteaMirror commented 2026-04-11 09:03:58 -05:00

Author

Owner

Copy Link

Copy Source

@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

Mirroring repository AdrenoToolsDrivers to organization starred
[HTTP Client] Authentication failed for http://gitea-mirror:3000/api/v1/repos/starred/AdrenoToolsDrivers/releases
[HTTP Client] Response: {"message":"user does not exist [uid: 0, name: ]","url":"https://site.example.com/api/swagger"}
[HTTP Client] Token appears to be invalid or the user account is not properly configured in Gitea
Error while mirroring repository AdrenoToolsDrivers: HTTP 401: user does not exist [uid: 0, name: ]
Publishing event to channel mirror-status:hgTimz072bXoNHZvV3lcC3och8b076bC for user hgTimz072bXoNHZvV3lcC3och8b076bC
Event published successfully with ID 974bb1e4-3237-460e-8436-152ca9232aa9
Retrying repository AdrenoToolsDrivers (attempt 1): Failed to mirror repository: Failed to mirror repository: HTTP 401: user does not exist [uid: 0, name: ]
Starting mirror for repository: AdrenoToolsDrivers
Repository AdrenoToolsDrivers will be mirrored to owner: starred
[Org Creation] Validating user authentication before organization operations
[Org Creation] Authenticated as user: homelab10400 (ID: 1)
[Org Creation] Attempting to get or create organization: starred (attempt 1/3)
[Org Creation] Organization starred already exists with ID: 3
Repository AdrenoToolsDrivers already exists in Gitea organization starred. Updating database status.
Publishing event to channel mirror-status:hgTimz072bXoNHZvV3lcC3och8b076bC for user hgTimz072bXoNHZvV3lcC3och8b076bC
Event published successfully with ID b3592c0d-e1a1-4685-9d2f-98cc7f146d49
Repository AdrenoToolsDrivers database status updated to mirrored in organization starred

Don't understand why its saying this because i have given every permission to token and user exists -

<!-- gh-comment-id:3170498587 --> @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 ``` Mirroring repository AdrenoToolsDrivers to organization starred [HTTP Client] Authentication failed for http://gitea-mirror:3000/api/v1/repos/starred/AdrenoToolsDrivers/releases [HTTP Client] Response: {"message":"user does not exist [uid: 0, name: ]","url":"https://site.example.com/api/swagger"} [HTTP Client] Token appears to be invalid or the user account is not properly configured in Gitea Error while mirroring repository AdrenoToolsDrivers: HTTP 401: user does not exist [uid: 0, name: ] Publishing event to channel mirror-status:hgTimz072bXoNHZvV3lcC3och8b076bC for user hgTimz072bXoNHZvV3lcC3och8b076bC Event published successfully with ID 974bb1e4-3237-460e-8436-152ca9232aa9 Retrying repository AdrenoToolsDrivers (attempt 1): Failed to mirror repository: Failed to mirror repository: HTTP 401: user does not exist [uid: 0, name: ] Starting mirror for repository: AdrenoToolsDrivers Repository AdrenoToolsDrivers will be mirrored to owner: starred [Org Creation] Validating user authentication before organization operations [Org Creation] Authenticated as user: homelab10400 (ID: 1) [Org Creation] Attempting to get or create organization: starred (attempt 1/3) [Org Creation] Organization starred already exists with ID: 3 Repository AdrenoToolsDrivers already exists in Gitea organization starred. Updating database status. Publishing event to channel mirror-status:hgTimz072bXoNHZvV3lcC3och8b076bC for user hgTimz072bXoNHZvV3lcC3och8b076bC Event published successfully with ID b3592c0d-e1a1-4685-9d2f-98cc7f146d49 Repository AdrenoToolsDrivers database status updated to mirrored in organization starred ``` Don't understand why its saying this because i have given every permission to token and user exists -    

GiteaMirror commented 2026-04-11 09:03:59 -05:00

Author

Owner

Copy Link

Copy Source

@arunavo4 commented on GitHub (Aug 9, 2025):

@Tailscale-VPS v3.2.5 try this one

<!-- gh-comment-id:3170703866 --> @arunavo4 commented on GitHub (Aug 9, 2025): @Tailscale-VPS `v3.2.5` try this one

GiteaMirror commented 2026-04-11 09:03:59 -05:00

Author

Owner

Copy Link

Copy Source

@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

Starting mirror for repository: AdrenoToolsDrivers
Starting mirror for repository: winlator
Repository AdrenoToolsDrivers will be mirrored to owner: starred
Repository winlator will be mirrored to owner: starred
[Org Creation] Validating user authentication before organization operations
[Org Creation] Validating user authentication before organization operations
[Org Creation] Authenticated as user: homelab10400 (ID: 1)
[Org Creation] Attempting to get or create organization: starred (attempt 1/3)
[Org Creation] Authenticated as user: homelab10400 (ID: 1)
[Org Creation] Attempting to get or create organization: starred (attempt 1/3)
[Org Creation] Organization starred not found. Creating new organization.
[Org Creation] Organization starred not found. Creating new organization.
[Org Creation] Successfully created organization starred with ID: 5
Publishing event to channel mirror-status:Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj for user Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj
Event published successfully with ID d4195c5d-7372-459a-a229-4b1f34dfcb70
[Org Creation] Organization creation failed due to duplicate. Will retry check.
[Org Creation] Waiting 100ms before retry...
Mirroring repository AdrenoToolsDrivers to organization starred
[Org Creation] Attempting to get or create organization: starred (attempt 2/3)
[Org Creation] Organization starred already exists with ID: 5
Mirroring repository winlator to organization starred
[Releases] Verifying repository AdrenoToolsDrivers exists at starred
[Releases] Found 30 releases to mirror for K11MCH1/AdrenoToolsDrivers
[Releases] Successfully mirrored release: v999.999.999
[Releases] Successfully mirrored release: v25.3.0-rc.03
[Releases] Successfully mirrored release: v25.3.0-rc.02
[Releases] Successfully mirrored release: v25.3.0-rc.01
[Releases] Successfully mirrored release: v25.2.0-rc.14
[Releases] Successfully mirrored release: v25.2.0-rc.13
[Releases] Successfully mirrored release: v25.2.0-rc.12
[Releases] Successfully mirrored release: v25.2.0-rc.11
[Releases] Successfully mirrored release: v25.2.0-rc.10
[Releases] Successfully mirrored release: v25.2.0-rc.09
[Releases] Successfully mirrored release: v25.2.0-rc.08
[Releases] Successfully mirrored release: v25.2.0-rc.07
[Releases] Successfully mirrored release: v25.2.0-rc.06
[Releases] Successfully mirrored release: v25.2.0-rc.05
[Releases] Successfully mirrored release: v25.2.0-rc.04
[Releases] Successfully mirrored release: v25.2.0-rc.03
[Releases] Successfully mirrored release: v25.2.0-rc.02
[Releases] Successfully mirrored release: v25.2.0-rc.01
[Releases] Successfully mirrored release: v25.1.0-rc.06
[Releases] Successfully mirrored release: v25.1.0-rc.05
[Releases] Successfully mirrored release: v25.1.0-rc.04
[Releases] Successfully mirrored release: v25.1.0-rc.02
[Releases] Successfully mirrored release: v25.1.0-rc.01
[Releases] Successfully mirrored release: 25.1.0-rc.03
[Releases] Successfully mirrored release: v819.1
[Releases] Successfully mirrored release: v805
[Releases] Successfully mirrored release: v25.0.0_r8
[Releases] Successfully mirrored release: v25.0.0_r7
[Releases] Successfully mirrored release: v25.0.0_r6
[Releases] Successfully mirrored release: v25.0.0_r5
✅ Mirrored 30 new releases to Gitea (0 already existed)
Error while mirroring repository AdrenoToolsDrivers: Missing GitHub or Gitea configuration.
Publishing event to channel mirror-status:Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj for user Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj
Event published successfully with ID 0837ee40-5182-4f60-bc0e-a309499c9b5e
Retrying repository AdrenoToolsDrivers (attempt 1): Failed to mirror repository: Failed to mirror repository: Missing GitHub or Gitea configuration.
Found 1 interrupted jobs:
- Job 9f4dab10-5d9d-48a5-87d6-7f4914730a39: mirror (started: 2025-08-09T13:32:28.000Z, last checkpoint: never)
Starting mirror for repository: AdrenoToolsDrivers
Repository AdrenoToolsDrivers will be mirrored to owner: starred
[Org Creation] Validating user authentication before organization operations
[Org Creation] Authenticated as user: homelab10400 (ID: 1)
[Org Creation] Attempting to get or create organization: starred (attempt 1/3)
[Org Creation] Organization starred already exists with ID: 5
Repository AdrenoToolsDrivers already exists in Gitea organization starred. Updating database status.
Publishing event to channel mirror-status:Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj for user Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj
Event published successfully with ID 12063a35-47f6-414b-b513-b5a653228f67
Repository AdrenoToolsDrivers database status updated to mirrored in organization starred

<!-- gh-comment-id:3170729625 --> @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 ``` Starting mirror for repository: AdrenoToolsDrivers Starting mirror for repository: winlator Repository AdrenoToolsDrivers will be mirrored to owner: starred Repository winlator will be mirrored to owner: starred [Org Creation] Validating user authentication before organization operations [Org Creation] Validating user authentication before organization operations [Org Creation] Authenticated as user: homelab10400 (ID: 1) [Org Creation] Attempting to get or create organization: starred (attempt 1/3) [Org Creation] Authenticated as user: homelab10400 (ID: 1) [Org Creation] Attempting to get or create organization: starred (attempt 1/3) [Org Creation] Organization starred not found. Creating new organization. [Org Creation] Organization starred not found. Creating new organization. [Org Creation] Successfully created organization starred with ID: 5 Publishing event to channel mirror-status:Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj for user Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj Event published successfully with ID d4195c5d-7372-459a-a229-4b1f34dfcb70 [Org Creation] Organization creation failed due to duplicate. Will retry check. [Org Creation] Waiting 100ms before retry... Mirroring repository AdrenoToolsDrivers to organization starred [Org Creation] Attempting to get or create organization: starred (attempt 2/3) [Org Creation] Organization starred already exists with ID: 5 Mirroring repository winlator to organization starred [Releases] Verifying repository AdrenoToolsDrivers exists at starred [Releases] Found 30 releases to mirror for K11MCH1/AdrenoToolsDrivers [Releases] Successfully mirrored release: v999.999.999 [Releases] Successfully mirrored release: v25.3.0-rc.03 [Releases] Successfully mirrored release: v25.3.0-rc.02 [Releases] Successfully mirrored release: v25.3.0-rc.01 [Releases] Successfully mirrored release: v25.2.0-rc.14 [Releases] Successfully mirrored release: v25.2.0-rc.13 [Releases] Successfully mirrored release: v25.2.0-rc.12 [Releases] Successfully mirrored release: v25.2.0-rc.11 [Releases] Successfully mirrored release: v25.2.0-rc.10 [Releases] Successfully mirrored release: v25.2.0-rc.09 [Releases] Successfully mirrored release: v25.2.0-rc.08 [Releases] Successfully mirrored release: v25.2.0-rc.07 [Releases] Successfully mirrored release: v25.2.0-rc.06 [Releases] Successfully mirrored release: v25.2.0-rc.05 [Releases] Successfully mirrored release: v25.2.0-rc.04 [Releases] Successfully mirrored release: v25.2.0-rc.03 [Releases] Successfully mirrored release: v25.2.0-rc.02 [Releases] Successfully mirrored release: v25.2.0-rc.01 [Releases] Successfully mirrored release: v25.1.0-rc.06 [Releases] Successfully mirrored release: v25.1.0-rc.05 [Releases] Successfully mirrored release: v25.1.0-rc.04 [Releases] Successfully mirrored release: v25.1.0-rc.02 [Releases] Successfully mirrored release: v25.1.0-rc.01 [Releases] Successfully mirrored release: 25.1.0-rc.03 [Releases] Successfully mirrored release: v819.1 [Releases] Successfully mirrored release: v805 [Releases] Successfully mirrored release: v25.0.0_r8 [Releases] Successfully mirrored release: v25.0.0_r7 [Releases] Successfully mirrored release: v25.0.0_r6 [Releases] Successfully mirrored release: v25.0.0_r5 ✅ Mirrored 30 new releases to Gitea (0 already existed) Error while mirroring repository AdrenoToolsDrivers: Missing GitHub or Gitea configuration. Publishing event to channel mirror-status:Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj for user Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj Event published successfully with ID 0837ee40-5182-4f60-bc0e-a309499c9b5e Retrying repository AdrenoToolsDrivers (attempt 1): Failed to mirror repository: Failed to mirror repository: Missing GitHub or Gitea configuration. Found 1 interrupted jobs: - Job 9f4dab10-5d9d-48a5-87d6-7f4914730a39: mirror (started: 2025-08-09T13:32:28.000Z, last checkpoint: never) Starting mirror for repository: AdrenoToolsDrivers Repository AdrenoToolsDrivers will be mirrored to owner: starred [Org Creation] Validating user authentication before organization operations [Org Creation] Authenticated as user: homelab10400 (ID: 1) [Org Creation] Attempting to get or create organization: starred (attempt 1/3) [Org Creation] Organization starred already exists with ID: 5 Repository AdrenoToolsDrivers already exists in Gitea organization starred. Updating database status. Publishing event to channel mirror-status:Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj for user Kdzl8PP8acXoYQI8b0CHOM3jaclGjpaj Event published successfully with ID 12063a35-47f6-414b-b513-b5a653228f67 Repository AdrenoToolsDrivers database status updated to mirrored in organization starred ```

GiteaMirror commented 2026-04-11 09:04:01 -05:00

Author

Owner

Copy Link

Copy Source

@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

<!-- gh-comment-id:3170843017 --> @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

GiteaMirror commented 2026-04-11 09:04:02 -05:00

Author

Owner

Copy Link

Copy Source

@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

<!-- gh-comment-id:3171327885 --> @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

GiteaMirror commented 2026-04-11 09:04:03 -05:00

Author

Owner

Copy Link

Copy Source

@arunavo4 commented on GitHub (Aug 9, 2025):

@Tailscale-VPS Thank you for the feedback will pick up tomorrow.

<!-- gh-comment-id:3171964851 --> @arunavo4 commented on GitHub (Aug 9, 2025): @Tailscale-VPS Thank you for the feedback will pick up tomorrow.

GiteaMirror commented 2026-04-11 09:04:04 -05:00

Author

Owner

Copy Link

Copy Source

@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

<!-- gh-comment-id:3233832977 --> @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

GiteaMirror commented 2026-04-11 09:04:04 -05:00

Author

Owner

Copy Link

Copy Source

@Tailscale-VPS commented on GitHub (Aug 28, 2025):

Sure ill test in within 24hrs.

<!-- gh-comment-id:3234680070 --> @Tailscale-VPS commented on GitHub (Aug 28, 2025): Sure ill test in within 24hrs.

GiteaMirror commented 2026-04-11 09:04:05 -05:00

Author

Owner

Copy Link

Copy Source

@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.

Mirroring 23 pull requests from K11MCH1/AdrenoToolsDrivers
[Pull Requests] Creating enriched issue for PR #62: Remove discord link
[Pull Requests] Falling back to basic info for PR #62 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #60: Citra fix
[Pull Requests] ❌ Failed to mirror PR #62: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #59: Fix name in ppsspp.md
[Pull Requests] Creating enriched issue for PR #58: Add PPSSPP
[Pull Requests] Falling back to basic info for PR #60 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #59 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #58 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #61: Remove yuzu and Citra
[Pull Requests] ❌ Failed to mirror PR #59: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #60: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #58: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #61 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #61: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #56: Remove broken discord link
[Pull Requests] Falling back to basic info for PR #56 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #41: added images instead of links of Yuzu android guide
[Pull Requests] ❌ Failed to mirror PR #56: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #55: Organize images
[Pull Requests] Creating enriched issue for PR #57: Grammar Nits
[Pull Requests] Falling back to basic info for PR #41 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #42: Adjusted the readme title for mobile viewers
[Pull Requests] Falling back to basic info for PR #57 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #55 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #41: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #42 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #57: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #55: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #42: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #38: Use images files for Citra
[Pull Requests] Falling back to basic info for PR #38 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #32: Added Citra Support
[Pull Requests] Creating enriched issue for PR #40: Yuzu android guide is changed to letest yuzu android version guide
[Pull Requests] ❌ Failed to mirror PR #38: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #33: Fixed All Caps And Improved The Guide
[Pull Requests] Falling back to basic info for PR #32 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #40 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #31: Revert "Added Citra Readme File"
[Pull Requests] Falling back to basic info for PR #33 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #32: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #40: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #31 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #33: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #31: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #27: Added Citra Support
[Pull Requests] Creating enriched issue for PR #30: Revert "Added Citra Support"
[Pull Requests] Falling back to basic info for PR #27 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #28: Added Citra Readme File
[Pull Requests] ❌ Failed to mirror PR #27: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #30 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #29: Added Citra Readme File
[Pull Requests] Falling back to basic info for PR #28 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #30: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #29 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #28: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #16: Added Yuzu and Dolphin emulators
[Pull Requests] ❌ Failed to mirror PR #29: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #16 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #16: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #1: Minor adjustment
[Pull Requests] Falling back to basic info for PR #1 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #1: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Creating enriched issue for PR #15: Update README for Strato
[Pull Requests] Creating enriched issue for PR #2: add mali drivers for readme md
[Pull Requests] Falling back to basic info for PR #15 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] Falling back to basic info for PR #2 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #2: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
[Pull Requests] ❌ Failed to mirror PR #15: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64
✅ Mirrored 0/23 pull requests to Gitea as enriched issues (23 failed)

<!-- gh-comment-id:3236628597 --> @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. ``` Mirroring 23 pull requests from K11MCH1/AdrenoToolsDrivers [Pull Requests] Creating enriched issue for PR #62: Remove discord link [Pull Requests] Falling back to basic info for PR #62 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #60: Citra fix [Pull Requests] ❌ Failed to mirror PR #62: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #59: Fix name in ppsspp.md [Pull Requests] Creating enriched issue for PR #58: Add PPSSPP [Pull Requests] Falling back to basic info for PR #60 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #59 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #58 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #61: Remove yuzu and Citra [Pull Requests] ❌ Failed to mirror PR #59: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #60: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #58: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #61 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #61: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #56: Remove broken discord link [Pull Requests] Falling back to basic info for PR #56 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #41: added images instead of links of Yuzu android guide [Pull Requests] ❌ Failed to mirror PR #56: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #55: Organize images [Pull Requests] Creating enriched issue for PR #57: Grammar Nits [Pull Requests] Falling back to basic info for PR #41 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #42: Adjusted the readme title for mobile viewers [Pull Requests] Falling back to basic info for PR #57 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #55 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #41: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #42 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #57: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #55: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #42: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #38: Use images files for Citra [Pull Requests] Falling back to basic info for PR #38 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #32: Added Citra Support [Pull Requests] Creating enriched issue for PR #40: Yuzu android guide is changed to letest yuzu android version guide [Pull Requests] ❌ Failed to mirror PR #38: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #33: Fixed All Caps And Improved The Guide [Pull Requests] Falling back to basic info for PR #32 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #40 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #31: Revert "Added Citra Readme File" [Pull Requests] Falling back to basic info for PR #33 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #32: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #40: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #31 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #33: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #31: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #27: Added Citra Support [Pull Requests] Creating enriched issue for PR #30: Revert "Added Citra Support" [Pull Requests] Falling back to basic info for PR #27 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #28: Added Citra Readme File [Pull Requests] ❌ Failed to mirror PR #27: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #30 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #29: Added Citra Readme File [Pull Requests] Falling back to basic info for PR #28 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #30: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #29 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #28: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #16: Added Yuzu and Dolphin emulators [Pull Requests] ❌ Failed to mirror PR #29: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #16 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #16: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #1: Minor adjustment [Pull Requests] Falling back to basic info for PR #1 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #1: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Creating enriched issue for PR #15: Update README for Strato [Pull Requests] Creating enriched issue for PR #2: add mali drivers for readme md [Pull Requests] Falling back to basic info for PR #15 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] Falling back to basic info for PR #2 due to error: HttpError: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #2: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 [Pull Requests] ❌ Failed to mirror PR #15: HTTP 422: []: json: cannot unmarshal number { into Go struct field CreateIssueOption.Labels of type int64 ✅ Mirrored 0/23 pull requests to Gitea as enriched issues (23 failed) ```

GiteaMirror commented 2026-04-11 09:04:06 -05:00

Author

Owner

Copy Link

Copy Source

@arunavo4 commented on GitHub (Aug 29, 2025):

Thanks for the update looking into this today

<!-- gh-comment-id:3236651905 --> @arunavo4 commented on GitHub (Aug 29, 2025): Thanks for the update looking into this today

GiteaMirror commented 2026-04-11 09:04:06 -05:00

Author

Owner

Copy Link

Copy Source

@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

<!-- gh-comment-id:3236747018 --> @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 <img width="848" height="296" alt="Image" src="https://github.com/user-attachments/assets/05d67b9a-e23a-47ab-a7c3-b90eaea929de" />

GiteaMirror commented 2026-04-11 09:04:07 -05:00

Author

Owner

Copy Link

Copy Source

@Tailscale-VPS commented on GitHub (Aug 29, 2025):

@arunavo4 PR mirroring is working correctly in 3.4.0

<!-- gh-comment-id:3236905756 --> @Tailscale-VPS commented on GitHub (Aug 29, 2025): @arunavo4 PR mirroring is working correctly in 3.4.0

GiteaMirror referenced this issue 2026-04-11 09:14:25 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #316

GiteaMirror referenced this issue 2026-04-13 14:16:18 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #559

GiteaMirror referenced this issue 2026-04-16 02:46:29 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #807

GiteaMirror referenced this issue 2026-04-19 13:38:04 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #1057

GiteaMirror referenced this issue 2026-04-21 23:16:17 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #1307

GiteaMirror referenced this issue 2026-04-24 18:19:39 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #1559

GiteaMirror referenced this issue 2026-04-27 19:10:50 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #1812

GiteaMirror referenced this issue 2026-05-03 03:02:41 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #2068

GiteaMirror referenced this issue 2026-05-12 20:26:45 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #2326

GiteaMirror referenced this issue 2026-05-15 05:15:10 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #2588

GiteaMirror referenced this issue 2026-05-17 19:20:37 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #2851

GiteaMirror referenced this issue 2026-05-20 14:49:37 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #2994

GiteaMirror referenced this issue 2026-05-24 13:44:26 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #3216

GiteaMirror referenced this issue 2026-05-28 23:30:14 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #3493

GiteaMirror referenced this issue 2026-06-01 22:33:52 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #3778

GiteaMirror referenced this issue 2026-06-07 15:25:47 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #3935

GiteaMirror referenced this issue 2026-06-08 15:45:35 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #4177

GiteaMirror referenced this issue 2026-06-10 19:16:03 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #4336

GiteaMirror referenced this issue 2026-06-13 07:22:25 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #4576

GiteaMirror referenced this issue 2026-06-15 05:52:46 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #4871

GiteaMirror referenced this issue 2026-06-17 01:53:33 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #5039

GiteaMirror referenced this issue 2026-06-18 18:11:08 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #5289

GiteaMirror referenced this issue 2026-06-20 14:01:06 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #5589

GiteaMirror referenced this issue 2026-06-21 21:50:10 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #5892

GiteaMirror referenced this issue 2026-07-12 09:49:40 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #6199

GiteaMirror referenced this issue 2026-07-13 13:10:42 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #6513

GiteaMirror referenced this issue 2026-07-14 20:16:22 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #6827

GiteaMirror referenced this issue 2026-07-16 01:45:13 -05:00

[PR #166] [CLOSED] Fix/issue 161 165 sync improvements #7143

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

chore/security-and-deps

v3.21.0

v3.20.4

v3.20.3

v3.20.2

v3.20.1

v3.20.0

v3.19.1

v3.19.0

v3.18.0

v3.17.1

v3.17.0

v3.16.3

v3.16.2

v3.16.1

v3.16.0

v3.15.12

v3.15.11

v3.15.10

v3.15.9

v3.15.8

v3.15.7

v3.15.6

v3.15.5

v3.15.4

v3.15.3

v3.15.2

v3.15.1

v3.15.0

v3.14.2

v3.14.1

v3.14.0

v3.13.4

v3.13.3

v3.13.2

v3.13.1

v3.13.0

v3.12.5

v3.12.4

v3.12.3

v3.12.2

v3.12.1

v3.12.0

v3.11.0

v3.10.1

v3.10.0

v3.9.6

v3.9.5

v3.9.4

v3.9.3

v3.9.2

v3.9.0

v3.8.11

v3.8.10

v3.8.9

v3.8.8

v3.8.7

v3.8.6

v3.8.5

v3.8.4

v3.8.3

v3.8.2

v3.8.1

v3.8.0

v3-sso

v3.7.2

v3.7.1

v3.7.0

v3.6.0

v3.5.4

v3.5.3

v3.5.2

v3.5.1

v3.5.0

v3.4.0

v3.3.0

v3.2.6

v3.2.5

v3.2.4

v3.2.3

v3.2.2

v3.2.1

v3.2.0

v3.1.1

v3.1.0

v3.0.1

v3.0.0

v2.22.0

v2.21.0

v2.20.1

v2.20.0

v2.18.0

v2.17.0

v2.16.3

v2.16.2

v2.16.1

v2.16.0

v2.15.0

v2.14.0

v2.13.2

v2.13.1

v2.13.0

v2.12.0

v2.11.2

v2.11.1

v2.11.0

v2.10.0

v2.9.3

v2.9.2

v2.9.1

v2.9.0

v2.8.0

v2.7.0

v2.6.0

v2.5.4

v2.5.3

v2.5.2

v2.5.1

v2.5.0

v2.1.0

v2.0.0

v1.0.0

Labels

Clear labels

bug

documentation

enhancement

help wanted

pull-request

Mirrored from GitHub Pull Request

question

wontfix

No labels bug

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

GiteaMirror ninjasurge (Kaehlen Rog)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#166