Releases page don't show anything if git version less than 1.8

[lunny]

That means you have to upgrade your git version to more than 1.8

[bkcsoft]

As I've mentioned in a number of issue now, go-gitea/git really needs to panic() if the git-version is below a certain value 😂

[lunny]

So I think maybe we have to ask git 1.8 to let release work.

[bkcsoft]

@lunny I think we should have a test-suite for go-gitea/git so we can know what version we require. Guessing is never a good idea 😄

[lunny]

@bkcsoft You are right.

[strk]

As we're now accepting 1.7 this ticket should be reopened. I just got a report about releases missing, and I'll be happy to work on making a 1.7.10 compatible version if needs be.

[strk]

We need an automated test for the tag-extracting function in git module

[lafriks]

@strk check if this returns tags in 1.7 - https://github.com/go-gitea/git/blob/master/repo_tag.go#L133

[lunny]

@strk this has been resolved by @lafriks ' syncRelease PR.

[strk]

Where is the "syncRelease" PR ?
@lafriks tags can actually be extracted fine because I do see them in the "Code" tab, where you can select branch or tag to view...

[strk]

I found this PR, which was already included in 1.3.2 as far as I can tell: #2459 - was that the one ? It mentions syncing on PUSH, but we're not PUSHing to that repo, is that the needed trick ?

[strk]

I just pushed, didn't change a thing. Should I file a separate issue or will you re-open this ?

[lafriks]

@strk there was migration that synced all repos. Tags are resynced on tag push/remote delete

[strk]

the migration evidently failed. This task (sync from tags) looks really something that might benefit from having a command-line or GUI task to be run for re-synching

[strk]

now I also tried pushing tags, which succeeded but only populated the "releases" table with 3 over 4 tags I pushed. Maybe because the 4th tag was already known by the gitea-managed repository, so was not considered new (ie: something to add a release record for). I'm now stuck. I guess I could delete the tag and re-create it, but who knows how many such cases exist in our hosting, what's really needed here is a consistency checking routine that rebuilds the missing records, not just on "push" but on manual intervention. Do you agree @lafriks ?