logoalt Hacker News

New repository settings for configuring pull request access

19 points • by Bluestein • last Tuesday at 7:01 AM • 11 comments • view on HN

Comments

CrimsonRain • today at 9:22 AM

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.

➕ show 1 reply
asdfsa32 • today at 8:48 AM

If the Microsoft purchase of Github wasn't a good indicator of the start of the end, this is it, I know a lot of people like to have "control" over things, but I have found so many fixes for software I use in un-merged PRs. Github moving towards closer and a closer system is good opp for alternatives to take some of that space. Nice.

sampli • today at 8:45 AM

This is from February

➕ show 1 reply
soltanov • today at 7:46 AM

About time; locking down pull request surface area at the repository level without hacky automation is a clean win.

bingemaker • today at 7:58 AM

I think OSS maintainers can protect themselves from hacktoberfest PR slop! A welcome change.

➕ show 1 reply