GitHub backend, commits not ordered with most recent on top, and commits from same push omitted about codespeed

[acdha]

Ah, I should correct the sort order for that - that's definitely wrong.

The other difference is really a philosophical one: I'm not sure whether we should be storing every commit or only the ones which are associated with a benchmark run. The Github API doesn't allow ranged queries but I could request every commit in a branch and filter the list.

[acdha]

acdha/codespeed@b7c2cfc3d9bb2eed4431 fixes the sort order issue

[tobami]

Re storing commits, I thought first of storing all commit logs in the Codespeed DB, as that allows among other things for faster response time. But that is really overkill. IMHO, it is a bad idea to replicate data that is best kept at the source. Data that belongs to the commits being tested does concern Codespeed (well, at least commit dates).

[acdha]

That's my view as well: while writing the github backend I found myself wondering how much it'd make sense to aggressively link to sites like github, bitbucket, google code, sourceforge, etc. which have some sort of UI and usually other niceties beyond just the commit logs.

[tobami]

Yeah, linking more aggressively does make sense. That way you can immediately go to a changelog's diff, inside the niceties of your repository UI.

[smarr]

And another thing I noticed to be different from the current git backend:

The git backend seems to show all commits from the range between the last data point in the DB and the point that is currently shown.
With the github backend only the latest commit is shown.

I noticed after switching to the github backend because we wanted the revision links in the view, but then the commits were gone.
Still, the links are highly appreciate and useful! :)

[smarr]

This should also be fixed with #40

[tobami]

I am closing it then. Thanks for pointing out.