[Feature Request] Reorder commits by drag and drop

[cdmihai]

Sometimes I want to reorder commits which I know are not conflicting. It would be super awesome if I could just drag and drop from the history view. Either a single commit, or a contiguous selection.

[DanPristupov]

You can reorder commits by drag and drop using Interactive Rebase.

For example right click on a some commit behind the active branch and select 'Interactive Rebase to Here' in the context menu.

[cdmihai]

You can reorder commits by drag and drop using Interactive Rebase.

That's my current way of doing it. But being able to just drag and drop commits and have Fork do the appropriate rebase in the background would increase the usability (fewer UI boiler plate actions and making the UI interaction the established drag-and-drop affordance that most apps use when something needs moving) of this use case.

[sglienke]

I really disagree - doing an interactive rebase and reordering commits thus rewriting history is not something you do all the time like moving around some files. So keeping it in the interactive rebase UI is fine imo

[cdmihai]

Actually I do it pretty often with non published WIP work. I usually keep all my WIP commits on top (by rebasing on master, never merging) and constantly move them around for various reasons, like when I need to have a feature branch that's composed of other feature branches (in which case I want to have contiguous commits for each composed feature).

Shared history is immutable, of course. Personal history is volatile, until it gets into final shape.

[Tawmy]

Reordering commits is something you'd usually only do during a rebase - and I believe it's important to keep that separated from, well, not being actively rebasing. Having that functionality available outside of a rebase could quickly lead to confusion and overall do more harm than it'd do good for this edge case.

[cdmihai]

Reordering commits is something you'd usually only do during a rebase

It would be implemented by a rebase in the background.

quickly lead to confusion

To eliminate confusion, dragging and dropping the commits can bring up the rebase window with the commits already reordered. All the user has to do is click the Rebase button.

[pavel-kolesnikov]

I really disagree - doing an interactive rebase and reordering commits thus rewriting history is not something you do all the time like moving around some files. So keeping it in the interactive rebase UI is fine imo

I do it all the time. Also, https://gitup.co/ does this pretty awesomely easy. When I prepare to push upstream sometimes I want to reorder commits to ease the review.