Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,875
    • Issues 43,875
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,393
    • Merge requests 1,393
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #18488
Closed (promoted) (promoted)
Open
Created Jun 14, 2017 by Kyle James@kylifornication

Add configuration options for protected branches at the group and instance levels

This issue was promoted to an epic. It was too large in scope to consider for a single issue.

Old context

Problem to solve

Administrating and enforcing protected branch configurations on only a project level can take several hours of monotonous and repetitive work. Several apps and services have been created to help alleviate this paint point.

We have specific groups at Disney that have policies around their branching techniques. Currently these branching rules have to audited and applied manually. This takes hours.

Proposal

Extend functionality of protected branches so that they may be more swiftly configured and easily enforced when necessary.

Splitting the work

Groups and instance level work will take place in their own respective epics. Group level work will take priority for

References

User commentary

  • #18488 (comment 396921742)
  • #18488 (comment 449530647)
  • #18488 (comment 266451426)
  • #18488 (comment 215006605)

GitLab Service

Community contributed automated bot (GitLab Form)

Edited Sep 07, 2021 by Sam Kerr
Assignee
Assign to
Time tracking