better way to look at the more recent revision from `alembic history` output

[ChannyClaus]

Describe the use case

alembic history currently prints out the history of revisions to STDOUT in reverse-chronological order. personally as a user, i am a lot more interested in the recent revisions than the initial one and it can be not particularly ergonomic to have to scroll up to look at the recent commits.

Databases / Backends / Drivers targeted all of them?

Example Use

included in the use case.

Additional context

i think there can be two different ways to go about implementing this:

• we could add a flag --reverse to reverse the output, although this might be of relatively small value since tail -r on macos or tac on linux would achieve exactly the same via piping (unless alembic history output decides to add a header or something)
• the better way, i think, is to make it scrollable via less-like interface like git log does by default. since the output stays exactly the same, this should be backwards-compatible while achieving the goal of allowing the users to look at the most recent revision with no extra effort beyond just typing alembic revision.

Have a nice day!

[CaselIT]

Hi,

I think this could be useful. The first option seems easier to implement, unless the python stdlib has a way of emulating a less like interface.

Regarding the name of the flag I think something like --chronological would be clearer