mirror of
https://github.com/RayLabsHQ/gitea-mirror.git
synced 2026-04-24 23:05:53 +03:00
[GH-ISSUE #165] Issues and PRs are not mirroring after initial sync #81
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#81
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 @emrebasarannn on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/165
Originally assigned to: @arunavo4 on GitHub.
Having trouble with issue and pr mirroring.
For the initial sync + mirror, each issue mirrored successfully. But after that point no more issue or pr is being mirrored. I first initialized this repo 3 weeks ago and there is not a single more issue or pr since that day. I have to point out that my commits syncing just fine!
Here are logs: (i manually pushed
syncbutton on the gitea-mirror for the repodevops-issue-management)[Sync] Issues already mirrored for devops-issue-management; skippingWhen i manually check the original repo, i can see that there is multiple new issues that are not mirrored to my gitea. (the last mirrorred issue is 3 weeks old)
Images:
self hosted gitea image: docker.gitea.com/gitea:1.25.2
mysql image: docker.io/library/mysql:8
gitea-mirror image: ${DOCKER_REGISTRY:-ghcr.io}/${DOCKER_IMAGE:-raylabshq/gitea-mirror}:v3.9.2
(which i dont specify env variable for this, its taking default values)
My configuration on gitea-mirror:
@arunavo4 commented on GitHub (Jan 13, 2026):
@emrebasarannn Its a mistake on my part. I kept that resyncing for later cause the tracking and de-duplicating across github and gitea was getting too complex. Like when you first mirror it its fine but since we have issues and PR in same issues in gitea casue theres no way to do PR's tracking for gitea properly. I found that subsequent tracking of all the chnages /updates was too complex for all the metadata like issues / PR's / tags etc. Now one easy solution was to delete all and recreate it again. or build a complex tracking with id's etc.
@emrebasarannn commented on GitHub (Jan 13, 2026):
Hi @arunavo4,
So what you are telling me is that there is no current solution for this? Other then deleting and re-mirroring to the gitea?
I dont think this is manageble at all because for our organizations, we have about 200+ repos. We needed a automatic tool that constantly backups our metadata without human interaction.
@arunavo4 commented on GitHub (Jan 13, 2026):
@emrebasarannn Let me take a look at it again this week. as I had already planned to bulid this out. Let me see if I can find a way to solve this.
@emrebasarannn commented on GitHub (Jan 13, 2026):
Okey thank you.
@arunavo4 commented on GitHub (Feb 24, 2026):
Update: this is now handled in PR #184.
https://github.com/RayLabsHQ/gitea-mirror/pull/184
It fixes metadata sync so Issues and PRs continue syncing after the first run, updates existing mirrored entries instead of creating duplicates, and avoids duplicate mirrored comments on re-sync.