Hacker News Reader

Any time you make a private repo public it’s best to just copy that code into a new public repo and leave the private repo private. Otherwise have to audit every previous commit and every commit on every fork of your private code.

View on HN

If I understand the issue correctly if you make the original repo public any private forks from other users are also effectively public. Right?

You create a new repository, “git init” it and copy your files over to it and push your new repository to your open source repository.

Seems to be the case yes. And I guess that the authors of those repos will not get a notification of any sort.

Yeah that's fine but the issue is GitHub doesn't make it clear that you need to do this.

Reply on news.ycombinator.com