+[2016-08-27T16:59:00Z]graphitemasterinstead of using the bug tracker +[2016-08-27T17:02:29Z]mikeymike If i wanted to work on an existing project, do I fork it and create and work in a new branch, or work in the main branch itself of my cloned repo? +[2016-08-27T19:11:05Z]dcfixso - I have a flask/bootstrap project in production and I'm going to migrate to webservices/reactjs. I may have to do some changes in prod while doing the refactoring. What's the "best" way manage my repo? Fork? Tag? New Project? +[2016-08-27T19:24:37Z]Caelumwhen you have a file in a gist with very long lines, any way to display the file with wrapping without breaking up the lines? +[2016-08-27T19:25:42Z]Caelumfor example, in this gist I just made: https://gist.github.com/rkitover/5453d1fda6f6f69015c0fd9ee2febfb4
+[2016-08-28T06:49:13Z]antipsychiatryHi +[2016-08-28T09:34:04Z]SopaXorzTakerWhile browsing the DMCA takedown repository, I noticed that a deleted gist with leaked keys is still present in the Web Archive: http://web.archive.org/web/20160624123555/https://gist.github.com/anonymous/{REDACTED} +[2016-08-28T09:39:17Z]ZarthusSopaXorzTaker: none of us are github staff here, but it's up to $someoneelse to change their keys to prevent others from using it +[2016-08-28T09:39:29Z]Zarthusthey will probably remain forever on the internet, that's just how it works +[2016-08-28T09:39:39Z]FTTC^