+ [2017-05-18T18:24:49Z] Insti but PR2 ends up containing all of PR1 :/
+ [2017-05-18T18:25:32Z] Insti Is there a way to only submit PR1--PR2 and have github report a merge conflict until PR1 is merged?
+ [2017-05-18T22:30:35Z] ayee like I'm pushing up changes to my branch, and I want to take notes on those changes as I do them, before the PR
+ [2017-05-18T22:30:53Z] ayee after say 3 days of work and a bunch of notes about why I did various things, I do the PR and all my notes are shown as part of the PR
+ [2017-05-18T22:31:15Z] ayee (without needing to do inline comments, since some of my notes are things like... this function wasn't being used anywhere so I deleted it, as an example)

message no. 169091

Posted by Insti in #github at 2017-05-18T18:23:46Z

What is the best practice when you want to make a new pull request that builds on a pull request that is not yet merged?
+ [2017-05-19T02:28:53Z] Jonno_FTW if I have my fork, how can I merge in code from the original repo?
+ [2017-05-19T05:04:06Z] sparkshift ok so what is this place exactly?
+ [2017-05-19T07:44:42Z] tobiasvl sparkshift: this place? the IRC channel? or github
+ [2017-05-19T08:12:19Z] ZSky Hi!