pub fn order(a: &str, b: &str) -> Option<Ordering>Expand description
How the version a of one issue stands to its version b: Greater when a is the later,
Less when it is the earlier, Equal only when every part is equal — and None when either
is not a token of this plugin, or the two cannot be put in order.
Two versions naming different repositories, different facets or different relationship counts are never ordered: a transfer, a label renamed, a field option renamed, a kind changed or a far end deleted says nothing about which reading came first, and a count that can fall — a deleted far end takes its events with it — orders nothing. Otherwise both times only ever move forward, so a later version holds neither earlier; one holding one of them ahead and the other behind is no version read after the other. When both times are equal and the comment counts are not, the version with fewer comments is the later: the one change that moves the comment count and nothing else is a comment deleted, because adding one moves the issue’s time.