Re:GitHub discusses giving maintainers control to disable PRs
by wavemode on Monday February 02, 2026 @09:50PM
(#46865814)
yeah, I thought they were going to provide some sort of rationale as to why they've never implemented this. instead this post just basically goes "yeah, you guys have been asking for this feature for 10 years, and... it's a good idea! let's do it."
[ Parent
| on HN ]
Re:GitHub discusses giving maintainers control to disable PRs
by martinwoodward on Tuesday February 03, 2026 @09:52AM
(#46871704)
Honestly, it's not an area where there has been consensus on when we talk with maintainers. Some folks worry about that reducing the very nature of open source collaboration.
We've had the ability to temporarily disable PR's for a while for maintainers but we felt like it was time to look at this again and see what folks think.
Re:GitHub discusses giving maintainers control to disable PRs
by nerdsniper on Tuesday February 03, 2026 @10:10AM
(#46871935)
A lot of GitHub public repo’s aren’t FOSS though.
Re:GitHub discusses giving maintainers control to disable PRs
by viraptor on Wednesday February 04, 2026 @10:01AM
(#46886636)
> Some folks worry about that reducing the very nature of open source collaboration.
Collaboration on repos where the authors explicitly don't accept PRs and are going to auto close or ignore them? I don't get it - it's not like you're going to force opensource on anyone.
Re:GitHub discusses giving maintainers control to disable PRs
by nerdsniper on Tuesday February 03, 2026 @10:12AM
(#46871954)
My guess is AI powered auto-submission / spam to high value customers is forcing their hand.
Re:GitHub discusses giving maintainers control to disable PRs
by Analemma_ on Tuesday February 03, 2026 @02:57PM
(#46876375)
Imagine the panic inside Microsoft right now where they're all-in in "AI in everything, everywhere" and the results have been so bad that GitHub is being forced to finally let repo owners disable PRs to make it stop.