Not all new git tags are listed as release

[dmolineus]

• Gitea version (or commit ref): 1.7.3
• Git version: 2.16.5
• Operating system: Linux (Cent OS 7)
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

I struggle with a strange behaviour. Since Gitea 1.7.0 it happens quite often that not all new tags are not listed on the release page. Sometimes they get added somestimes not. I have no idea why. It beheaves different on the same repository. Sometimes the tags are created sometimes not. Any idea how to find out what's going wrong?

[silverwind]

I too think something is up with inconsistent release generation. I have repos that generate a release every tag, but then I also have repos which fail to generate releases since at least half a year ago. Maybe it is related to force pushing over tags? @dmolineus do you also force-push over tags sometimes?

[dmolineus]

No, I don't use force-push over tags at the affected repositories.

[lunny]

@dmolineus have you found that on https://try.gitea.io?

Hi, I get no more updates to releases page after upgrading from 1.5.something to 1.7.4 in one repository. No hint, no idea.

master + next branch, simple git-flow style release from next, few commits, annotated tag; doesn't show up:

• https://try.gitea.io/transferkraM/github-issue-6237

[lafriks]

could you provide exact commands to reproduce that?

git checkout -b release/2 next
echo 2 > VERSION
git add --update
git commit -sm 'Version 2!'
git checkout master
git merge --no-ff --log release/2
git tag -a 2 -sm 'Version 2!'
git rebase release/2 next
git push origin master next --tags

Just added tag 3 non-annotated, no difference.

[zeripath]

I am highly suspicious that this is, yet another, escaping issue. Perhaps related to #6321.

[mrsdizzie]

This appears to be a conditional issue with the code that generates the releases and not only about particular tags themselves. If I 'migrate' the example repo here then the releases show up as you'd expect: https://try.gitea.io/mrsdizzie/github-issue-6237-migrate/releases

So it does see those tags as valid releases but isn't generating the releases when the tags are pushed in this case.

[HorlogeSkynet]

Running v1.7 branch and confirming this (strange) issue too...
Occurring with a simple repository, and two tags pushed.
They are effectively present, but no release has been automatically created.

I can run some tests if needed, bye 👋

[HorlogeSkynet]

Hey back, so I've naively reviewed the changes brought by v1.7.0, and it could be a regression added by #5609 (so ping @yasuokav & @HarshitOnGitHub).

Could anyone confirm this (or not) ?

Bye 👋

[lunny]

@HorlogeSkynet I put a comment there. https://github.com/go-gitea/gitea/pull/5609/files#r281054937