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
A three column git merge conflict resolution view could be really useful. Currently, a single column is used, showing both incoming changes and changes from HEAD, as well as the eventual merged state.
An alternative to this would be to use three columns for the three different states, ie. incoming changes on the left, the state of HEAD on the right, and the output of the merge once changes are picked in the centre column.
A three column git merge conflict resolution view could be really useful. Currently, a single column is used, showing both incoming changes and changes from HEAD, as well as the eventual merged state.
An alternative to this would be to use three columns for the three different states, ie. incoming changes on the left, the state of HEAD on the right, and the output of the merge once changes are picked in the centre column.
Sublime Merge has a similar implementation.
The text was updated successfully, but these errors were encountered: