4 ms·
1. You migh thave N projects where a few want contributions and a few don't. You don't want several sites to manage them. 2. The code part of github (a git tre
by alkonaut 6y ago
1. You migh thave N projects where a few want contributions and a few don't. You don't want several sites to manage them.
2. The code part of github (a git tree on a webpage) isn't even the key functionality. It's PR's, CI. You may accept feature requests and bug requests but still not want PR's.
3. Having collaborative development with a small team of e.g. 2 people means internal pull requests, reviews, discussions etc are important (and could still be useful to see or contribute to by external users), so taking away PR's isn't the same as going under ground with the project.
4. GitHub is a well known site, people will find your project there.