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

Closed
Open
Created 12 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Assign merge requests only to users that can handle them.

Closed

Assign merge requests only to users that can handle them.

Created by: nielsbasjes

When I make a merge request to a protected branch I'm able to select every user in the project as the person the MR is assigned to. Even if such a user does not have the rights to handle such a request.

I tried it by assigning a MR to a protected branch to someone with the Developer role. It worked and that user got an error that essentially says: "Only masters can accept MR".

I propose to limit the users that I can assign a MR to.

  • Unprotected branch: Only Developers and Masters
  • Protected branch: Only Masters

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: sroth80021

      We have this problem as well-- our current workaround is to give everyone Master role.

      Unfortunately, this also means anyone can do a force-push, which is a bit dangerous.

      By Administrator on 2012-10-26T13:36:50 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: sroth80021

      Sorry, please disregard my previous comment -- I misread your post. I thought you were proposing allowing developers to accept merge requests.

      By Administrator on 2012-10-26T16:33:35 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: kirantpatil

      +1

      By Administrator on 2012-10-31T10:52:16 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: senny

      Hey @nielsbasjes

      Thanks for your interest in GitLab ❤

      We don't use the Github issue tracker for feature requests. Please use http://feedback.gitlab.com/ for this purpose. Have a look at the contribution guidelines for more information.

      Also don't hesitate to use the support forum if you have further questions.

      By Administrator on 2013-04-24T05:46:04 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference: