Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #1724

Closed
Open
Created Oct 17, 2012 by Administrator@rootOwner

merge request: error if merge request already exists

Created by: sroth80021

If I understand properly, Merge Requests are for branches (A ==> B) rather than for commits. I think this means the merge request is not so much for merging a specific static set of code -- it seems to be dynamic (for example, if branch A keeps getting pushed to, then the latest changes will get pushed to B, when the MR is accepted)

So if one does this sequence:

  • push A1, A2 to branch A
  • create MR from branch A ==> B
  • push A3 to branch A
  • accept MR

Then one will end up with A1, A2, and A3 pushed to branch B, even though A3 did not exist at the time the MR was created.

Presuming I understand correctly, then I dont think it makes sense to have two merge requests for the same pair of branches (A ==> B), since approving either would essentially perform the accept on both.

If this is the case, then it would be nice to get an error message when creating a MR from A==>B if an existing MR already exists from A==>B.

Assignee
Assign to
Time tracking