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

Closed
Open
Created Sep 30, 2014 by Administrator@rootOwner

Protected master branch prevents developer from pushing to wiki repo but not editing from wiki web UI

Created by: bbodenmiller

It appears that protecting the master branch prevents a developer from pushing to the master branch of the wiki repo (as implemented at https://github.com/gitlabhq/gitlabhq/blob/master/lib/api/internal.rb#L18-L24) however the user still is able to edit the wiki repo via the wiki web UI. Since the is no way to create a merge request for a wiki repo I think the wiki branch protection should be separate from the main repo branch protection. Many teams want the master code branch protected but want to allow edits to the wiki.

Related to https://github.com/gitlabhq/gitlabhq/pull/7915.

Assignee
Assign to
Time tracking