+ [2017-06-02T23:40:29Z] SkullTech Yeah you're right :P Would be confusing for someone who'd want to look at the source code.
+ [2017-06-02T23:40:51Z] SkullTech Just an idea. Most probably won't move forward with it
+ [2017-06-02T23:42:21Z] SkullTech Github could provide native support for it though
+ [2017-06-02T23:42:31Z] SkullTech It's an useful feature IMO
+ [2017-06-02T23:52:18Z] preaction but a lot of work for them to implement

message no. 169363

Posted by SkullTech in #github at 2017-06-02T23:29:26Z

https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/
+ [2017-06-03T02:17:07Z] kingarmadillo hi, I'm looking to create a docker base image in one repo for use in a project repo. the project is nodejs so i want to keep the image updated with the packages required in the project repo. Is there a way to do this with github?
+ [2017-06-03T06:35:50Z] localhorse how can i fix this mess? i was trying to sync my fork that was 14 commits behind using GitHub Desktop, but then it showed 1 commit ahead and still 14 behind. but i did "compare" and it showed it can merge, so i created a PR and merged it via the "rebase" option on the PR. but now it created even more commits and now it says 10 commits ahead, 14 behind :(( https://github.com/Boscop/rust-vst2/commits/master
+ [2017-06-04T22:38:43Z] jeaye Has Github recently changed some GH Pages code to force site.baseurl to the repo name?
+ [2017-06-04T22:42:03Z] pouikpouik jeaye: what do you mean?
+ [2017-06-04T22:43:18Z] jeaye pouikpouik: Just recently, I started seeing an odd behavior where my jekyll-feed is producing urls like https://mysite.com/mysite.com/posts/my-post