How to Reject a Feature Request
lorendb.dev
lorendb.dev
Some users will fork your code to implement something they see as necessary, so if you're going to reject an issue, the first thing you need to do is understand why the user is requesting it, and what their options are without an implementation
If it's a really dumb/lazy issue created in your own GitHub repository, you should have every right to roast them. I feel like this actually might be one of the only tangible benefits of maintaining a popular open source repo.
I actually might include that as a clause in the license for a future open source effort.