Comment by manquer
2 days ago
Issues and Pull requests are only optional features . Open source projects could always use GitHub as just git host/mirror like how torvalds/linux is setup .
2 days ago
Issues and Pull requests are only optional features . Open source projects could always use GitHub as just git host/mirror like how torvalds/linux is setup .
PRs are not optional: there is no way to disable them on GitHub. I can't be sure that this is intentional, but it certainly works out well for them that this is one of many properties which make it quite difficult to migrate away from the platform.
There's technically a way[1], but you'd have to do it every 6 months which is not great.
https://docs.github.com/en/communities/moderating-comments-a...
Yeah, that's actually what we've done on the Zig GitHub repository. However, it doesn't stop pushes to existing PRs, which isn't ideal; and, yes, it's quite hard to escape the conclusion that there being no "until I turn it back on" option is intentional.
3 replies →
Yikes, the PRs on the Linux repo are quite terrible. At least there's a bot to auto-reply with the correct procedure.
https://github.com/torvalds/linux/pull/1370
I guess you could make a bot that closes any opened PR with a message that PRs are not accepted on Github and a link to the contribution docs.
PRs aren't an optional feature, though acting on PRs is obviously optional; nothing prevents you from ignoring or (even automatically) closing all PRs from anyone who is not on a list of approved contributors.
Pull requests are not optional on GitHub. Users have been begging for more than a decade for an option to disable pull request for a repository, and GitHub continues to ignore them.
As another poster noted, you can disable it by limiting all interactions (6 months at a time). It is not ideal, but it does work to for PRs. You should also close all current PRs when you do that so users cannot push to those branches as well.