Live data from Hacker News

Ask HN: How to say no to a GitHub issue feature request?

news.ycombinator.com

51–60 of 243 posts

Re: Ask HN: How to say no to a GitHub issue feature request?

#51

I'm no dev but let's say that my job has a similar issue. The approach that I use focuses on being 1) truthful, 2) clear, 3) polite, 4) concise. In this specific order. In other words: "Sorry, I'm not going to do this because [insert here the actual reason, not some lame excuse]". Past that, if that user keeps insisting, the user is being entitled and you should not bother yourself with entitled people.

You can block people on GitHub to stop them from interacting with you or bothering you

Re: Ask HN: How to say no to a GitHub issue feature request?

#53
Thank you for developing something people think is worth using and for being a nice enough person to feel awkward about disappointing anyone. A charitable assumption is that the requester stumbled on to github and has mistaken it for his computer vendor's technical support channel the way people used to do on AOL. I agree with everyone's advice and would suggest in addition only that you be explicit about your wish list policy in your README. I have such a section in mine but won't post it here because it's probably too snarky for a nice person.

Re: Ask HN: How to say no to a GitHub issue feature request?

#54
"I am not planning to implement this, but it sounds like a good idea, feel free to send a pull request"

additionally apply label "PR welcome" and/or close issue

------------

"This feature is out of scope and not planned"

additionally close issue and optionally apply label "declined"

Ideally, you can also drop link to some documented project vision.

------------

Other comments have good hints how you can try explaining things.

------------

Note that on GitHub and any decent platform you can lock discussions and block people. Feel free to use this, you are not hired by them.

Re: Ask HN: How to say no to a GitHub issue feature request?

#55
Github could do well to help here. In LinkedIn for recruiters you have auto responses "I'm not interested" etc. Github could do something similar, possibly with a "mute this conversation" option. And if someone is getting muted a lot maybe it's time to restrict that account or give them some kind of nudge towards improving their behaviour.

Re: Ask HN: How to say no to a GitHub issue feature request?

#56

"I am not planning to implement this, but it sounds like a good idea, feel free to send a pull request" additionally apply label "PR welcome" and/or close issue ------------ "This feature is out of scope and not planned" additionally close issue and optionally apply label "declined" Ideally, you can also drop link to some documented project vision. ------------ Other comments have good hints how you can try explainin…

Yeah but I guess the issue then becomes, what happens if the PR ever materializes? Would you want to maintain that code now?

Re: Ask HN: How to say no to a GitHub issue feature request?

#60

Github could do well to help here. In LinkedIn for recruiters you have auto responses "I'm not interested" etc. Github could do something similar, possibly with a "mute this conversation" option. And if someone is getting muted a lot maybe it's time to restrict that account or give them some kind of nudge towards improving their behaviour.

Maybe posting a guide to saying you're not interested is a stronger statement than a button? For example, the guide could suggest creating a label that you use when something won't be prioritised given present conditions. Or whatever is the direct-but-not-offensive way to reject a request.
Post reply on HN