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 you have some branches that begin with the same prefix followed by a "/", such as "feature/abc" and "feature/cba", right clicking the directory icon in the branches pane and clicking "Delete all", the resulting command gives an error: "Branch "feature/cba," is not selectable, this branch has been removed from the selection. The command will only delete the last branch in the list. Removing all the commas from the text field before clicking Delete fixes the problem.
Expected behaviour
The text field should not contain commas, so that the command succeeds without manual editing being necessary.
Screenshots
Did this work in previous version of GitExtensions
Yes, this worked in GitExtensions 2.51 using Git 1.9.4. I upgraded to Git 2.20 in order to use GitExtensions 3, and this introduced this problem for me.
@gerhardol Indeed, I was mistaken in which previous version I used. This works in GitExtensionsMod (2.53), a fork of GitExtensions which had merged that pane much earlier.
Current behaviour
When you have some branches that begin with the same prefix followed by a "/", such as "feature/abc" and "feature/cba", right clicking the directory icon in the branches pane and clicking "Delete all", the resulting command gives an error: "Branch "feature/cba," is not selectable, this branch has been removed from the selection. The command will only delete the last branch in the list. Removing all the commas from the text field before clicking Delete fixes the problem.
Expected behaviour
The text field should not contain commas, so that the command succeeds without manual editing being necessary.
Screenshots
Did this work in previous version of GitExtensions
Yes, this worked in GitExtensions 2.51 using Git 1.9.4. I upgraded to Git 2.20 in order to use GitExtensions 3, and this introduced this problem for me.
Environment
The text was updated successfully, but these errors were encountered: