Zachary Ware <zachary.w...@gmail.com> added the comment:
That commit does not appear to be part of any branch of the main repository, and also appears to contain non-changes to every file in the repository. There are known private keys somewhere in Lib/test for use in tests. If you're referring to something else, please point it out a bit more clearly, preferably with a link directly to the file :) If you're talking about accidentally committing your own private key to your personal fork of the repo, your best course is probably to delete your fork and re-fork, though I don't know if that will actually make that commit go away forever; you'd need to talk to GitHub about that. ---------- nosy: +zach.ware _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42289> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
