[go: up one dir, main page]
Skip to content

Creating a new Merge Request from same source after a Merge Request accepted

Description

It is probably a long shot but my proposal would help us tremendously with our workflow and wanted to see if something like this would be possible. So in our workflow ( forking based ) a developer creates a merge request to our QA branch. Then it goes to Master user's for code review and acceptance then QA team has their own environment to test and verify the changes done by developer. Once they approve changes are good, then we send task back to developer to send another merge request to master branch ( our release candidate ). The reason we use this workflow to keep our release candidate isolated from unapproved, untested or not reviewed code base and is always ready to be pushed production once release date comes.

As you may notice it is a hassle for developer to keep track of branches and merge requests they sent, to send another from same branch to another upstream branch. So initially we thought we can use cherry-pick option on merge request page ( once accepted ) to cherry-pick it and create a new merge request to master. But this was not a good solution since it creates a new branch off that merge event that causes history and changes to get lost.

Proposal

My proposal is adding another button on same screen where we have cherry-pick option after merge request accepted, and basically replicates same process of creating a new merge request from same source branch to any branch on upstream ( similar to cherry-pick popup )

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.