Community
Participate
Working Groups
Double clicking on a tag or branch in Git Repository Explorer checks out what was double clicked on. This can be a very expensive operation and if it was inadvertent it can be a major nuisance. I've suffered this a couple of times in a project with 40K+ files and it might take several minutes to switch and another several minutes to switch back complete with any complications from auto build, staging etc. A double click should pose a confirmation dialog asking the user if they wish to continue to check out the branch. Alternately the double click should open the checkout branch dialog prefilled with the proper values. This would avoid inadvertent checkouts and make the operation explicit. Failing this, there needs to be a setting which disables checkout on double click, or which modifies it to a less painful action such as show history.
+1, I think this would make sense on double-click. Checkout via context menu should stay as it currently is. To implement this, OpenCommand needs to show a MessageDialog with a confirmation in case of a branch or tag. It should not show a confirmation dialog in case checkout already asks a question (checkout of remote-tracking branch), see BranchOperationUI.checkoutWillShowQuestionDialog.
Contribution from EclipseCon Europe 2013 Hackathon: https://git.eclipse.org/r/#/c/17866/ Thanks, Robin!
Fixed with e5fa5fd5d9be3082cac2932ab7981aa02357e770
