Setting a system-wide default branch name
Administer Bitbucket Data Center
- Users and groups
- Advanced repository management
- External user directories
- Global permissions
- Setting up your mail server
- Integrate with Atlassian applications
- Connect Bitbucket to an external database
- Migrating Bitbucket Data Center to another server
- Migrate Bitbucket Server from Windows to Linux
- Run Bitbucket in AWS
- Specify the Bitbucket base URL
- Configuring the application navigator
- Managing apps
- View and configure the audit log
- Monitor security threats
- Update your license key
- Configuration properties
- Change Bitbucket's context path
- Data recovery and backups
- Disable HTTP(S) access to Git repositories
- Mirrors
- Bitbucket Mesh
- Export and import projects and repositories
- Git Large File Storage
- Git Virtual File System (GVFS)
- Enable SSH access to Git repositories
- Signed system commits
- Secret scanning
- Use diff transcoding
- Change the port Bitbucket listens on
- Lockout recovery process
- Configure secure administrator sessions (websudo)
- Proxy and secure Bitbucket
- High availability for Bitbucket
- Diagnostics for third-party apps
- Enabling JMX counters for performance monitoring
- Bitbucket guardrails
- Enable debug logging
- Scaling Bitbucket Data Center
- Add a shortcut link to a repository
- Administer code search
- Adding additional storage for your repository data
- Add a system-wide announcement banner
- Configuring Project links across Applications
- Improving instance stability with rate limiting
- Use a CDN with Atlassian Data Center applications
- Managing HTTP access tokens
- Manage keys and tokens
- Link to other applications
- Setting a system-wide default branch name
- Automatically decline inactive pull requests
- Secure Bitbucket configuration properties
- Data pipeline
- Monitor application performance
- Secure secrets configuration properties
On this page
Related content
- No related content found
The default branch for a repository is its integration branch for work. In pull request workflows, its where feature branches are targeted. It's also the first branch created in a new repository.
As a Bitbucket Data Center administrator, you can select how this branch is named by going to 
> Default branch name. On this page your options are:
| Option | Description |
|---|---|
| Use the Git default name | The name given to the default branch is based on the installed Git version:
|
| Set a custom default name | You can set an set an instance-wide custom default name for this branch. This custom name will be used instead of the Git name, and when a user creates a new repository they’ll see it prefilled in the default branch name field. They can then use this name, or enter a branch name of their own. |
When creating a new repository, users can leave the Default branch name field empty. If they do, the name given to the default branch will be the default branch name that has been configured for the instance.
Related content
- No related content found