That’s a wild find. I can’t believe a simple GitHub issue could end up leaking private repo data like that.