Enforce Merge Request branch workflow

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Description

Currently, Merge Request branch workflow doesn't prevent creating an MR from unwanted branches to the target branch.

For example, I have the following:

**Branch name pattern "**develop/*" redirect to Target branch "main"

Branch name pattern "feature/*" redirect to Target branch "develop"

Then, as a Developer, I create an MR from feature-1, the MR defaults the target to "develop" branch, but I can easily change that target to "main" again.

Proposal

Make this redirection enforced for certain roles.