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

Closed
Open
Created Mar 05, 2014 by Administrator@rootOwner

Gitlab Merge Issue

Created by: gerardmoroney

The issue is encountered when a Merge Request is created from a fork of a project.

  1. Create Merge Request with latest commit from fork master to original project master.
  2. Click Submit Merge Request button.
  3. Routed to error 500 page (see attached screenshot)
  4. The Merge Request is created despite the error, but it is empty when viewed on GitLab.
  5. When the Merge Request is pulled into the local repository of a machine you will see that it does contain a commit and is not empty. gitlaberror_screenshot
Assignee
Assign to
Time tracking