Hacker News new | past | comments | ask | show | jobs | submit login

I've been guilty of this too, and generally I'll write something along the lines of "this would be nice to do, but it's out of scope unless you want to take it on".



That's a fair proposal though.

My issue is, if you want other things done, make issues for them. Don't try to address every single thing you don't like, that is remotely around the code I am trying to get this fix in for.

Like, he has great feedback. It's not the quality of the feedback or content, it's that it has nothing to do with what I currently need urgently implemented to fix a problem.


I get what you mean, and I agree. It might be a good thing to do, but something like that shouldn't be blocking a PR.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: