Feature Request: Optional Approval Requirement for Forking Private Repositories #192938
Replies: 2 comments
-
|
💬 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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Subject: +1 for Granular Forking Controls This is a great shout. Right now, our only real option is to toggle forking "on" or "off" at the org level, which is a bit of a blunt instrument. An approval gate would be the perfect middle ground—it lets us keep the collaborative spirit of forking without losing sleep over where our proprietary code is being cloned. The audit log idea is also a massive win for compliance. Hope the team considers this! #ProductFeedback #Security #Governance |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Product Feedback
Body
Hi GitHub team,
I’d like to propose a feature enhancement for private repositories.
Problem
Currently, collaborators with access to a private repository can fork it without requiring explicit approval from the repository owner. While this supports collaboration, it can be limiting in cases involving sensitive, proprietary, or early-stage codebases that require tighter control over duplication.
Proposed Feature
An optional setting for private repositories that requires owner/admin approval before a fork is created.
Suggested behavior
Why this helps
This would provide a useful middle ground between collaboration and stricter access control.
Thanks for considering this idea.
Beta Was this translation helpful? Give feedback.
All reactions