GitHub discusses giving maintainers control to disable PRs
1–10 of 75 posts
Re: GitHub discusses giving maintainers control to disable PRs
#2About time. It's absolutely ridiculous that this hasn't existed for the past 10 years.
Re: GitHub discusses giving maintainers control to disable PRs
#3About time. It's absolutely ridiculous that this hasn't existed for the past 10 years.
Exactly. Yes, please.
Re: GitHub discusses giving maintainers control to disable PRs
#4About time. It's absolutely ridiculous that this hasn't existed for the past 10 years.
Just make the repo private?
Re: GitHub discusses giving maintainers control to disable PRs
#5Re: GitHub discusses giving maintainers control to disable PRs
#6About time. It's absolutely ridiculous that this hasn't existed for the past 10 years.
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."
Re: GitHub discusses giving maintainers control to disable PRs
#7Re: GitHub discusses giving maintainers control to disable PRs
#8They need to talk about how the pr itself should change. The text diff just is not the right thing to center. We should be using ai to chunk changes into reviewable bytes and to align on semantics and contracts.
Re: GitHub discusses giving maintainers control to disable PRs
#9I can imagine a few maintainers might appreciate that ability (https://github.com/expressjs/express/pulls?q=is%3Apr%20is%3A...).
Re: GitHub discusses giving maintainers control to disable PRs
#10I can imagine a few maintainers might appreciate that ability ( https://github.com/expressjs/express/pulls?q=is%3Apr%20is%3A... ).
Wow, what is the context for all of these spam PRs?