When I look at my commit history (/audit/?authors=<username>), the commits are not ordered chronologically. They appear to be mostly in order with some things out of order.
Description
Description
Revisions and Commits
Revisions and Commits
| rP Phabricator | |||
| D14013 | rPbce0698a0f5d Modernize Audit search engine | ||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | epriestley | T9279 Sort commit history chronologically | ||
| Resolved | epriestley | T9482 Problems in the "Commits in this Package that Need Attention" view |
Event Timeline
Comment Actions
To give more info: I'm sure the order makes sense for some use case (though I can't quite figure out what it is right now). The use case we have (in this scenario) is:
Often, we don't want to audit commits. We just want to see a person's commit history, perhaps as a way to quickly find something they did in the past. For this case it, providing an option to sort the commits chronologically seems like it would make finding old commits easier.
Comment Actions
It looks like they're ordered by internal ID, which is often correlated with commit date but not always the same. This is just the default behavior of queries, not an intentional behavior.
It's not trivial to order commits by ancestry, but we can order them by commit date pretty easily. This should be the same as (or, at least, similar to) ancestry in most cases (e.g., when users haven't been messing with commit dates using git commit --date).
Comment Actions
I pushed that to this server if you want to poke at it, let me know if I missed anything.
Comment Actions
T9302 has a followup bug on this, there may be an issue with the interaction between this query and Owners packages.