Enable custom editing of branch names in non-default configuration

[opherv]

Enable custom editing of branch names in non-default configuration

[OpherV]

Closing this because I think 5 years waiting for a reply is enough time

[OpherV]

The drop downs let you select from existing branches. "develop" doesn't exist in your project yet.

[uda]

Or in some cases, you haven't checked out the develop branch (it happened to me).

[rbellamy]

@OpherV - yeah so I should have spoken up sooner. And probably been more clear. Most other tools I've used with the git flow workflow would do whatever it took to make this work. So if there is no develop branch, create it. If the remote has one but local doesn't, go get it.

[OpherV]

tldr;
I spent a lot of time looking into this it but unfortunately it's non-trivial. Maybe someone has a good idea on how to tackle this.

The full scoop:

The git flow init command prompts for extra input to define the production branch, release branch, prefixes etc. If the production and release branches do not exist, it creates them. I couldn't find an easy way of inputting these extra parameters after the command was already issued, since the git4idea plugin I rely on doesn't really support something like that.

The way the git options work right now, as @avogler implemented it:

1 .Options dialog is confirmed
2. Prefixes in the .git/config are set to dialog options
3. git flow init -d is called (default options)
4. This in turn sets 'Develop' and 'Master' branches and creates them (because of the default options flag)
5. dev and prod branch names from dialog options are set in .git/config

This is kind of a workaround, but it works because the branches are already there.
It won't work for non-existent branch names, because the proper branches will not be created by the init function.

If we want to make this work with custom names, we'll have to find a way to input parameters into the git flow init prompt.

[OpherV]

I did some more research into this.
I think I can make it work with custom development branch name, but not with a custom production name. Even in SourceTree, when you try to insert a non-existing master branch name you get:

@rbellamy What do your other tools to when you try to init with a non-existing master branch?

[OpherV]

Update - this seems to work with git flow when initializing a repo with no branches, but not when initializing a repo with existing branches.

Which use case were you referring to?

[VFedyk]

So what about plans on this feature?

[OpherV]

There are definitely plans

[VFedyk]

Sounds good. Let's wait another year. ;-)

[OpherV]

Or... you can always clone the repo and give it a go :)

[VFedyk]

Yep.) I forgot where is my book "How to learn Java in 21 days". :D