Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-8363

Creating branches with same name but with unique case sensitivity is not allowed.

XMLWordPrintable

      Steps to produce

      1. On terminal create a branch called ServiceOne using git command.
      2. Follow by add a file, commit the changes and push the commit to branch ServiceOne.
      3. Create a branch called serviceone using git command.
      4. Follow by add a file, commit the changes and push the commit to branch serviceone.

      Results
      Terminal produces error as following:

      Counting objects: 2, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (2/2), 236 bytes | 0 bytes/s, done.
Total 2 (delta 0), reused 0 (delta 0)
remote: error: failed to lock refs/heads/serviceone
To http://stash_admin@10.60.2.7:7990/stash/scm/st/02-si-tools.git/
 ! [remote rejected] serviceone -> serviceone (failed to lock)
error: failed to push some refs to 'http://stash_admin@10.60.2.7:7990/stash/scm/st/02-si-tools.git/'

      Expected Results
      To create another branch with same name that allows with unique name.

      Workaround
      Upgrade to Bitbucket Server ver4.1.X.

          Form Name

            [BSERV-8363] Creating branches with same name but with unique case sensitivity is not allowed.

            Adam Ahmed (Inactive) added a comment -

            Since it sounds like the bug somehow only affects older versions of Bitbucket Server, and since we have a Suggestion which will be likely to guide the future direction of our behavior, I'm closing this as Obsolete.

            I'm a bit surprised that there is a difference of behavior in 4.0 and 4.1, but I have not checked the difference myself.

            Please watch BSERV-8361 to track if/when/how we will prevent the creation of branches that differ only in case. If you have a compelling reason to allow branches that differ only in case, please add comments to that issue to help us understand the side effects of making this change.

            Cheers,
            Adam

            Adam Ahmed (Inactive) added a comment - Since it sounds like the bug somehow only affects older versions of Bitbucket Server, and since we have a Suggestion which will be likely to guide the future direction of our behavior, I'm closing this as Obsolete. I'm a bit surprised that there is a difference of behavior in 4.0 and 4.1, but I have not checked the difference myself. Please watch BSERV-8361 to track if/when/how we will prevent the creation of branches that differ only in case. If you have a compelling reason to allow branches that differ only in case, please add comments to that issue to help us understand the side effects of making this change. Cheers, Adam

              Unassigned Unassigned
              bannamalai Baskar Annamalai (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: