When submitting issues, I live in constant fear of creating duplicates.

When submitting issues, I live in constant fear of creating duplicates.

I do feel like putting an intentional, obvious, but non-issue causing bug in a code base now. Make a contrib guide. Mention needing to read the docs first and check previous issues/discussions first, and make a closed ticket explaining that that bug is nothing but an example bug and that will ban anyone that attempts to fix or report it.

Like a green mnm test for a code base

No you can't. The only way to turn off PRs on a public repo is to migrate away from GitHub.

I've had someone screenshot my code, circle a buggy line in red, and blog about it instead of submitting a PR.

Lucky you don't enjoy the peace

Apart from bad quality code, the PR might not fit the vision the owner has in mind for the project. Improvements are subjective.

Every bit of code a maintainer accepts becomes their responsibility to maintain. Considering that half the time „improvements” don’t even have tests to help maintaining them, feel free to maintain your own fork.

Not everything sent in PR is an improvement from everyone pov though. It might be an improvement for the contributor of a new feature they might be the only one to ever use, while it adds maintenance burden for you, more dependencies, risks of bugs etc for the community, which you have to balance somehow. Plus you might have a view on how to do things properly on your project, which needs to be communicated to contributors, which is additional work you might not have time for, especially if this is just some small side project.

Please stop trying to explain it to me.

I never understand people rejecting free feedback on social media posts.

1. It's meant as a portfolio and I don't want to risk someone mistaking some contribution for my own work.

2. I don't actually intend to put any time into maintaining it, but you are free to fork it if you want that responsibility.

3. Your linting is lousy. It causes my eyes much pain.

I never understand people rejecting free improvements on FOSS projects.

I never understand people who don't install every free FOSS software offered to them on their PC.

Why would someone take every contribution to their FOSS project? It makes no sense to take a contribution doesn't help the project owner's vision of the project.

Fork it, prefix it with open, free, or libre and take the PR from the upstream and ass it to yours after messaging the contributor.

I'd probably reject PRs into my FOSS projects, because the aim is to put the code out there for other people to see and do what they want with it. I'm expressing myself, and sharing what I made; I'm not setting up a tentpole project for others to pitch in and take over on, and start managing their contributions and collaborate with them.

If they want to take the code and do something with it, great. I don't want to be involved in their endeavour.

git branch -a

master

peasant_garbage

hey there's a bug in zyz branch. fix it.