3 ms·

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 guy

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."

martinwoodward 8mo ago
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.
- nerdsniper 8mo ago
  A lot of GitHub public repo’s aren’t FOSS though.
- viraptor 8mo ago
  > 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.
nerdsniper 8mo ago
My guess is AI powered auto-submission / spam to high value customers is forcing their hand.
- Analemma_ 8mo ago
  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.