Uploaded attachments of a release in a mirrored repo will never display if release tag already exists in an older commit #3148

New Issue

GiteaMirror · 2025-11-02T05:02:00-06:00

GiteaMirror commented

2025-11-02 05:02:00 -06:00

Originally created by @chotaire on GitHub (Apr 7, 2019).

Gitea version (or commit ref): 1.9.0+dev-61-g7ed65a98e
Git version:
Operating system: Linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes
- No
- Not relevant
Log gist:

Description

When mirroring e.g. a Github repository that has an older, not the current commit tagged v0.1 and a release created, no release will show up on the mirrored repository. So we're creating a release of v0.1 within the mirrored repository. This will work, but any uploaded attachments will never show.

However, if the current commit is tagged v0.1 and then the repository gets mirrored and we're creating a release called v0.1 within the mirrored repository, uploaded attachments will finally show up.

There seems to be an issue with displaying release attachments when the release has the tag of an older (not the current) commit. This is a real issue as I can't seem to be able to create a release from a tag that has been set to an older commit (unlike on Github).

Normal repositories might also be affected, but I have not seen it yet.

Originally created by @chotaire on GitHub (Apr 7, 2019). - Gitea version (or commit ref): 1.9.0+dev-61-g7ed65a98e - Git version: - Operating system: Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes - [ ] No - [ ] Not relevant - Log gist: ## Description When mirroring e.g. a Github repository that has an older, not the current commit tagged v0.1 and a release created, no release will show up on the mirrored repository. So we're creating a release of v0.1 within the mirrored repository. This will work, but any uploaded attachments will never show. However, if the **current** commit is tagged v0.1 and then the repository gets mirrored and we're creating a release called v0.1 within the mirrored repository, uploaded attachments will finally show up. There seems to be an issue with displaying release attachments when the release has the tag of an older (not the current) commit. This is a real issue as I can't seem to be able to create a release from a tag that has been set to an older commit (unlike on Github). Normal repositories might also be affected, but I have not seen it yet.

GiteaMirror added the issue/confirmed type/bug labels 2025-11-02 05:02:00 -06:00

GiteaMirror closed this issue

2025-11-02 05:02:00 -06:00

GiteaMirror commented

2025-11-02 05:02:01 -06:00

@chotaire commented on GitHub (Apr 8, 2019):

Finally I found what's causing this. Have fun with this one :(

@chotaire commented on GitHub (Apr 8, 2019): Finally I found what's causing this. Have fun with this one :(

GiteaMirror commented

2025-11-02 05:02:01 -06:00

@chotaire commented on GitHub (Apr 11, 2019):

It turned out that I am also having random issues if there were any untagged commits after tagging a release on the source repository. This is the only way I could reliably upload release attachments to a mirror repository:

Tag a release on the source repository, do not commit anything else thereafter.
Mirror the repository
Create a release with the same name as the source repository's tag on the mirror repository and upload the release attachments right away during the creation
After that you can continue committing on the source repository

@chotaire commented on GitHub (Apr 11, 2019): It turned out that I am also having random issues if there were any untagged commits after tagging a release on the source repository. This is the only way I could reliably upload release attachments to a mirror repository: - Tag a release on the source repository, do not commit anything else thereafter. - Mirror the repository - Create a release with the same name as the source repository's tag on the mirror repository and upload the release attachments right away during the creation - After that you can continue committing on the source repository

GiteaMirror commented

2025-11-02 05:02:01 -06:00

@stale[bot] commented on GitHub (Jun 11, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jun 11, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:02:02 -06:00

@lunny commented on GitHub (Feb 29, 2024):

I think this has been resolved. Let's close and feel free to reopen it if there is further information.

@lunny commented on GitHub (Feb 29, 2024): I think this has been resolved. Let's close and feel free to reopen it if there is further information.

GiteaMirror referenced this issue

2025-11-02 12:19:35 -06:00

[PR #3163] [MERGED] Fix repo links (#3093) #16808

Sign in to join this conversation.