Hello, first of all thank you for developing this wonderful tool.
I have an issue regarding only 2 repos out of around ~150 on my server.
I have set repos to also sync releases on interval.
Out of my ~150 repos, several dozens of them use GitHub releases, but only 2 surface this issue:
Every sync shows events for every release on these 2 repos. This spams the homepage activity log without any new releases actually being created that were not in the previous sync. Here is a screenshot demonstrating the problem:
This happens only for the 2 mentioned repos. Their GitHub links are the following:
I am not sure why this happens.
I have tried removing the repos from gitea-mirror and re-syncing them again from scratch. It didn't seem to change anything.
The actual releases don't get duplicated or anything from what I can tell, this is only an activity log spam issue.
Please let me know what other information I can provide to help pin the issue down.
Originally created by @chenasraf on GitHub (Jun 2, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/310
Hello, first of all thank you for developing this wonderful tool.
I have an issue regarding only 2 repos out of around ~150 on my server.
I have set repos to also sync releases on interval.
Out of my ~150 repos, several dozens of them use GitHub releases, but only 2 surface this issue:
Every sync shows events for every release on these 2 repos. This spams the homepage activity log without any new releases actually being created that were not in the previous sync. Here is a screenshot demonstrating the problem:
<img width="435" height="1052" alt="Image" src="https://github.com/user-attachments/assets/725d6bcf-26ed-4476-97c1-59c70fd4973d" />
---
This happens only for the 2 mentioned repos. Their GitHub links are the following:
- https://github.com/chenasraf/unaconfig_dart
- https://github.com/chenasraf/pantry-flutter
I am not sure why this happens.
I have tried removing the repos from gitea-mirror and re-syncing them again from scratch. It didn't seem to change anything.
The actual releases don't get duplicated or anything from what I can tell, this is only an activity log spam issue.
Please let me know what other information I can provide to help pin the issue down.
gitea-mirror version: v3.15.12
gitea version: 1.24.4
Fixed in v3.18.0 (#318). The release sync had a check that deleted and recreated every release whenever their order in Gitea didn't match GitHub's published_at order. On your two repos the git tag commit dates and the GitHub publish dates are in different orders (v0.1.0 was tagged before v0.1.1 but published after it), so that check fired on every sync and recreated everything, which is what spammed the activity feed. It now reconciles by tag instead of reordering, so existing releases are left alone.
<!-- gh-comment-id:4700703503 -->
@arunavo4 commented on GitHub (Jun 14, 2026):
Fixed in v3.18.0 (#318). The release sync had a check that deleted and recreated every release whenever their order in Gitea didn't match GitHub's `published_at` order. On your two repos the git tag commit dates and the GitHub publish dates are in different orders (v0.1.0 was tagged before v0.1.1 but published after it), so that check fired on every sync and recreated everything, which is what spammed the activity feed. It now reconciles by tag instead of reordering, so existing releases are left alone.
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 @chenasraf on GitHub (Jun 2, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/310
Hello, first of all thank you for developing this wonderful tool.
I have an issue regarding only 2 repos out of around ~150 on my server.
I have set repos to also sync releases on interval.
Out of my ~150 repos, several dozens of them use GitHub releases, but only 2 surface this issue:
Every sync shows events for every release on these 2 repos. This spams the homepage activity log without any new releases actually being created that were not in the previous sync. Here is a screenshot demonstrating the problem:
This happens only for the 2 mentioned repos. Their GitHub links are the following:
I am not sure why this happens.
I have tried removing the repos from gitea-mirror and re-syncing them again from scratch. It didn't seem to change anything.
The actual releases don't get duplicated or anything from what I can tell, this is only an activity log spam issue.
Please let me know what other information I can provide to help pin the issue down.
gitea-mirror version: v3.15.12
gitea version: 1.24.4
@arunavo4 commented on GitHub (Jun 14, 2026):
Fixed in v3.18.0 (#318). The release sync had a check that deleted and recreated every release whenever their order in Gitea didn't match GitHub's
published_atorder. On your two repos the git tag commit dates and the GitHub publish dates are in different orders (v0.1.0 was tagged before v0.1.1 but published after it), so that check fired on every sync and recreated everything, which is what spammed the activity feed. It now reconciles by tag instead of reordering, so existing releases are left alone.@chenasraf commented on GitHub (Jun 14, 2026):
Thank you so much for the fix 🙏🏼