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

Closed
Open
Created Aug 18, 2016 by Administrator@rootOwner

the developers still can push code to the remote server even though the remote branches are protected and the option 'develop can push' is not selected

Created by: elainewu03

As what i described in the title, the developers still can push code even though the branches on remote server are protected and the option 'develop can push' is not selected. Is there anyone who ever got the same problem before?

Additional info: I setup custom hook with pre-receive and rules works as i expected. I am not sure if it has any impact on the configuration of protected branch and the setting of whether develop can push or not. version info: GitLab Community Edition 8.9.5

I plan to apply code review in my team, now the plan is blocked by this problem. :-(

Assignee
Assign to
Time tracking