Issue with a bogus release


#1

Hi,
I recently migrated my Gogs installation to Gitea, and until now, it works fine.
However, in one single repository I have a strange issue: there should be 2 releases, but only 1 is shown and can be downloaded. What could be the reason with the missing release? I think it could be due to some missing entry in the database or something like that.

Are the files (.zip) for the releases stored something on disk? if so, could it be due to a missing file?

Can I fix the missing release, or is it possible to get rid of it somehow?


#2

I would guess that the count will be correct with https://github.com/go-gitea/gitea/pull/2389, this will be part of Gitea 1.2.0.


#3

Hi,
thanks. I have some other repos where I also have tags, but there are no releases displayed, which is correct. I think not every tag generates a release, does it?


#4

Correct, a release is based on a tag, but just the existance of a tag doesn’t build a release :slight_smile:


#5

:slight_smile: okay, and how is then a release distinguished from a tag?


#6

A release have to be created manually, and a release can get uploads/artifacts attached while a tag just provides the source.