• Overview
    • Django
    • Next.js
    • Drupal
    • WordPress
    • Symfony
    • Magento
    • See all frameworks
    • Observability
    • Auto-scaling
    • Marketing Teams
    • Retail
    • Higher Education
  • Pricing
  • Featured articles
    • Switching to Platform.sh can help IT/DevOps organizations drive 219% ROI
    • Organizations, the ultimate way to manage your users and projects
  • Support
  • Docs
  • Contact
  • Login
  • Free Trial
Cover image

Renaming your project’s default branch

January 20, 2021
Chad Carlson
Chad Carlson
Manager, Developer Relations

When you create a new repository in Git, the “default branch”—the top-level branch, from which all subsequent branches split off from and merge back into—has always been named master.

This naming convention has carried into every product that’s built on top of Git. Platform.sh is no exception. New Platform.sh projects have master as the default production environment, and master was, until recently, hardcoded in certain places.

Sensitivity around the word “master” has led many in the developer community to adopt alternate default branch naming when possible. To support this movement, we’re proud to announce that you can now update your Platform.sh project’s default branch to something other than master, no matter your integration.

We’ve written a handy guide to take you through the process step by step:

If you have any questions about this update or the guide, feel free to contact us.

Get the latest Platform.sh news and resources

Related Content

Cover image

A beginner’s guide to Platform.sh

AboutSecurity and complianceTrust CenterBoard and investorsCareersPressContact us
Leader Winter 2023
System StatusPrivacyTerms of ServiceImpressumWCAG ComplianceManage your cookie preferencesReport a security issue
© 2023 Platform.sh. All rights reserved.
Supported by Horizon 2020's SME Instrument - European Commission 🇪🇺