-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Mirror release commit count issue #13398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
this still holds btw, even with great improvements to the UI such as #13428 ("Tags cleanup"). |
Currently running Note that initially the issue was only pertaining mirrored repositories. I haven't come across your issue yet (looks like this is a regular repository, not a mirror), although that'd probably presume me reproducing the commit count etc. @conor-byrne Just out of curiosity, what happens when you tag a commit that's 256 commits behind current HEAD? How will Gitea display that? Smaller number (37<256<272) gets shown just fine |
Close as outdated. Please open a new issue if this happen again. |
Gitea version 1.14.0+dev-132-g8176ba657 built with GNU Make 4.3, go1.15.3 : bindata, sqlite, sqlite_unlock_notify
git version 2.29.2.222.g5d2a92d10f
Description
I believe the commit count in the release area of a mirror is off.
For instance while the release page of a
go-gitea/gitea
mirror shows there have been 0 commits to master sincev1.14.0-dev
, the Gitea version string (1.14.0+dev-132-g8176ba657
) says there in fact have been 132 commits to master.I think the latter is correct.
Screenshots
my instance:


try.gitea.io
The text was updated successfully, but these errors were encountered: