<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=353280) </details> <!--IssueSummary end--> I suggest to improve GitLab [Push Options feature](https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-merge-requests). Here's what I was trying to do in my Makefile: ``` publish!: git push --force origin $(BRANCH) \ -o merge_request.create \ -o merge_request.target=master \ -o merge_request.assign="$(USERNAME)" \ -o merge_request.label="to-production" \ -o merge_request.title="$(TICKET) $(FEATURE_NAME)" git commit --allow-empty -m "empty commit" git push --force origin $(BRANCH) \ -o merge_request.create \ -o merge_request.target=staging \ -o merge_request.assign="$(USERNAME)" \ -o merge_request.label="to-staging" \ -o merge_request.title="[staging] $(TICKET) $(FEATURE_NAME)" ``` Unfortunately even with `--force` and and empty commit it doesn't create second merge request, but instead shows me the link to the first one created. The reason for 2 MR creation is our flow - the staging one gets merged almost instantly after brief review. The production one will be around for a bit longer. Upd: just realized that the above setup changes target branch instead of creating new MR: