Also, asking more information from users make the process more painful for them.
Hopefully, it's a deterrent for bad players and doesn't harm good players.
I expect the following outcome. People will dig more into their problem before opening an issue.
I have seen too many issues with a simple answer that people could have found on their own if they were willing to spend time on it.
They will better know the codebase, and potentially submit (& better) PRs.
One possible issue is that you enforce strict constraints on something that sometimes calls for flexibility.
expected behaviour?The request to read the docs/code/goto SO hardly ever nudge someone from their goal - an answer.
After all, I have found the number of issues manageable (3 months ago) since I have opened this issue. I find less the need to enforce it.
Most helpful comment
Also, asking more information from users make the process more painful for them.
Hopefully, it's a deterrent for bad players and doesn't harm good players.
I expect the following outcome. People will dig more into their problem before opening an issue.
I have seen too many issues with a simple answer that people could have found on their own if they were willing to spend time on it.
They will better know the codebase, and potentially submit (& better) PRs.