{"push_id":1145386811,"size":1,"distinct_size":1,"ref":"refs/heads/fix-commit-order","head":"190a4f7117df1dffa5b0a012e752120a47f3e175","before":"529e625e5b80e421e0501b39c8a7ad3695fc6b11","commits":[{"sha":"190a4f7117df1dffa5b0a012e752120a47f3e175","author":{"name":"Philippe Pepiot","email":"c6b3a276cf9cf258fd6abc089ee35cdf0595d6bd@logilab.fr"},"message":"Handle benchmarks by commit revision instead of date\n\nCommits date are not necessary monotonic along the commit log,\nespecially if working with rebase workflow (instead of merge), this\ngenerate false positive or missed regression detection and unwanted\npeaks in the web UI.\n\nThis patch introduce a revision number as a drop-in replacement of\ncommit date. This revision number is an incremental number representing\nthe number of ancestors commits.\n\nIn the web UI the distance between commits is the number of commits\nbetween them. Commits can still be displayed by date using the date\nselector.\n\nCloses #390","distinct":true,"url":"https://api.github.com/repos/philpep/asv/commits/190a4f7117df1dffa5b0a012e752120a47f3e175"}]}
{"actor":{"display_login":"philpep"}}