Merge ~cjwatson/turnip:log-by-date into turnip:master
Status: | Needs review |
---|---|
Proposed branch: | ~cjwatson/turnip:log-by-date |
Merge into: | turnip:master |
Diff against target: |
118 lines (+29/-3) 4 files modified
requirements.txt (+1/-0) setup.py (+1/-0) turnip/api/store.py (+16/-2) turnip/api/views.py (+11/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
William Grant (community) | code | Approve | |
Review via email: mp+295544@code.launchpad.net |
Commit message
Add start_time and end_time parameters to log API
This is useful for bounding the set of commits returned in cases where
we may not have a reliable stop commit.
Description of the change
When I was integrating git commits into Launchpad's merge proposal conversations, I initially thought about filtering by date on the turnip side, but ended up doing that on the Launchpad side instead since it was simpler. However, it can apparently happen that our idea of the stop commit isn't in the source repository, in which case we need a different way to bound the set of commits returned by turnip's log API.
I think the OOPSes I've seen are mainly a bug in Launchpad: we need to be requesting cross-repository diffs in a better way, and I'll work on that separately. Still, it doesn't hurt to attack this from multiple fronts.