One question from a UX point of view -- should Stash All Changes come after the "opens"? Generally, the way you have it follows our patterns, but I wonder in this case if the 2 opens are the much more likely actions. /cc @d13 @justinrobots

One question from a UX point of view -- should Stash All Changes come after the "opens"? Generally, the way you have it follows our patterns, but I wonder in this case if the 2 opens are the much more likely actions. /cc @d13 @justinrobots

Good point and would like feedback from @d13 and @justinrobots

It's a tough one to answer, because sometimes I'm committing my WIP stuff more frequently (in which case I would prefer Open Source Control on top) and sometimes I'm stashing more frequently (in which case I would prefer Stash All Changes on top).

Overall I find that I stash more often, as usually I'm writing stuff on main and end up wanting it on its own branch, or I need to switch context for a bit to test a PR before going back to my changes, so my vote would be to have Stash All Changes on top.

@eamodio Haven't heard any additional feedback on this (regarding the UX). Should we go ahead with the current ordering of the menu items and then rearrange them if needed once we get feedback after this lands?