{"push_id":2406463005,"size":4,"distinct_size":1,"ref":"refs/heads/reapply_move","head":"16f31aa59fa640dd8cdced2191a1fdb75c9174c8","before":"288f0b3e544a2230e0da1636b7a4ce81c7379f30","commits":[{"sha":"89332cb8be139aff2e1449b709e450d0b2194b57","author":{"name":"James Graham","email":"01cfcc75cc77e42d1369b51ffa1aaa70069d0f46@hoppipolla.co.uk"},"message":"Return a single bug number from bug_number_from_url","distinct":false,"url":"https://api.github.com/repos/mozilla/wpt-sync/commits/89332cb8be139aff2e1449b709e450d0b2194b57"},{"sha":"34e0f12b4b79ec582c102420d593d84e412261f9","author":{"name":"James Graham","email":"01cfcc75cc77e42d1369b51ffa1aaa70069d0f46@hoppipolla.co.uk"},"message":"Handle commits which become empty after reapplying gecko patches.\n\nIf we land a gecko commit it may become empty after applying all the\nupstream changes. In this case we want to handle the exception trying\nto create an empty commit, revert back to the previous HEAD and continue.","distinct":false,"url":"https://api.github.com/repos/mozilla/wpt-sync/commits/34e0f12b4b79ec582c102420d593d84e412261f9"},{"sha":"118cd8cab26600b7dbb671ea6812dbeadcf85621","author":{"name":"James Graham","email":"01cfcc75cc77e42d1369b51ffa1aaa70069d0f46@hoppipolla.co.uk"},"message":"Look up sync by bug number, not URL","distinct":false,"url":"https://api.github.com/repos/mozilla/wpt-sync/commits/118cd8cab26600b7dbb671ea6812dbeadcf85621"},{"sha":"16f31aa59fa640dd8cdced2191a1fdb75c9174c8","author":{"name":"James Graham","email":"01cfcc75cc77e42d1369b51ffa1aaa70069d0f46@hoppipolla.co.uk"},"message":"Don't do a full-tree copy for landing prs after the first.\n\nWhen landing from upstream we currently copy the full tree for each PR\nand then attempt to reapply local commits. This has the advantage that\nit prevents us drifting too far from upstream without realising\nit. However it has pretty poor performance when the number of changes\nto be reapplied is large since for N PRs landed and M upstreamed changes\nit requires N*M operations.\n\nA faster approach with similar properties is to do a copy-and-reapply\nfor the first sync in a landing and then simply cherry-pick the\nremaining commits from web-platform-tests on top of that. Assuming\neach sync has a single commit this requires N + M operations, which\ncan be a significant improvement.","distinct":true,"url":"https://api.github.com/repos/mozilla/wpt-sync/commits/16f31aa59fa640dd8cdced2191a1fdb75c9174c8"}]}
{"actor":{"display_login":"jgraham"}}