Branches page still shows no. of commits ahead after merging to master branch #31472
Comments
|
I also noticed that when I merge a branch outside of Gitea into the default branch and push it to gitea, the branch is not marked as Included in the branch overview. This seems to be the same issue. |
|
I just upgraded to 1.22.1, this seems to be fixed now |
|
Unfortunately, after merging a PR, the problem is back again... |
|
This should be caused by #29577 |
|
So I guess the cache should be invalidated after merging? |
Yes. I will send a PR to fix it. |
This was referenced Jul 19, 2024
techknowlogick
pushed a commit
that referenced
this issue
Jul 19, 2024
Backport #31659 by @Zettat123 Fix #31599 Fix #31472 A branch divergence is counted based on the default branch. If the default branch is updated, all divergence caches of the repo need to be deleted. Co-authored-by: Zettat123 <[email protected]>
|
Closed by #31659 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
After upgrading from 1.21 to 1.22 I noticed the branches page shows merged branches with the same number of commits ahead as before merging. See screenshot for an example.
Step to reproduce: create a PR, merge it. Branches page will show the branch is merged, but the number of commits ahead is not 0.
Gitea Version
1.22
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Git Version
2.39.2
Operating System
Windows
How are you running Gitea?
gitea-1.22.0-gogit-windows-4.0-amd64.exe, downloaded from dl.gitea.com, running as a windows service.
Database
SQLite
The text was updated successfully, but these errors were encountered: