+ [2016-08-15T19:53:45Z] gitinfo Rewriting public history is not recommended. Everyone who has pulled the old history will have to do work (and you'll have to tell them to), so it's infinitely better to just move on. If you must, you can use `git push --force-with-lease <remote> <branch>` to force (and the remote may reject that, anyway). See http://goo.gl/waqum
+ [2016-08-15T19:54:17Z] geri how does bfg cleaner connect to github?
+ [2016-08-15T19:55:24Z] jhass it doesn't
+ [2016-08-15T19:55:36Z] jhass it cleans your repo which you can overwrite your github repo with
+ [2016-08-15T20:06:55Z] Zarthus don't forget to change the sensitive data you leaked like passwords

message no. 146879

Posted by gitinfo in #github at 2016-08-15T19:53:45Z

Rewriting public history is not recommended. Everyone who has pulled the old history will have to do work (and you'll have to tell them to), so it's infinitely better to just move on. If you must, you can use `git push --force-with-lease <remote> <branch>` to force (and the remote may reject that, anyway). See http://goo.gl/waqum
+ [2016-08-16T01:32:57Z] ghost0x01 /HILIGHT nick
+ [2016-08-16T04:18:43Z] TML Is there an obvious way that I'm overlooking to inform github that a given branch on my fork of project X shouldn't be shown as a PR to the upstream?
+ [2016-08-16T04:20:58Z] zh_cool any one
+ [2016-08-16T04:21:56Z] TML zh_cool: My client suggests there are at least 480 "ones" here; whether or not any of them are answering questions ATM, I cannot sya.
+ [2016-08-16T04:22:00Z] TML nor can I "say"