{"action":"opened","issue":{"url":"https://api.github.com/repos/hail-is/ci/issues/19","repository_url":"https://api.github.com/repos/hail-is/ci","labels_url":"https://api.github.com/repos/hail-is/ci/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/hail-is/ci/issues/19/comments","events_url":"https://api.github.com/repos/hail-is/ci/issues/19/events","html_url":"https://github.com/hail-is/ci/issues/19","id":350554577,"node_id":"MDU6SXNzdWUzNTA1NTQ1Nzc=","number":19,"title":"CI should also heal GitHub status as well","user":{"login":"danking","id":106194,"node_id":"MDQ6VXNlcjEwNjE5NA==","avatar_url":"https://avatars2.githubusercontent.com/u/106194?v=4","gravatar_id":"","url":"https://api.github.com/users/danking","html_url":"https://github.com/danking","followers_url":"https://api.github.com/users/danking/followers","following_url":"https://api.github.com/users/danking/following{/other_user}","gists_url":"https://api.github.com/users/danking/gists{/gist_id}","starred_url":"https://api.github.com/users/danking/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danking/subscriptions","organizations_url":"https://api.github.com/users/danking/orgs","repos_url":"https://api.github.com/users/danking/repos","events_url":"https://api.github.com/users/danking/events{/privacy}","received_events_url":"https://api.github.com/users/danking/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-08-14T18:53:10Z","updated_at":"2018-08-14T18:53:10Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"In particular, if the target SHA changed but the latest GitHub status is still for an old SHA, we should send the latest status to GitHub. This can happen if a network fault or CI fault or CI restart causes GitHub to lose the notification that the CI received a `push` to the target ref."}}
{"actor":{"display_login":"danking"}}