6 ms·

About time. It's absolutely ridiculous that this hasn't existed for the past 10 years.

by tlhunter 8mo ago

drob518 8mo ago
Exactly. Yes, please.
gscho 8mo ago
Just make the repo private?
- ethin 8mo ago
  That doesn't work. What if your repo is a mirror of another repo?
- Carrok 8mo ago
  "I am fine with my code being public, but I am not fine being badgered by people about changes I have no interest in." is a perfectly valid stance.
wavemode 8mo ago
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 7mo 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.
zvqcMMV6Zcr 8mo ago
It is almost like finding 20 year old bugs on Mozilla tracker. That said GitHub doesn't have the excuse of mostly relying on volunteer work. Also I don't find GitLab that much better. I remember the feature request for "Give option to disable automatic adding of 'Closes ISSUE' to merge requests" closed with "Why would you need an option for that, everyone either loves it or likes manually removing it every time.

About time. It's absolutely ridiculous that this hasn't existed for the past 10 years.

drob518 8mo ago

Exactly. Yes, please.

gscho 8mo ago

Just make the repo private?

ethin 8mo ago
That doesn't work. What if your repo is a mirror of another repo?
Carrok 8mo ago
"I am fine with my code being public, but I am not fine being badgered by people about changes I have no interest in." is a perfectly valid stance.

wavemode 8mo ago

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

zvqcMMV6Zcr 8mo ago

It is almost like finding 20 year old bugs on Mozilla tracker. That said GitHub doesn't have the excuse of mostly relying on volunteer work. Also I don't find GitLab that much better. I remember the feature request for "Give option to disable automatic adding of 'Closes ISSUE' to merge requests" closed with "Why would you need an option for that, everyone either loves it or likes manually removing it every time.