Update note on organization membership visibility#42643
Update note on organization membership visibility#42643RamandeepSinghMakkar wants to merge 1 commit intogithub:mainfrom
Conversation
Clarify that private repositories and contributions remain inaccessible even if the organization is public on GitHub.
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
This comment was marked as spam.
This comment was marked as spam.
|
@RamandeepSinghMakkar I'm checking to see whether this is a common point of confusion, because I don't think it is, but we should have data on it. |
|
@RamandeepSinghMakkar Yeah, this isn't really something we get people confused about, so we're not going to accept this change. My colleague did point out that the intro is unwieldy, though. If you would like to shorten that for the sake of readability, we can definitely talk, but I'm going to close this PR. |
Clarify that private repositories and contributions remain inaccessible even if the organization is public on GitHub.
Why:
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following: