-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unique Constraint error when renaming a branch #30428
Comments
lafriks
pushed a commit
that referenced
this issue
Apr 12, 2024
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Apr 12, 2024
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Apr 12, 2024
lunny
added a commit
that referenced
this issue
Apr 12, 2024
lunny
added a commit
that referenced
this issue
Apr 12, 2024
DennisRasey
pushed a commit
to DennisRasey/forgejo
that referenced
this issue
Apr 15, 2024
…eleted but exist in database Fix go-gitea/gitea#30428 --- Conflict resolution: trivial and move test to own subtest run directly after `Normal`. (cherrypicked commit 9466fec879f4f2c88c7c1e7a5cffba319282ab66) (cherry picked from commit db39b8f)
DennisRasey
pushed a commit
to DennisRasey/forgejo
that referenced
this issue
Apr 15, 2024
…eleted but exist in database Fix go-gitea/gitea#30428 --- Conflict resolution: trivial and move test to own subtest run directly after `Normal`. (cherrypicked commit 9466fec879f4f2c88c7c1e7a5cffba319282ab66)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
When renaming a branch to a branch name that was deleted before, a 500 error occurs with
An error occurred: RenameBranch, Error 1062 (23000): Duplicate entry '2118-Test123' for key 'UQE_branch_s'
Steps to reproduce
--> Error 500 with above mentioned error.
Gitea Version
1.21.10
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?
Binary from downloads
Database
None
The text was updated successfully, but these errors were encountered: