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
If you rename a remote branch through the Gitea UI, a pull request of this branch does not have its "pull from" branch renamed automatically. As a result, the PR becomes stale and no loger receives updates.
Maually altering the pull_request table record of this PR in the Gitea DB is the current workaround to revive the stale pull request.
Gitea Version
1.22.1
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?
Direct installation, not containerized
Database
PostgreSQL
The text was updated successfully, but these errors were encountered:
I tested on my local and I see that If you change the name of a branch through Gitea UI that has a pull request, the pull request is getting broken. But I am not sure it is intended situation or not 🤔
Description
If you rename a remote branch through the Gitea UI, a pull request of this branch does not have its "pull from" branch renamed automatically. As a result, the PR becomes stale and no loger receives updates.
Maually altering the pull_request table record of this PR in the Gitea DB is the current workaround to revive the stale pull request.
Gitea Version
1.22.1
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?
Direct installation, not containerized
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: