Our organization has a fair amount of “inner sourcing” among teams. For the most part the whole company is under one organization with a github team for each development team. It would be very helpful in facillitating multiple teams working in another teams repo’s if each team that needs to work in anothers space can create a fork under the team. This way they can maintain their own rights and access that isn’t tied to a specific users fork.
Hi @destumme ,
Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.
My team and I are also interested (if I understand the original poster correctly) in enhancing fork to allow forks within a single organization. We want the benefits of forking while not having to maintain two or more orgs.
My team is part of a GitHub enterprise setup with strict requirements for controlling access to our source code. We use GHE orgs in order to tightly control who gets access. Teams would like to fork a larger repo and work on their functional component separately in order to take advantage of the GitHub collaboration tools (e.g. issues) at the team scale. Splitting up the large repo is not an option available to us.
@belhfl, a second related requirement for us would be to control to which org(s) a repo can be forked - we want to prevent our org members from forking to places we haven’t approved as ‘safe and secure’ for our code. If we had this, we could go with the two org solution and manage to get by without the single org fork feature.
Let me know if additional info would help. Our teams want to use GitHub Enterprise very soon for our projects and we’re not sure how we could make GHE work for us without one or both of these features.