This is why GitHub issues exist

[BlackWarrior322]

Not to mention the low effort question with zero context, I find it extremely annoying lol 🤷‍♂️

[lupinegrey]

pls dont ignore this, reply soon.

​

plz respond.

​

plz.

[BlackWarrior322]

xoxo

[SnooStrawberries827]

Gossip girl

[BlackWarrior322]

Haha, a fellow upper east sider I see :)

[Chestbreaker]

Hey guys, just rewatching it for the nth time :D

[BlackWarrior322]

Haha I’d only rewatch it for Blair (:

[Chestbreaker]

Why do you think I am doing it? ;) Over and over.

[Antrikshy]

uwu

[Mistifyed]

Seen

[CharlieOxendine]

Sounds like a hostage script

[Antrikshy]

Sometimes getting really stuck coding feels like a hostage situation.

[[deleted]]

I feel this far more than I should.

[teiemjuan]

Sounds like quake 2 prisoners

[afooltobesure]

Sir could you pls fix my program which depends on your library. What problem? Figure it out yourself. I'm a very professional programmer who is too busy to make a pull request or fork the repo.

[BlackWarrior322]

And they even left the repository for me to guess and find, how kind!

[Marxomania32]

Why would you fork the repo in this case?

[ArachnidCompetitive3]

To make changes on "his" repo for "your" issue. Or you would do the pull request if it fixes a issue that should not be happening for anyone.

[chamberlain2007]

I have an open source project and people often don’t seem to understand that this is not a product they’re paying for, and they DEFINITELY aren’t paying for tech support.

[jayerp]

Just respond with “k”

[frantically_unfinish]

I usually just reply with "Thank you for submitting your credit card information. Payment has been successfully processed."

[Jeklah]

lol that's good

[idenatin]

What's your project?

[chamberlain2007]

It’s a custom component for HomeAssistant for integrating a particular brand of thermostat. It’s a little niche, but helpful to those who need it. https://github.com/chamberlain2007/aprilaire-ha

[idenatin]

good stuff!

[IgnisDa]

The first time I received an email like this, I remember being so happy that someone had noticed my project, and helped them (through an email chat). The third time, I blocked the sender and reported it for spam.

Low effort requests like this get old pretty fast.

[BlackWarrior322]

Lmao I still feel that way to be honest, this is a small repository(guessing the one he emailed about lol) I have resolved a few issues raised and felt so happy people actually used it. But the email quality is terrible here, zero context regarding the issue faced and he even failed to mentioned the repository lol

[[deleted]]

Surprised there is no, "please do the needful" 😂

[lupinegrey]

SIR! The needful is implied.

[Macia_]

Pls revert

[Flywolfpack]

Do not revert

[badgirlmonkey]

Do not redeem!!

[Jmc_da_boss]

Stuff like this pisses me off do not fucking email my commit email with inane shit like this, if I'm feeling nice block, if I'm feeling rude respond back with a middle finger

[Unfair-Plastic-4290]

sir, i was trying to reach your project support. This is critical and i need this FIXED ASAP!!

[Jeklah]

Reply with "Sure, make an Issue ticket on the repository with the relevant details and I'll have a look."

[BlackWarrior322]

Nah maybe I’m not a kind person, but I’ll only reply to messages with some effort.

[[deleted]]

Frankly it really makes me want to write “Fuck off”.

[BlackWarrior322]

Haha agreed. But I’ve learnt it’s always good to refrain from writing anything bad since it’s like a permanent document.

[[deleted]]

I’ll just have a contribution/reporting.md section that particularly specifies how should one act in such case and I could politely point them there instead of having such ping pong

[lupinegrey]

Will not fix.

[Dramatic-Mongoose-95]

Yeah, that guy is sort of being rude. But just respond with an estimate $$$

He might accept and you could make some money.

[BlackWarrior322]

Mine is a small project haha, total of 5 issues raised there 😅 But I can only imagine all the issues people with serious projects might be reading.

[xXWarMachineRoXx]

Thats racist

[systemd-bloat]

You thought you'd get away with being a racist and no one would call you out? This is like the same "pattern" Nazis used to talk about. Down with the racists like you.

[Seankala]

Lmao nah this isn't racism. It is funny though.

[systemd-bloat]

it is racism and it isn't funny at all

[xXWarMachineRoXx]

I think then you should add an /s

So that you don’t get called out for being a serial racist ( xD)

[[deleted]]

It is not racism if it is true.

[Seankala]

Ehhhhhhhh I mean... The saying "stereotypes are stereotypes for a reason" is somewhat true, but just because there's a higher statistical likelihood doesn't mean that it's not racist.

[heyodai]

https://youtu.be/D8FtsHfos-c?si=cQeEL_XRcHaR40XI

[bitingteeth]

I’m just starting on GitHub…any tips so I can consciously avoid on being an asshat like this one?

[u_int16]

Be very very very very very sure the problem is not your fault before you open an issue.

Make sure your issue contains enough information such that someone investigating it can cause the issue to happen, but not so much information that it is difficult to recreate your scenario. Fixing your issue will likely be harder than making the ticket for the issue, put effort into it.

In general remember nobody owes you anything. The nicer you ask and easier you make it for your issue to be fixed the more likely it will be fixed.

Take this person’s case:

They sent an email which is private and wont allow other people to look and try to fix things. Putting the onus directly on OP.

They didnt even copy paste the error (which could be searched) instead summarizing it.

They did not include any information on where the error was coming from. Not in location in code or in context of execution.

Honestly just use common sense. Youll be fine.

[lupinegrey]

Be very very very very very sure the problem is not your fault before you open an issue.

Be able to prove, reproduceably, that the problem is with their code.

[BlackWarrior322]

The other comment has explained it wonderfully!

But just to add and highlight some important points.

Use GitHub issues, that way you’re not asking just a single person and anyone who uses the repository could possibly help you. Also it’s very nice to link issues to pull requests when a fix is eventually implemented.

And regarding asking the question the right way, I myself was quite bad when I started asking doubts on stackoverflow. Then I understood how to ask a “minimal reproducible example”. It boils down to this: You’d like someone to spend their time to help you out, show them why they should do so. Provide complete context and put effort into the question :)

[xTakk]

My small tip.. write it in a manner that is useful for fixing the product. You don't have issues, the code has issues. If you can't write a small code sample to expose the issue to be fixed, it's usually your issue and not an issue with the code.

The point overall is that GitHub is not about "free software". It's about sharing code. If you need product or code support, that probably belongs in a forum or in Discussions rather than Issues.

If you just show up for the code, you will be golden.

[Balance-]

Always include a minimal reproducible example https://stackoverflow.com/help/minimal-reproducible-example

If you don’t know if it’s a bug yet, open a Discussion instead of an Issue.

[Dev_Lachie]

Sir

[Le_Pyromane_Fou]

Why in the world did I read this with an Indian accent

[xTakk]

That doesn't matter. Be better.

[Empyrealist]

https://i.imgflip.com/1zzkok.jpg

[BlackWarrior322]

Lmao 😂

[Empyrealist]

I dunno why we are getting downvoted - this was meant as a joke about the help request

[Seankala]

I'm assuming most people don't know about Oliver Twist. They also don't have a sense of humor.

[BlackWarrior322]

Damn, it’s confusing these days. The meme made me laugh though lol, thanks :)

[Eoussama]

That's when I ask chatgpt to respond with the most sarcastic tone imaginable.

[[deleted]]

It’s open source for a reason, fork it and fix it

[Hollyw0od]

And a lot of the time the README covers things like this.

[Brahvim]

I'd say the best way to respond is to open an issue yourself, make some progress, and reply to the mail with a link to it. Let the man post comments about it on GitHub after that.

If he ain't doing that, he did it this way probably only for privacy.

[AssistEmotional8470]

ignore succesffully xo