Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
delivery
delivery
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 355
    • Issues 355
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards
  • GitLab.com
  • GitLab Infrastructure Team
  • deliverydelivery
  • Issues
  • #1356

Closed
Open
Opened Nov 19, 2020 by Daniel Gruesso@danielgruesso🌀Developer

Change default branch name for GitLab.com instance

Problem to solve

As part of gitlab-org&3600 GitLab has worked towards providing users flexibility in choosing a default branch name for their repositories both at the instance-level as well as the group-level.

The GitLab.com instance still uses master as its default branch name, something we'd like to change to main in order to align with Git's new default branch name as well as the community at large.

Proposal

Change default branch name in GitLab.com admin settings from master to main so that all new repos created from GitLab will use the new default.

Users will be able to change this for their particular group if they so desire.

Edited Nov 19, 2020 by Daniel Gruesso
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-com/gl-infra/delivery#1356