There doesn't seem to be any condition for this, I think it happens on all my releases/repos.
Let me know if there is anything else I can provide for context
Originally created by @chenasraf on GitHub (Jun 30, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/334
Originally assigned to: @arunavo4 on GitHub.
Thank you for this wonderful tool! I have a small issue where release data mirrored over from GitHub does not include the release title.
Example release: https://github.com/chenasraf/pantry-flutter/releases/tag/v0.19.0
Example screenshots:
Gitea:
<img width="1312" height="530" alt="Image" src="https://github.com/user-attachments/assets/80ec71e7-5784-475b-b914-ef381199be67" />
<img width="1326" height="394" alt="Image" src="https://github.com/user-attachments/assets/a991e57c-a4fb-4418-9861-0018de3897e0" />
GitHub (same release):
<img width="1238" height="521" alt="Image" src="https://github.com/user-attachments/assets/8c550bd3-23e5-4bcb-b6b6-fa9c347a703a" />
There doesn't seem to be any condition for this, I think it happens on all my releases/repos.
Let me know if there is anything else I can provide for context
@chenasraf Thanks for reporting this should be fixed now in latest verison
<!-- gh-comment-id:4850763846 -->
@arunavo4 commented on GitHub (Jul 1, 2026):
@chenasraf Thanks for reporting this should be fixed now in latest verison
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 30, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/334
Originally assigned to: @arunavo4 on GitHub.
Thank you for this wonderful tool! I have a small issue where release data mirrored over from GitHub does not include the release title.
Example release: https://github.com/chenasraf/pantry-flutter/releases/tag/v0.19.0
Example screenshots:
Gitea:
GitHub (same release):
There doesn't seem to be any condition for this, I think it happens on all my releases/repos.
Let me know if there is anything else I can provide for context
@arunavo4 commented on GitHub (Jul 1, 2026):
@chenasraf Thanks for reporting this should be fixed now in latest verison
@chenasraf commented on GitHub (Jul 1, 2026):
Thank you for looking into it and resolving 😊🙏🏼