Context
The Fork Git client provides a UI for managing GitFlow branches. Even after properly initializing GitFlow using git flow init (with correct base branches like master/main and develop), Fork fails to respect this configuration when creating:
• Hotfixes: not created from master or main
• Features: no longer systematically created from develop
• Releases: not automatically created from develop as expected
Problem Identified
When creating a GitFlow branch using the Fork UI (right-click → Git Flow → New [branch type]), the dropdown automatically selects the first branch in alphabetical order, instead of using the base branches defined during git flow init. This breaks the expected GitFlow behavior.
Consequences
• Hotfixes may be branched off development branches instead of production
• Features and releases may originate from incorrect bases
• CI/CD workflows may break if branches are not created from the correct starting point
• Git history becomes messy and error-prone
Steps to Reproduce
1. Run git flow init in a repository with proper GitFlow configuration
2. Open the repository in Fork
3. Try to create a new GitFlow branch (feature, release, or hotfix)
4. Notice that the base branch is pre-selected incorrectly (alphabetical order)
Expected Behavior
• Features should always be created from develop
• Hotfixes should always be created from master or main
• Releases should always be created from develop
• The Fork UI should honor the GitFlow settings initialized via git flow init
Suggestions
• Fix the default base branch selection to follow the GitFlow configuration
• Clearly indicate the selected base branch before confirmation
• Provide an option in the settings to always respect git flow init defaults
⸻
Context
The Fork Git client provides a UI for managing GitFlow branches. Even after properly initializing GitFlow using git flow init (with correct base branches like master/main and develop), Fork fails to respect this configuration when creating:
• Hotfixes: not created from master or main
• Features: no longer systematically created from develop
• Releases: not automatically created from develop as expected
Problem Identified
When creating a GitFlow branch using the Fork UI (right-click → Git Flow → New [branch type]), the dropdown automatically selects the first branch in alphabetical order, instead of using the base branches defined during git flow init. This breaks the expected GitFlow behavior.
Consequences
• Hotfixes may be branched off development branches instead of production
• Features and releases may originate from incorrect bases
• CI/CD workflows may break if branches are not created from the correct starting point
• Git history becomes messy and error-prone
Steps to Reproduce
1. Run git flow init in a repository with proper GitFlow configuration
2. Open the repository in Fork
3. Try to create a new GitFlow branch (feature, release, or hotfix)
4. Notice that the base branch is pre-selected incorrectly (alphabetical order)
Expected Behavior
• Features should always be created from develop
• Hotfixes should always be created from master or main
• Releases should always be created from develop
• The Fork UI should honor the GitFlow settings initialized via git flow init
Suggestions
• Fix the default base branch selection to follow the GitFlow configuration
• Clearly indicate the selected base branch before confirmation
• Provide an option in the settings to always respect git flow init defaults
⸻