The new Git default branch name
Blog post from GitLab
GitLab is implementing changes to adopt a more inclusive default branch name, transitioning from "master" to "main" in alignment with community feedback and wider industry practice. This change will be phased in across GitLab.com and self-managed users, with the first phase updating GitLab.com on May 24, 2021, and the second phase affecting self-managed GitLab as part of the major 14.0 release on June 22, 2021. This move follows Git's introduction of the init.defaultBranch configuration option in 2020, allowing users to set a default branch name other than "master," and reflects a broader effort to move away from terms with potentially offensive historical connotations. GitLab's existing projects will remain unaffected; however, new projects will adopt "main" as the default branch name, requiring users to update any hard-coded references in CI/CD configurations. The change aligns with similar shifts by GitHub and Atlassian, marking a significant step toward inclusivity in software development practices.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.