The commit listing is currently sorted by commit date. This is useful to see what work has been done most recently on branches, so concurrent work can be easily viewed and compared. But it's not so useful if you have many small, shallow branches, and you want to see the history of each in a cohesive list; or if your branch commits are out of order due to rebasing with --committer-date-is-author-date.

Could we have a search operator that sorts commits by branch (but still shows all/queried branches) instead of date? And have the branches ordered by most recent commit on their tip?

For example, say you have this structure:

   A
 / | \
B  C  D
|  |  |
E  F  G

And let's say each commit was created in the order A, B, C, D, E, F, G, with A being the oldest and G being the newest.

In OneDev, with the default newest-first commit sort, the commits will show up in the list like this:

G
|  F
|  |  E
D  |  |
|  C  |
|  |  B
| /  /
A

What would be nice would be to have an order like this, behind a search operator:

G
D
|  F
|  C
|  |  E
|  |  B
| /  /
A

So that G, as the most recent commit, has its full branch shown back down to A first. Then F, which is newer than E, shows its full history back to A. Then E. This is similar to what you'd get with git log --oneline --graph --branches or gitk.