Git shows commits in the interactive-rebase todo list (produced by git rebase -i) in the opposite of the usual order: the most ancestral commit (typically, the oldest commit) is shown first, not last.
Can I get it the other way around, for consistency with the usual sort order of git log? That is, I'd like the todo list shown in the default sort order of git log, and I'd like the todo list to still be understood by Git after I've edited it, without having to manually re-reverse it.
You can use a custom
sequence.editorconfig:It's easy to configure a reusable alias for that and use it:
Here's an approach that keeps the commented-out interactive-rebase hints on the bottom, and changes the line "top to bottom" to "bottom to top".