Mention “previous“ commit in report

[nomeata]

When looking at a report, it is often not clear what commit the changes are relative to, especially when codespeed can get confused (#173). In order to debug that better, and also generally it would be nice to have that in the report.

Bonus points if it can be used for navigation. I could imagine two columns: One for the previous report (with summary), and one for the following (also with summary), if available. (Please ask if I did not make myself clear.)

[tobami]

That's true, a report should save the previous revision it is using as baseline, and show it below "revision->commit" on the right.

I am not sure I understood the second part though: what two columns do you mean? The "time in seconds" one? One for the current, one for the previous revision? And what do you mean by "also with summary"?

[nomeata]

Maybe I shouldn’t have said columns. I guess something like this would work, putting it in the “Revision” box:

Revision
Commit   4b74f6ca3fb962e9e9ccff1665f4d941763101e4
Date     July 4, 2014, 1:35 a.m.
Repo     https://github.com/ghc/ghc/
Summary  test foo +10%
Prevoius deadbeef  (no significant changes)
Next     beefdead (test foo up 10%)

What I meant with columns was something like the following, on top of the page:

← deadbeef  (no significant changes)               beefdead (test foo up 10%) →    

but either design is fine with me.