Compare release with other tagged versions not working

[kernie]

Description

Following scenario:

• Create a repo
• Commit und push something, create a tag, create a release in Gitea
• Commit und push something, create a second tag
• Go to the gitea web page -> Releases
• Choose the one release
• Click "Compare" with the second tag

It results in "No common commits. The tagged versions do not share a common history" (translated, I have it in German).

The link not working is: https://try.gitea.io/koobiedoodiedoo/TagCompare/compare/Rev01...Rev00

However, https://try.gitea.io/koobiedoodiedoo/TagCompare/compare/Rev00...Rev01 works as expected.

Gitea Version

1.19.0+dev-415-g82728a7ce, 1.18.3

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

No response

Operating System

Ubuntu 20.04

How are you running Gitea?

mysql DB, systemd, on virtual machine

Database

MySQL

[delvh]

Please click on the PR icon you see on the top left of the page, this should turn the comparison around.

[delvh]

The only thing we could think about is whether we swap around the comparison by default.
I'm not sure if the current approach, or the opposite is the correct comparison.

[kernie]

@delvh thanks for the hint with the symbol. I'm not a git expert, your answer implies that the forward comparison old<->new isn't possible at all? Only new<-> old?

[delvh]

I don't think it is.
As I mentioned, I'm not too familiar with the comparison mechanism, since we simply pass it down to git which handles that itself.
The problem is even more difficult as there are in total four different possibilities:
In addition to reversing the comparison, there is also a different comparing mechanism you can unlock by clicking on the … in your screenshot.
I always get confused which one will be correct, and simply try all combinations until I find the one that looks probable.

[GiteaBot]

We close issues that need feedback from the author if there were no new comments for a month. 🍵