Unable to move new file with same filename named by previous file in a folder
Summary
I have found a bug which makes no sense at all. In a folder, I renamed the file "file1" to a whatever name "file12". I created a new file "file1" and move to a folder (Folder/file1) then I got an error that someone edited the file the same time I did. I deleted "file12" and tried again but same error. This really make no sense. I don't have someone editing the files. Only me. When this problem is permanent, I must either delete the entire repo and create it again or only use the client like SourceTree to make changes. Luckily SourceTree works without any problem
Steps to reproduce (via the GitLab UI)
- Create a new repo project
- Create a new file "file1"
- Create a new folder "FolderTest"
- Edit "file1" and move to "FolderTest" (FolderTest/file1)
- Rename "file1" to "file12"
- Create a new file "file1" again
- Edit and move file1" and move to "FolderTest" (FolderTest/file1)
What is the current bug behavior?
Got an error "Someone edited the file the same time you did. Please check out the file and make sure your changes will not unintentionally remove theirs." when i tried to move the file with filename that was named by previous file in a folder. Click "the file" link returns 404 error
What is the expected correct behavior?
Be able to move the file with filename that was named by previous file in a folder without problem
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com