Community
Participate
Working Groups
To reproduce: 1. Checkout one branch from the repository 2. Make changes, so that they conflict with the other branch (don't commit) 3. Go to git-repository.html and try to check out the other branch Result: * checkout branch call return "error: conflicting" [GOOD] * branch is not checked out [GOOD] * git-repository page is reloaded [NOT GOOD] * error in checkout is not shown, or maybe it's shown but immediately erased by status messages from reloading the page [BUG] Extected: * git-repository is not reloaded * you can read the error in status
I've check how it looks like on the old git repository page. The response code is 409 and an error should be reported, but UI status says OK, so this is bad. However in the new repository page even if the error was reported correctly it would be erased by status messages from reloading the page, so it looks like we have two problems to solve.
Fixed with Bug 370250.