Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46,616
    • Issues 46,616
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,523
    • Merge requests 1,523
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #741
Closed (moved) (moved)
Open
Issue created Jun 29, 2016 by Sid Sijbrandij@sytsesDeveloper

Clone MR

As a developer working on solving a bug that occurs in multiple (release) branches I want to clone the MR.

This to ensure we have a trial of solving the bug in all relevant branches.

How to use:

  1. You have an existing MR (feature1 => master)
  2. Press the 'clone MR button'
  3. Select the branches you want to clone it to (release1, release2)
  4. Two new MR's are created (feature1 => release1 and feature1 => release 2) with a link back to the original MR and original issue
  5. Merge the different merge requests (can maybe automerge if it is a clean merge)
  6. The original issue now contains linked to all MR's, showing in which releases it was resolved

/cc @JobV @dzaporozhets @markpundsack

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited Aug 04, 2022 by 🤖 GitLab Bot 🤖
Assignee
Assign to
Time tracking