Hacker News new | ask | show | jobs
by KomoD 839 days ago
If I don't charge money, why would I keep the repo private.

Like your example in the video "Let's just say I'm a big-time content creator who does 10 YouTube tutorials a week, showing how to develop apps and I want to share the code with you but I'd also love to be in control of that code inside a private repo"

If I'm making YouTube tutorials and I want to share the code, why would I keep the repo private...?

And regarding "prevent cloning", how does that work?

If someone can see the code, nothing stops them from taking it?
1 comments
hermanthepug 839 days ago
It's for cases where you'd ideally keep the repo private - eg. source code for an app you're working on.

Cloning can be prevented as we're not simply sharing the github repository directly to the client. We're exposing a version of the repository (to which the user could painstakingly go file by file and copy all the contents), but there'd be no git clone option. However, this could be enabled if wanted by the owner.

If you're a content creator and wanting to share the code, you may want to monetise access to the code. Many creators do this by uploading the repo to Dropbox and adding a share link inside their Patreon or membership platform.

link