Should .github-private really be a public repo?

[Sleavely]

For a member-only README on an organization the docs state that you should create a public .github-private repo. It seems a bit counterintuitive.

docs/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md

Line 52 in 1473485

1. If your organization does not already have a `.github-private` repository, create a public `.github-private` repository. This action can be performed by any user that has write access to that repository.

(Since I'm not sure about the actual behavior I didn't want to file it as an Issue.)

[thispsj]

Hey @Sleavely ig you're absolutely right. .github-private should be a private repo because members can see private repos and a member only readme in a public repo makes no sense 😅

The docs are incorrect about this and need to be corrected. Ig the person who wrote the doc just copy pasted the instructions for .github repo and forgot to correct that.

Please mark this as answer if it resolves your query.