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

Closed
Open
Created Sep 16, 2013 by Administrator@rootOwner

Weird behaviour on accepting merge requests

Created by: azhuchkov

We are using manual merge when accepting Merge Request (to prevent additional merge commit creation). And I noticed:

  • when MR is unassigned, the MR become 'MERGED' automatically right after git push operation
  • when it is assigned to someone (e.g. me) I should manually push button 'merge' (despite of commits are pushed already)

Actually I don't know which behaviour is better (from one hand requests that have been merged should be displayed as merged, from another hand - when you push button you can remove source branch), but it looks like a bug.

Version: 6.0.2 87ee4030

Assignee
Assign to
Time tracking