You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i use gitflow init from console it suggests me to use 'master' branch for production releases and it make sense. But Gitflow Integration plugin suggests me to use 'develop' branch for both, production and next release.
I think we have to use default settings from original gitflow. Or atleast have ability to set these params in plugin settings.
The text was updated successfully, but these errors were encountered:
If you don't select "use non-default configration", you'll get two branches: develop and master, as you'd expect.
When you open a new git repo, without committing anything - you don't have any branches in the repo yet. So when you init git flow you get this dialog:
If you do commit something, the default branch is master (unless you renamed it) so when you choose 'use non-default configuration', and attempt to select from existing branches you get this:
Which makes sense, because you only have one branch present in your project.
When i use gitflow init from console it suggests me to use 'master' branch for production releases and it make sense. But Gitflow Integration plugin suggests me to use 'develop' branch for both, production and next release.
I think we have to use default settings from original gitflow. Or atleast have ability to set these params in plugin settings.
The text was updated successfully, but these errors were encountered: