Branches list page shows "NaN Commits" #14004

Closed
opened 2025-11-02 10:59:48 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @Zettat123 on GitHub (Jan 16, 2025).

Description

image

https://demo.gitea.com/Zettat123/test/branches

Gitea Version

1.24.0+dev-176-g4d399e717d

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

demo site

Database

None

Originally created by @Zettat123 on GitHub (Jan 16, 2025). ### Description ![image](https://github.com/user-attachments/assets/fadfc288-a5ac-404e-a6ec-e995de48d27b) https://demo.gitea.com/Zettat123/test/branches ### Gitea Version 1.24.0+dev-176-g4d399e717d ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? demo site ### Database None
GiteaMirror added the type/bug label 2025-11-02 10:59:48 -06:00
Author
Owner

@yp05327 commented on GitHub (Jan 16, 2025):

It seems like a UI bug, as it is right in home page. Maybe some ctx data is missing.

@yp05327 commented on GitHub (Jan 16, 2025): It seems like a UI bug, as it is right in home page. Maybe some ctx data is missing.
Author
Owner

@kemzeb commented on GitHub (Jan 16, 2025):

Running git bisect, it looks like this was caused by #33242

@kemzeb commented on GitHub (Jan 16, 2025): Running `git bisect`, it looks like this was caused by #33242
Author
Owner

@wxiaoguang commented on GitHub (Jan 16, 2025):

-> Fix incorrect ref usages #33301

@wxiaoguang commented on GitHub (Jan 16, 2025): -> Fix incorrect ref usages #33301
Author
Owner

@wxiaoguang commented on GitHub (Jan 16, 2025):

Running git bisect, it looks like this was caused by #33242

Because I have a plan to clean up all legacy unclear code -- even if there could be some regressions on the dev branch

image

@wxiaoguang commented on GitHub (Jan 16, 2025): > Running `git bisect`, it looks like this was caused by #33242 Because I have a plan to clean up all legacy unclear code -- even if there could be some regressions on the dev branch ![image](https://github.com/user-attachments/assets/144207d4-7642-45dd-83fc-1ae009508d2a)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14004