+ [2015-06-04T21:16:18Z] gdoteof er rather, the gist that is embedded there
+ [2015-06-04T21:16:21Z] gdoteof it'
+ [2015-06-04T21:16:42Z] gdoteof s like... not correctly parsing out some of the stuff.. line 15, lines 22-24
+ [2015-06-04T21:16:50Z] gdoteof it's not wrapping them in any span tags even
+ [2015-06-04T23:55:04Z] VxJasonxV gdoteof: works4me

message no. 96753

Posted by lethosor in #github at 2015-06-04T20:21:16Z

the files are part of a separate repo, whose url can be obtained by adding ".wiki" after the repo name
+ [2015-06-05T07:30:53Z] Zevv Hi; when I make a release Github also offers automatic zip/tgz archives with all the sources. These are not autoconf-prepared like my release, which confuses my users. Is there a way to omit these automatic zips when releasing, and only offer the release file I make myself?
+ [2015-06-05T07:50:28Z] IntriR Hi all - is it possible to push new commits to a PR that has already been merged? Is this considered bad practice?
+ [2015-06-05T07:54:37Z] VxJasonxV IntriR: you can push to the branch, but the pull request won't update
+ [2015-06-05T07:54:41Z] VxJasonxV you'll have to open a new one
+ [2015-06-05T07:55:59Z] IntriR VxJasonxV: Thanks, appreciate it :)