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

Closed
Open
Created Jun 19, 2015 by Administrator@rootOwner

Merge Request action between two branches always defaults to Master branch as target branch

Created by: layer3switch

Gitlab 7.12rc2 Ruby 2.1.6

After creating merge request via Gitlab UI button, changing target branch other than master will always default to Master branch regardless of changing to other branch.

After creating merge request, manually changing target branch and saving the change is the only way to avoid merging to Master branch.

Our developers advised that either CSS/JS change to carry "target branch" be part of URI request during "Merge Request" API call.

Please advise.

Assignee
Assign to
Time tracking