Add clear distinction for User Namespace and Organization repos regarding what private means - #41810
Add clear distinction for User Namespace and Organization repos regarding what private means#41810deiga wants to merge 2 commits into
Conversation
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. |
|
@deiga I think this is a useful clarification, I just want to check with the rest of the team about terminology. |
…ding what private means
29b6a1b to
9a8a981
Compare
|
A stale label has been added to this pull request because it has been open 30 days with no activity. If you think this pull request should remain open, please add a new comment. |
|
@Sharra-writes Hows that checking going? :) |
|
@deiga Hello, and please accept my apologies for the late conclusion here After review, we're not convinced there's enough evidence to add this clarification. In general I'd encourage you to open a community discussion if it's something you'd like to pursue, as this helps us to understand how users are affected by specific articles. I'm going to close this out, but apologies again for the late reply, and sorry this isn't the answer you were looking for |
|
@subatoi Sure, I understand the decision. Thanks for letting me know 🙏 |
Why:
The current description of
privaterepositories can be unclear that "Member privileges" can grant access to all membersCloses:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Update docs for
privaterepos in GHEC OrganizationsCheck off the following: