Multiple Merge Requests

[hirnschmalz]

Let me first describe our workflow

• Client creates an issue
• Developer creates a feature branch
• Coding/fixing in the feature branch
• Changes in the feature branch are pushed
• Changes are merged to the staging branch which causes deployment to a staging environment
• Client reviews the changes
• Changes are merged to the main branch which causes a deployment to a live environment

So for me, it would be absolutely fantastic if I could create multiple merge requests (in my case one for staging and one for the target branch defined in the GitButler project settings) for each branch.

I just created this issue to maybe start a discussion if this feature would be useful for others too.

[Byron]

Thanks a lot for sharing your workflow, it's very helpful and much appreciated!

While supporting multiple merge requests per branch would be ideal, a simpler version of this could be if it was possible to disassociate a merge request so that a new one can be created. There is an additional complication of having a very fixed target branch, so creating a merge request against multiple different targets is currently very cumbersome as well.

The way this could work better is if there would be multiple workspaces and each workspace has its own target and its own set of applied branches. Fortunately, this is possible now even though the user interfaces are still hard-coded to a single well-known workspace.

Let me CC @krlvi so he can also keep this workflow in mind.