https://iphone.artsy.net

• New repo, we could do the opposite to https://github.com/artsy/force-public, wherein we make our current repo private and use that for time-sensitive, or confidential PRs that need to be private but that we create a new repo ( with maybe even a new history? We'd have to probably crop the history for the private one too, they will leak into public for sure. ) that's public and we migrate over issues / milestones / CI to the public repo and use that from then on in.
• Existing Repo, read + sanitise all 2k issues, delete PRs leaking information, nuke git history for any file that's ever had a key in it, kill git history and open the current repo. Still create an eigen-private that we can use when something shouldn't be discussed publicly for whatever reason.