Complete `update-refs` support

[lishaduck]

Description

#2387 was marked as completed with a note to add our use cases for actual update-refs support.

Mine: I regularly write my code all on one branch, in small commits, but determine the branches divisions after I'm done writing a stack. Then I create the branches from the end, rebase on upstream, and move the branches where they belong with update-refs. Overcomplicated? Perhaps, but it's my workflow 🤷🏻‍♂️

Completely understand if it's not supported, but it's a shame cuz the rebase editor is really nice for that sort of work but I have to keep it off to make these sort of rebases. (It's still lacking for bulk work, I would love a multiselect, but that's much rarer for me)

[eamodio]

Have you tried the new rebase editor? It was only released a few hours ago. It supports update-refs, multiselect, bulk actions, etc

[lishaduck]

Have you tried the new rebase editor? It was only released a few hours ago. It supports update-refs, multiselect, bulk actions, etc

Not yet, no, but you closed the issue with:

Although in this version you can't move or remove update-refs directly -- they are attached to the commit itself and move along with it.

Which, as I wrote, is still a dealbreaker for me unfortunately (but very very glad to hear about multiselect though! I'm pretty excited to get to use that!)