Bitbucket capitalises origin GitFlow brance name

Question

When pushing a new branch to Bitucket, with a GitFlow prefix, it is capitalized on origin.

Any idea why and how to change that?

Checking out a new branch locally release/1.0 and hotfix/1.1.1 is changed to Release/1.0 and HotFix/1.1.1

macOS Catalina SourceTree 2.1 (I’m afraid I cannot update)

The left side of each of those arrows (`* [new branch] HotFix/5.0.4 ->` for instance) is your *local* name, which is clearly capitalized. Bitbucket has no influence over how you spell your names locally. — torek, Jun 20 '21 at 16:03
@torek check the local name, it is lowercase. We also checked the .git folder and it is also lowercase. — Tal Zion, Jun 20 '21 at 16:04
@torek But maybe the *local* git-flow extension does have an influence on how those git-flow branches are created though. — VonC, Jun 20 '21 at 16:05
@TalZion What is your OS, OS version, Git version and which git-flow extension are you using? The nvie one or the avh one? — VonC, Jun 20 '21 at 16:06
@VonC good point: something definitely uppercased the names somewhere. It wasn't Bitbucket, but what was it? — torek, Jun 20 '21 at 16:07
If you run `git ls-remote origin`, what list of branches do you see ? do you see the "lowercase" version of your branch names ? the "capitalized version" ? or both ? Same question with your local branches, when you run `git branch`. — LeGEC, Jun 20 '21 at 20:35
@TalZion I have edited my answer to suggest a course of action. — VonC, Jun 21 '21 at 19:16

VonC · Answer 1 · 2021-06-21T19:10:13.500

0

Strange, considering the own Atlassian blog post illustrating SourceTree using gitflow does not show any upercase letter:

Nor does the "Gitflow Workflow" BitBucket tutorial.

Check if gitflow-avh (installed with brew install git-flow-avh) works better.

My recommendation: start by renaming those local branches (check it does change the case in refs/heads/xxx), and see if the issue persists

edited Jun 21 '21 at 19:10

answered Jun 20 '21 at 13:01

VonC

1 Answers1