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 creating a new branch within Studio using the 'Create a new branch' menu option, it will checkout the default merge branch first, then create the new branch. This is helpful and helps to avoid issues with developers inadvertently creating branches off feature branches that are not merged yet.
However creating a new branch in Git UI does not have this behaviour and will create a branch directly off a feature branch unexpectedly, which has caused issues with some of our developers who are still getting their heads around Git concepts and it's not realised what has potentially happened until a PR is submitted and unexpected commits are discovered during review.
Being able to create a new branch in Git UI has proven to be more attractive and noticeable to developers, who are otherwise doing a lot of Git tasks within the Git UI, compared to closing Git UI and going to a menu option.
IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2024.1 (Build 267_2U) Tue Apr 30 2024 16:04:37 EDT
The text was updated successfully, but these errors were encountered:
Calling this a bug since it's a consistency issue. Let's update the behavior to be:
In Basic Mode, creating a new branch via Git WebUI always uses the default merge branch as a basis, period.
Will file a separate enhancement request to allow selection of the branch.
When creating a new branch within Studio using the 'Create a new branch' menu option, it will checkout the default merge branch first, then create the new branch. This is helpful and helps to avoid issues with developers inadvertently creating branches off feature branches that are not merged yet.
However creating a new branch in Git UI does not have this behaviour and will create a branch directly off a feature branch unexpectedly, which has caused issues with some of our developers who are still getting their heads around Git concepts and it's not realised what has potentially happened until a PR is submitted and unexpected commits are discovered during review.
Being able to create a new branch in Git UI has proven to be more attractive and noticeable to developers, who are otherwise doing a lot of Git tasks within the Git UI, compared to closing Git UI and going to a menu option.
IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2024.1 (Build 267_2U) Tue Apr 30 2024 16:04:37 EDT
The text was updated successfully, but these errors were encountered: