Better Delete Branch Warning
When we delete a branch, we get the "destructive operation" warning.
However, there is a difference between deleting a branch that has commits that are not in another branch and deleting a branch that doesn't (has been merged).
SourceTree distinguishes these two cases. If you try to delete a branch with changes that haven't been merged, you get a warning. If you try to delete a branch with no unique changes, you don't get a warning.
I would prefer similar functionality in GitKraken. Either that or have a warning for both, but make the message different so it is clear whether or not you are losing commits. It's "more destructive" if you delete a branch with commits that haven't been merged.
Comments: 1
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
22 Apr
DylanIt's kind of insane this is not a thing - this is really bad design, and especially awful for users who rely on GitKraken *because* they aren't super-familiar with git. It would be super easy to change this flow. Exactly as shown, if a branch is already safely merged essentially a deletion is not a big deal.
Super puzzling that you'd get an strong-sounding warning for what is a nearly harmless operation...