Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-22261

Branch branch name does not align the suggested default branch name

XMLWordPrintable

      Issue Summary

      When creating a new repository, the default suggestion for the main branch is 'main'
      However, if you don't give it a name and after the repository is created the main branch name defaults to 'Master'

      According to this post, we should have moved away from the 'Master' terminology

      Steps to Reproduce

      1. Create a new repository
      2. Go through the normal steps (Select a workspace, give it a name, assign it to a project)
      3. Leave the "Default branch name" field blank
      4. Click Create repository

      Expected Results

      • The main branch should be named 'Main'

      Actual Results

      • The main branch is named 'Master'

      Workaround

      • Don't leave the "Default branch name" field blank. Give it a name

        1. create_repo.png
          create_repo.png
          39 kB
        2. main_branch_name_in_repo_settings.png
          main_branch_name_in_repo_settings.png
          60 kB
        3. main_branch_name_on_soource_page.png
          main_branch_name_on_soource_page.png
          29 kB

            [BCLOUD-22261] Branch branch name does not align the suggested default branch name

            Moby QT added a comment - - edited

            Can this get fixed as a straight up UI bug? 

            This is a clear functional failure, but it has no owner.

            Ignoring localization, its a one line change and a one test fix.

            (I could write a patch in Swift, if you just needed psuedo-code to prove my point).

            UPDATE:

            I just re-tested this, and it appears to behave as desired. 

            The last time I had created a repo (middle of last year), the problem was still occurring.

             

            Moby QT added a comment - - edited Can this get fixed as a straight up UI bug?   This is a clear functional failure, but it has no owner. Ignoring localization, its a one line change and a one test fix. (I could write a patch in Swift, if you just needed psuedo-code to prove my point). UPDATE: I just re-tested this, and it appears to behave as desired.  The last time I had created a repo (middle of last year), the problem was still occurring.  

            jake-aft added a comment -

            Is there any danger of getting this fixed.

            It's kind of a pain and just not necessary to have to mess about to get rid of the master branch.

             

            This happens all the time when you create a repo when you create a project in Jira. It's not that great UX or integration of Jira and Bitbucket and means I have a crap to do that I don't and shouldn't have to do to fix it.

            jake-aft added a comment - Is there any danger of getting this fixed. It's kind of a pain and just not necessary to have to mess about to get rid of the master branch.   This happens all the time when you create a repo when you create a project in Jira. It's not that great UX or integration of Jira and Bitbucket and means I have a crap to do that I don't and shouldn't have to do to fix it.

            Stijn added a comment -

            This is not a new ticket.

            Simply the same issue as reported in https://jira.atlassian.com/browse/BCLOUD-20212 which was closed even though getting "master" as the default branch name is still the default.

            Stijn added a comment - This is not a new ticket. Simply the same issue as reported in https://jira.atlassian.com/browse/BCLOUD-20212 which was closed even though getting "master" as the default branch name is still the default.

              Unassigned Unassigned
              ptrinh@atlassian.com Phil C
              Affected customers:
              15 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: