<!--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=338362) </details> <!--IssueSummary end--> ### Proposal Our release pipeline makes use of the [Push Options for Merge Requests](https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-merge-requests), but its lacking an Option for setting a [Merge Request Dependency](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_dependencies.html) Use case here is that we have an upstream project pipeline (with an MR) triggering a downstream project (creating an MR). As such, the downstream MR should not merge until the upstream merges. If I can pass the MR info from the upstream to the downstream, then I could additionally create the MR dependency with something like: ``` downstream-job: ... script: - ... - | git push --set-upstream origin "$BRANCH_NAME" \ -o merge_request.create \ -o merge_request.target=master \ -o merge_request.remove_source_branch \ -o merge_request.title="Release Candidate $RELEASE_VERSION" \ -o merge_request.dependency="$UPSTREAM_PROJECT_PATH/$UPSTREAM_MERGE_REQUEST_ID" ``` While this is our specific use case, this Push Option is flexible for many cases that involve creating an MR.