+ [2015-08-31T22:24:50Z] cyrus_mc ideally development stays around for ever. You develop a new feature, merge it into production when tested and then continue to develop
+ [2015-08-31T22:24:59Z] tobiasvl all right. that's fine too
+ [2015-08-31T22:27:57Z] tobiasvl cyrus_mc: what you do after you've merged the pull request, when you want to do new work on development, you do "git rebase master"
+ [2015-08-31T22:28:17Z] tobiasvl and voila, you're not behind anymore. you integrate the production branch's merge commit into development

message no. 110076

Posted by vicatcu in #github at 2015-08-31T19:50:21Z

tobiasvl, so what's the right way to express that a new code base in its own repository has a heritage of another repo?
+ [2015-09-01T01:55:56Z] fahadash Can I modify an existing PR by adding a few newer commits to it?
+ [2015-09-01T01:58:28Z] thibaultcha fahadash Just push to the same branch
+ [2015-09-01T01:58:35Z] fahadash I just noticed
+ [2015-09-01T01:58:38Z] fahadash Github is amazing
+ [2015-09-01T06:14:07Z] VxJasonxV thibaultcha: it's better to encourage branching