[GitHub] [incubator-openwhisk] markusthoemmes commented on issue #4532: [WIP] Initial commit for Scheduler
markusthoemmes commented on issue #4532: [WIP] Initial commit for Scheduler URL: https://github.com/apache/incubator-openwhisk/pull/4532#issuecomment-508519119 Well if you do it the latter way, you'll have a huge chunk to merge at some point anyway, right? I'd just push it all to master. That'll ensure it's all continuously tested, non disruptive and everything. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-openwhisk] markusthoemmes commented on issue #4532: [WIP] Initial commit for Scheduler
markusthoemmes commented on issue #4532: [WIP] Initial commit for Scheduler URL: https://github.com/apache/incubator-openwhisk/pull/4532#issuecomment-508364370 @style95 I'm not quite sure why we need an "official" branch for this feature in the repo itself. We have never done that to date. Can you not work on this feature on a fork and incrementally merge the bits into master? Merging this once it's done into master is kinda impractical anyway. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services