Allow forks to change visibility to match upstream repository visibility

[mlima-gh]

Select Topic Area

Product Feedback

Body

I'm trying to change the repository visibility on forked repository.
After changing the upstream repository visibility from internal to private, the forked repo visibility maintains internal visibility and can't be changed to private.

Recreating or detaching the repo would not transit secrets, actions history, user association, github app installation, package permissions, etc.

I would expect to be able to change the visibility of a fork network, be it automatically or manually.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[queenofcorgis]

@mlima-gh welcome to the GitHub Community! Thanks for sharing this feedback and including so many helpful details on how you troubleshooted. The bot message above has more details on what to expect now that you've submitted. Hope to see you around the community 😃