upvote
PRs should be rejected by simply not enabling PRs in the first place. If PRs are needed for development, then that should be done in a private repo that is mirrored to a public one. I wouldn't even be surprised if that person'a readme says the project is open to contributions and that pull requests are welcome. I've found this contradiction to be very common, yet it seems like I'm in the minority for believing it's rude.
reply
Forking also doesn't mean completely going your own way! I have multiple repos forked where we and the maintainer disagreed on the direction, so I keep my additions on top of theirs in my own repo just how I like
reply
yeah sadly only 0.0001% of all users and reporters seem to understand this stand, which is oh-so-obvious if you have ever put anything public, but then people use opensource because it was hailed as free, more secure, and even more trustworthy. and as a result everyone and their dog not only seems to blindly prefer it but is then entitled to service which was never promised. what a massive cognitive dissonance indeed, but one that was carefully catered to and fed by the few key opinion leaders in the opensource sphere.
reply