{"push_id":729871723,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"6bc782de75be6720aa31843e64f4cb57bfe01de9","before":"879dafb5b910b4c8e9fc37895495b4ddf2d58ef5","commits":[{"sha":"6bc782de75be6720aa31843e64f4cb57bfe01de9","author":{"email":"76349f49a6eee99156d916b8bdf84c707ac3ad66@hp.com","name":"James E. Blair"},"message":"Handle adding a job to a failing change during reconfig\n\nDuring live reconfiguration, if an item was either in a merge\nconflict state, or if it had jobs marked as skipped because of\na failing superior job in a job tree, any new jobs added to that\nitem during the reconfiguration would not have their state\nupdated to 'skipped'.  This would cause the item to stay in the\nqueue indefinitely.\n\nCorrect this by performing again the state updates that set build\nstatuses to 'skipped' after an item is re-enqueued.\n\nChange-Id: I96195cb9996b01075e3705b6cd89a9863528898e","distinct":true,"url":"https://api.github.com/repos/openstack-infra/zuul/commits/6bc782de75be6720aa31843e64f4cb57bfe01de9"}]}