3 ms·
At least on Bitbucket they're pretty explicit about the rules around forks. Creating a new private repository, you get the option to select [No Forks | Allow Fo
by pandler 9y ago
At least on Bitbucket they're pretty explicit about the rules around forks. Creating a new private repository, you get the option to select [No Forks | Allow Forks | Allow only private forks]. I don't see any kind of configuration like that on github.
- dfansteel 9y agoDoes that differentiation necessarily mean Bitbucket repos are immune to this problem?
- pandler 9y agoNo of course not. They're just a bit more explicit about the fact that permissions can persist across forks.
- incognito2375 9y agoThat is silly either way. Once you have a local copy you can just push that copy to any git hoster and thus make it public. Forking through their web ui is just a convenience feature.
- Bellyache5 9y agoGitHub gives you the option to allow/disallow forking for private repos at both the repo and organization level. https://help.github.com/articles/allowing-people-to-fork-private-repositories-in-your-organization/ https://help.github.com/articles/allowing-people-to-fork-pri...