Bug Report: PR Status Not Updating to Merged During High Traffic Periods

[Kumaresansyncfusion]

Description

Description:
During high traffic times, pull requests (PRs) that are merged without direct merge access do not update their status from "Open" to "Merged" in Gitea. This leads to confusion and inaccurate PR status tracking, especially under load conditions.

Steps to Reproduce:

Create a PR in Gitea during peak usage hours.
Merge the PR using a user without merge permissions (via admin override or API).
Observe that the PR status remains "Open" even after the merge is successful.

Expected Behavior:
The PR should automatically and immediately update to "Merged" once the merge is completed, regardless of traffic load or user permissions.

Actual Behavior:
The PR stays in the "Open" state during high traffic periods, causing discrepancies in PR status and potential confusion among team members.

Gitea Version

1.24.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Docker

Database

PostgreSQL

[lunny]

Hm, maybe we need a new merging state because the merging is not in a transaction.