4 ms·
But now it becomes a harder mistake to make. Creating a new repository is easy, but not so easy you would do it by accident. Importantly when this is discovere
by bluGill 3y ago
But now it becomes a harder mistake to make. Creating a new repository is easy, but not so easy you would do it by accident.
Importantly when this is discovered you can fire the person who did it, and they can't say it's was an accident, while the fork button to the wrong place is potentially an accident.
- masklinn 3y agoI’d say it becomes much easier: if you fork a private repository, you need to go through multiple layers of warning to move it to public. If you want a collaboration repository with forking disabled, public is the default.
- chrisfosterelli 3y agoYou can't accidentally share a private fork any easier than you could a new repo. If you try to make a private fork public in GitHub there is just a message that "For security reasons, you cannot change the visibility of a fork." As far as I know the article's example of 'a developer forks a private repo and makes it public' is not possible in github.