New repository settings for configuring pull request access

Re:New repository settings for configuring pull request access by CrimsonRain on Thursday October 08, 2026 @05:22AM (#50003631)

Locking down pr is the wrong approach (for most). Just provide a subtab inside PR tab that shows PRs from new people. One tab for pr from contributors and users who already have PRs accepted in the repo.

Another tab from first time/no pr approved yet users. Maintainers can treat it as spam box if they want.

Occasionally, users can flag them as useful and maintainers can then look at them.

Give a button to move from others to PR tab.

Don't consider count of PRs inside others in the main count.

[ Parent | on HN ]

Re:New repository settings for configuring pull request access by fzeindl on Thursday October 08, 2026 @06:35AM (#50004125)

Agreed. So many things could be solved by smart UIs. This is pouring the baby out with the bathwater.

[ Parent | on HN ]

Re:New repository settings for configuring pull request access by Bluestein on Thursday October 08, 2026 @08:09AM (#50004855)

Heck, one could say "Chat" for GPTs was the summum of "smart" UIs (or "smarts" for an "optimal" UI: Chat ...)

... and there's an asymmetry there.-

[ Parent | on HN ]

Re:New repository settings for configuring pull request access by embedding-shape on Thursday October 08, 2026 @06:51AM (#50004243)

> Locking down pr is the wrong approach (for most).

Depends on your goal no? If your goal is to not accept random contributions or PRs, then being able to disable PRs completely, seems like the perfect approach? Up until this change (which happened almost a year ago, FWIW), it was impossible to just have a read-only mirror on GitHub that didn't get hit with drive-by PRs that just waste time, for example: https://github.com/videolan/dav1d/pulls?q=is%3Apr+state%3Acl...

I'm glad we can finally completely disable it, as it seems to just confuse people when you're not actually accepting PRs.

[ Parent | on HN ]

Re:New repository settings for configuring pull request access by GaryBluto on Thursday October 08, 2026 @08:00AM (#50004794)

I never thought I’d see the day where somebody who works at the DoD would spend their spare time trying to get random open source projects (even one that already has a CoC) to accept the Contributors Covenant via GitHub pull requests. We truly are living in an enlightened age.

[ Parent | on HN ]

Re:New repository settings for configuring pull request access by rrr_oh_man on Thursday October 08, 2026 @08:44AM (#50005173)

> September 2026 - Created 670 commits in 80 repositories

> I never thought I’d see the day where somebody who works at the DoD would spend their spare time

He didn't.

[ Parent | on HN ]

Re:New repository settings for configuring pull request access by nerdix on Thursday October 08, 2026 @10:53AM (#50006545)

He has over 600 repositories. A few are forks but the majority appear to be TypeScript slop with less than 100 commits (with most of them being dependabot updates).

There needs to be public service announcements about responsible AI use. If we're going to boil the Earth and live in a world where a 64 GB DDR5 RAM kit that was $200 three years ago is now over $1000 then can we at least get the LLMs to generate code that's actually useful instead of circadian rhythm calculators.

[ Parent | on HN ]

Re:New repository settings for configuring pull request access by embedding-shape on Thursday October 08, 2026 @10:04AM (#50005941)

They didn't. They made the senseless PR in 2022, but only worked at DoD for a whole month so far, seems to have joined in October.

I think it takes a certain type of person to join that department at this time, so make of that what you will. Certainly seems like they've "turned their life around", for better or worse.

[ Parent | on HN ]