Edit: Thanks for your kind comments on disabling contributions. I'm aware of the possibility, this is just a meme.
Contributions in open source projects are great, needed and make the world a better place after all. Therefore they should be declined politely, optionally by giving a reason.
I hereby inform you that I will no longer accept contributions to this post /s.
53 Comments
KindnessIsPunk@lemmy.ca · 106 pts · 291d
Don't worry, you also get issue reports were the user didn't read the start guide or document any of the steps to reproduce the issue.
passepartout@feddit.org · 88 pts · 291d
When submitting issues, I live in constant fear of creating duplicates.
Korhaka@sopuli.xyz · 60 pts · 291d
When submitting issues, I live in constant fear of creating duplicates.
snooggums@piefed.world · 30 pts · 291d
When submitting duplicates, I live in constant fear of creating issues.
bss03@infosec.pub · 23 pts · 291d
When creating duplicates, I live in constant fear of submitting issues.
Viking_Hippie@lemmy.dbzer0.com · 15 pts · 291d
When living duplicitously, I submit a constant fear of issues.
bss03@infosec.pub · 12 pts · 291d
When submissively fearing, I constantly duplicate living issues.
erictile@lemmy.world · 8 pts · 291d
His name is Robert Paulson.
Dicska@lemmy.world · 2 pts · 290d
And this is Jackass.
42beansinapod@discuss.tchncs.de · 47 pts · 291d
When submitting issues, I live in constant fear of creating duplicates.
bss03@infosec.pub · 26 pts · 291d
Possible dup? https://feddit.org/comment/9969130
nialv7@lemmy.world · 83 pts · 291d
You can turn issues and PRs off on GitHub though.
Unless replying rudely to PRs is exactly what you want to do. Then you do you.
fruitycoder@sh.itjust.works · 37 pts · 291d
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
dev_null@lemmy.ml · 12 pts · 291d
No you can't. The only way to turn off PRs on a public repo is to migrate away from GitHub.
witten@lemmy.world · 11 pts · 291d
nialv7@lemmy.world · 3 pts · 291d
Ooops, I misremembered :(
witten@lemmy.world · 4 pts · 290d
tdawg@lemmy.world · 40 pts · 291d
Imagine getting PR's against ur projects šæ
qqq@lemmy.world · 27 pts · 291d
I've had someone screenshot my code, circle a buggy line in red, and blog about it instead of submitting a PR.
SubArcticTundra@lemmy.ml · 10 pts · 291d
Rip
cjk@discuss.tchncs.de · 5 pts · 291d
Was the blog post titled āhow to be the worst OSS citizenā? That would at least be consequential
gibson@sopuli.xyz · 39 pts · 291d
Open source doesn't mean you have to accept contributions or help anyone with anything š
yuriRO@lemmy.dbzer0.com · 31 pts · 291d
Lucky you get attention from the community
sirico@feddit.uk · 11 pts · 291d
Lucky you don't enjoy the peace
joyjoy@lemmy.zip · 29 pts · 291d
Me after submitting my 50th PR this month: "Look at me. I am the maintainer now."
lonesomeCat@lemmy.ml · 29 pts · 291d
You guys are getting PRs?
db0@lemmy.dbzer0.com · 18 pts · 291d
I never understand people rejecting free improvements on FOSS projects.
EDIT: Y'all, It's not like I cannot comprehend why they do it. Please stop trying to explain it to me. When I said "I don't understand", I meant the psyche of the character that does that. I personally do FOSS to improve the world and collaborate with others that do so as well. I will never get people who do FOSS and then get salty about people liking it too much.
passepartout@feddit.org · 102 pts · 291d
Apart from bad quality code, the PR might not fit the vision the owner has in mind for the project. Improvements are subjective.
db0@lemmy.dbzer0.com · -9 pts · 291d
Sure, but that's not what the meme implies.
rtxn@lemmy.world · 56 pts · 291d
Verifying that the code doesn't contain regressions, bugs, or vulnerabilities, that it doesn't conflict with whatever the owner is actively developing privately, in addition to making sure it wasn't vomited out by a goddamn clanker, is a huge burden on a solo developer. They are free to decide whether to take on this responsibility.
Slotos@feddit.nl · 57 pts · 291d
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.
db0@lemmy.dbzer0.com · 0 pts · 291d
Sure, one can request those PRs to add those tests before merging.
Don't get me wrong, I can understand why someone wants to just share without collaborating, but I don't get why they would publish in a collaborative environment, and then make memes about people trying to collaborate with them.
Personally, as someone writing FOSS for a while now, I'm always happy to get anyone helping out and get demotivated when nobody cares. Being actively hostile to actual code contributors, is just fucking bizarre to me.
ITGuyLevi@programming.dev · 21 pts · 291d
While I do agree GitHub is a place where people collaborate, it's also a pretty handy place to store stuff without having to host your own. If the project doesn't invite people to contribute, don't expect a polite response forever. It's like stopping your neighbor on the street corner to tell them they should paint their house white for the thermal benefits, yeah people collaborate on the street, yeah you are right, it's their house though.
db0@lemmy.dbzer0.com · 5 pts · 291d
Github provides ways to both display code just as is (archive mode) and to also disable issues and auto-close all PRs with a message.
Zagorath@aussie.zone · 4 pts · 291d
Is archive mode the appropriate tool for this? I would assume that's for when a repo is no longer receiving any updates from anyone, not just when the owner doesn't want others contributing.
firelizzard@programming.dev · 1 pts · 290d
I make my code open source and public so people can use it if they find it useful, not because I expect anyone to contribute.
And thereās a big fucking difference between actively hostile and āIām not interested in accepting this changeā.
alastel@lemmy.ml · 23 pts · 291d
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.
db0@lemmy.dbzer0.com · -7 pts · 291d
This is not what the meme implies. This is rejecting all PR, regardless of quality or fit. That, I don't get.
null@piefed.nullspace.lol · 17 pts · 291d
It's an exaggeration for the purposes of humor. Its not that deep.
Ajen@sh.itjust.works · 13 pts · 291d
I never understand people rejecting free feedback on social media posts.
socsa@piefed.social · 11 pts · 291d
It's meant as a portfolio and I don't want to risk someone mistaking some contribution for my own work.
I don't actually intend to put any time into maintaining it, but you are free to fork it if you want that responsibility.
Your linting is lousy. It causes my eyes much pain.
irelephant@lemmy.dbzer0.com · 5 pts · 291d
So disable prs then.
optissima@lemmy.ml · 3 pts · 291d
Why don't these get read only and archived then? Seems like there's a mechanism for this already?
socsa@piefed.social · 1 pts · 291d
Because maybe one day someone will send me something useful. Also I like the attention.
squaresinger@lemmy.world · 6 pts · 291d
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.
Skullgrid@lemmy.world · 5 pts · 291d
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.
slazer2au@lemmy.world · 5 pts · 291d
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.
SubArcticTundra@lemmy.ml · 17 pts · 291d
Just merge them into a separate branch. You can have your cake and eat it
_stranger_@lemmy.world · 44 pts · 291d
git branch -a
master
peasant_garbage
GreenKnight23@lemmy.world · 6 pts · 291d
_stranger_@lemmy.world · 2 pts · 289d
ikidd@lemmy.world · 17 pts · 291d
Oh, I prefer to be strung along and asked to make a bunch of changes before you reject my PR. That makes me feel truly loved. In the ass.
mesamunefire@piefed.social · 12 pts · 291d
You can disable issues if you want:
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues
I had to do that on a corpo repo to proprietary BS once. It works.
PRs are similar. Just dont allow it and put the rules as such. Or make the repo private. Or even better, self host ;)
rainbowbunny@slrpnk.net · 6 pts · 291d
Tried to swap to GitLab and it told me I need to verify with a phone number. After I already input everything and verified email.
Uri@infosec.pub · 0 pts · 290d
Fuck github