From 3b1e36ff350d18c6c5b2df06a779338cd4683bfd Mon Sep 17 00:00:00 2001 From: Mark Bainter Date: Mon, 15 Dec 2025 13:28:48 -0600 Subject: [PATCH] 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. --- .../customizing-your-organizations-profile.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md index 48331a3066d3..94954b94a04d 100644 --- a/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md +++ b/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md @@ -56,6 +56,8 @@ The content of public `README.md` will appear on your organization's public prof ## Adding a member-only organization profile README +>[!NOTE] Private organization profiles must have "Private" visibility, not "Internal". + The content of a member-only `README.md` will be displayed in the member view of your organization's profile. 1. If your organization does not already have a `.github-private` repository, create a private repository called `.github-private`.