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
  • #5215

Closed
Open
Created Sep 29, 2013 by Administrator@rootOwner

[6.1] Bug with Merge Requests (forked project)

Created by: yapengwu

Summary

The merge request submit from a forked project stuck with wrong merge request id

How to reproduce:
  • project A, project A has a number of merge history
  • Developer fork project A, got project B
  • Developer create a new branch b-bug on project B
  • Developer submit a merge request, made mistaken that: source project B -> target project B (this one should be A, but developer made mistakes).
  • Gitlab generated merge request number 1 for project B
  • Developer fix this problem by editing this merge request, change the target project from B to A.
  • Project A complaints merge request number 1 has been closed, and shows the merge history 1. Developer can't modify the original merge request any more.
Assignee
Assign to
Time tracking