Skip to content

Commit 3b1e36f

Browse files
authored
docs: clarify member-only profile instructions
The docs do specify a private repository already, but this adds a callout to emphasize that this doesn't mean "not public" but rather that it has to have visibility of private -- internal is not enough.
1 parent b2802ec commit 3b1e36f

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,8 @@ The content of public `README.md` will appear on your organization's public prof
5656

5757
## Adding a member-only organization profile README
5858

59+
>[!NOTE] Private organization profiles must have "Private" visibility, not "Internal".
60+
5961
The content of a member-only `README.md` will be displayed in the member view of your organization's profile.
6062

6163
1. If your organization does not already have a `.github-private` repository, create a private repository called `.github-private`.

0 commit comments

Comments
 (0)