Skip to content

Disable changing of target branch in new merge request page when a branch has already been specified

What does this MR do?

This MR prevents a user from changing the target branch inside a new merge request page if the target branch has already been specified (e.g. from the shortcut in the activity feed). A link to "Change branches" is provided to allow the user to do this properly.

Why was this MR needed?

If a user attempted to create a merge request from a shortcut with a pre-specified target branch (e.g. master), the dropdown would suggest that the user could change the branch. However, this did not actually work due to duplicate data elements (see #1830 (closed) for more details), and the target branch would always be set to the original, default branch. This would lead to confusion, potentially causing an improper merge request to be created.

What are the relevant issue numbers?

Closes #1830 (closed)

Screenshot

image

Merge request reports