{"action":"created","issue":{"url":"https://api.github.com/repos/Reviewable/Reviewable/issues/253","repository_url":"https://api.github.com/repos/Reviewable/Reviewable","labels_url":"https://api.github.com/repos/Reviewable/Reviewable/issues/253/labels{/name}","comments_url":"https://api.github.com/repos/Reviewable/Reviewable/issues/253/comments","events_url":"https://api.github.com/repos/Reviewable/Reviewable/issues/253/events","html_url":"https://github.com/Reviewable/Reviewable/issues/253","id":134802159,"number":253,"title":"Support dependent pull requests","user":{"login":"Artur-","id":260340,"avatar_url":"https://avatars3.githubusercontent.com/u/260340?v=4","gravatar_id":"","url":"https://api.github.com/users/Artur-","html_url":"https://github.com/Artur-","followers_url":"https://api.github.com/users/Artur-/followers","following_url":"https://api.github.com/users/Artur-/following{/other_user}","gists_url":"https://api.github.com/users/Artur-/gists{/gist_id}","starred_url":"https://api.github.com/users/Artur-/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Artur-/subscriptions","organizations_url":"https://api.github.com/users/Artur-/orgs","repos_url":"https://api.github.com/users/Artur-/repos","events_url":"https://api.github.com/users/Artur-/events{/privacy}","received_events_url":"https://api.github.com/users/Artur-/received_events","type":"User","site_admin":false},"labels":[{"id":127309078,"url":"https://api.github.com/repos/Reviewable/Reviewable/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":13,"created_at":"2016-02-19T08:13:32Z","updated_at":"2018-03-13T06:36:46Z","closed_at":null,"author_association":"NONE","body":"Some times, e.g. when refactoring a lot, it's very useful to make many pull requests which are dependent on each other instead of one large pull request. It's much easier for the reviewer if PR1 is rename \"A to B and C to D\" and PR2 is \"Fix bad code in B and D\". If you do this with Reviewable today, you will end up with the \"rename\" changes also in the review of PR2, which is not what you want. \n\nIt would be nice if you could create branch1 and branch2 for PR1 and PR2 where branch2 is based on branch1, and still only see PR2 code in the review of PR2.\n"},"comment":{"url":"https://api.github.com/repos/Reviewable/Reviewable/issues/comments/372561719","html_url":"https://github.com/Reviewable/Reviewable/issues/253#issuecomment-372561719","issue_url":"https://api.github.com/repos/Reviewable/Reviewable/issues/253","id":372561719,"user":{"login":"pkaminski","id":1646896,"avatar_url":"https://avatars0.githubusercontent.com/u/1646896?v=4","gravatar_id":"","url":"https://api.github.com/users/pkaminski","html_url":"https://github.com/pkaminski","followers_url":"https://api.github.com/users/pkaminski/followers","following_url":"https://api.github.com/users/pkaminski/following{/other_user}","gists_url":"https://api.github.com/users/pkaminski/gists{/gist_id}","starred_url":"https://api.github.com/users/pkaminski/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pkaminski/subscriptions","organizations_url":"https://api.github.com/users/pkaminski/orgs","repos_url":"https://api.github.com/users/pkaminski/repos","events_url":"https://api.github.com/users/pkaminski/events{/privacy}","received_events_url":"https://api.github.com/users/pkaminski/received_events","type":"User","site_admin":false},"created_at":"2018-03-13T06:36:46Z","updated_at":"2018-03-13T06:36:46Z","author_association":"OWNER","body":"This is steadily floating up the priority list:  I hear the demand, and it's a good fit for the new product direction of \"serious code reviews\".  That said, 1) there are still much higher priority things ahead of it that impact the core review experience, and 2) I'm concerned that GitHub will go ahead and implement this feature a couple months after I get around to it (like they did with multi-assignees) and cause me major migration headaches again.  So not right now... but a definite maybe in the future.\r\n"}}
{"actor":{"display_login":"pkaminski"}}