+[2017-04-30T17:24:39Z]a_p3rson|DHey y'all, need some advice for doing PRs and whatnot. I'm working on an issue for a repo, which doesn't really have any good branches to speak of. What I've been doing is forking the repo, then creating a branch from master to work on that issue. When I fixed it, I'm wondering if I should merge the issue branch and master in my copy of the repo, and then submit the PR (master to master), or submit the PR without a merge to master (i.e +[2017-04-30T17:25:32Z]a_p3rson|DI did the former, but now I'm thinking that if I want to work on another (unrelated) issue before that PR gets handled, I'm not going to be able to merge to master in my copy without borking my initial PR. +[2017-04-30T22:45:41Z]preactionktechmidas: no staff are in here to my knowledge, but no, that is absolutely inappropriate and you will get banned for it +[2017-04-30T22:46:30Z]preactiona_p3rson|D: you should always submit PRs from a branch in your repo. that way you can have multiple open PRs that don't affect one another +[2017-04-30T22:47:06Z]preactiona_p3rson|D: when one PR is merged to their master, you rebase your other PRs so they can be applied
+[2017-05-01T05:52:55Z]kafnjr#GeekBlogTV +[2017-05-01T15:31:55Z]FrozenFireAnyone know of an existing Slack integration that will send private messages to people on Slack when they receive a request for review on a PR? +[2017-05-01T16:15:53Z]hardenedappleIs there any way to setup default directory listing on github.io pages? i.e. navigating to username.github.io/subdirectory shows files in that directory instead of a 404 page. +[2017-05-01T18:47:47Z]preactionhardenedapple: no +[2017-05-01T18:48:03Z]preactionhardenedapple: there are likely jekyll plugins or hugo plugins that will do that though