{"push_id":2476294760,"size":1,"distinct_size":1,"ref":"refs/heads/next_try_push","head":"7746aa309f89df94fe3955aa38b08944d883ea56","before":"d6436b5f0a2f104dbda4aaa993afc926b0c443f8","commits":[{"sha":"7746aa309f89df94fe3955aa38b08944d883ea56","author":{"name":"James Graham","email":"474ba67bdb289c6263b36dfd8a7bed6c85b04943@hoppipolla.co.uk"},"message":"Put logic to determine next try push for a PR in the sync\n\nCurrently we have various pieces of logic to determine whether a sync\nis in a ready state and to decide what the next step is to make it\nready. This PR does two main things:\n\n* Makes metadata_ready a readonly-property (with an override for\n  testing) so that the metadata readiness is determine by the PR state\n  rather than being explicitly set.\n\n* Adds a next_try_push method that schedules whatever try push is\n  required to make progress toward metadata_ready.\n\nAll the entry points are refactored to use this new logic and logic\nfor handling a chnage of status for the PR itself is made into a\nproper entry point rather than being a method.\n\nOne addition in this change is that we assume that try pushes are only\nvalid if the commits haven't changed since the try push was\nmade. Previously we assumed that the PR never changed after approval,\nbut that obviously isn't quite right. It does mean that in some cases\nwe will generate multiple try pushes for the \"same\" changes, if a\nbranch is manually squashed before being merged.","distinct":true,"url":"https://api.github.com/repos/mozilla/wpt-sync/commits/7746aa309f89df94fe3955aa38b08944d883ea56"}]}
{"actor":{"display_login":"jgraham"}}