Branch name check on confidential issues always returns "available"
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
The following discussion from !175208 (merged) should be addressed:
-
@nickleonard started a discussion: (+1 comment) Existing MR/branch name
If I try to create an MR for a branch that already exists, it says "Branch name is available", then on the next screen it says an MR already exists for that branch and requires selecting a new branch. This seems to mean the branch name isn't available and the check isn't working correctly. This also happens with the default, where the default branch name doesn't update to a viable name, I assume because the check incorrectly passes.
This appears to be a bug in the legacy issue experience as well, so while not ideal to carryover bugs, we wouldn't have to resolve this for parity.