Support member-only organization profile with internal visibility on .github-private repo #213379
Replies: 3 comments 2 replies
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
Thanks for flagging this, and for opening a docs issue. I'm not GitHub staff, so this is a +1 with some practical notes. The mismatch As you describe it:
Both can't be true for the same repository, and each page has a different requirement. If one is wrong, the docs fix is the simplest outcome. If both are correct, then the two features have conflicting requirements, and that is the product gap you are describing. Why your suggested fix makes sense An organization uses one A possible workaround while this is open (untested)
Helpful details for the docs issue
Added a 👍. If staff confirms which page is right, it would help to post the result in the docs issue, so other administrators find it. |
|
3 Useful Websites You Shouldn't Miss! AgeWise: https://agewise-life-lens.lovable.app/ ReelSave: https://reelsave-guide.hatchable.site/ Calculator Hub: https://calculator-net-hub.netlify.app/ |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
Body
The Creating a repository for your enterprise governance documentation states that the
.github-privaterepo can be eitherinternalorprivatevisibility.However, the Adding a member-only organization profile README states that the
.github-privaterepo must beprivatevisibility for the profile to load.Ideally, the member profile would load when the repo's visibility is
internal. Doing so would allow organization members to view the copilot settings and also provide the members only profile.I've created this issue to update the documentation.
However, I would like to suggest the actual fix is to allow the members only profile to work with
internalvisibility.Thank you!
All reactions