You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello
I noticed there is a mismatch in the commit view in all my repositories/organizations :
If you click on a commit, if it has been merged in a Pull Request, it shows on top left the number of the PR:
In my case, this number is always wrong :
it should display 2934 so it is higher than the correct one by one unit if the pull request 2935 is the next one.
I have another case where it should be 2907 but display 2909 (the 2908 PR has not yet been merged)
The Pull Request view has no problem, it displays always the correct commits (see below screenshot)
Gitea Version
1.18.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker
Database
PostgreSQL
The text was updated successfully, but these errors were encountered:
99rgosse
changed the title
[Display only] Mismatch between Pull Request Numbers in commit view
[Display only] Mismatch between a Pull Request Number in commit view
Jan 19, 2023
Description
Hello
I noticed there is a mismatch in the commit view in all my repositories/organizations :
If you click on a commit, if it has been merged in a Pull Request, it shows on top left the number of the PR:
In my case, this number is always wrong :
it should display 2934 so it is higher than the correct one by one unit if the pull request 2935 is the next one.
I have another case where it should be 2907 but display 2909 (the 2908 PR has not yet been merged)
The Pull Request view has no problem, it displays always the correct commits (see below screenshot)
Gitea Version
1.18.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: