3 ms·
An other solution would be to create an org, give access to people you want as collaborators and forbid forking. They can work in branches in the main repositor
by masklinn 9y ago
An other solution would be to create an org, give access to people you want as collaborators and forbid forking. They can work in branches in the main repository, and you can use protected branches to alleviate the risk of incorrect pushes.
- ISL 9y agoWhen they clone to the machine on which they're going to work, they get a copy of the repo. That's part of the point of git. Git, by design, is a platform for the sharing of managed text.
- moondev 9y agoBut there is no github.com upstream relationship. Sure they can upload it, but it will be obvious it's rogue copy since there is no "forked from.." messaging to the canonical repo.