Mitigating duplicate issues for people new to GitHub #11315
Replies: 1 comment 3 replies
-
The mindset here is usually "AAAAA my stuff broke fix it ASAP". Open source etiquette is something to be learned over time. It's not something that comes naturally to people. The ideal behaviour of checking out the Readme, pinned issues, etc. has to be inculcated on purpose. FAQs or anything else won't make a difference. The most in-your-face instruction is the template. If people ignore that, then we just close the issue. After all,
:D
This isn't the case. Where have you seen this? |
Beta Was this translation helpful? Give feedback.
-
Checklist
What is/are your question(s)?
This isn't related to the NewPipe app, but to the repo itself, so I'm asking here. I'm noticing that most of the people duplicating known issues such as #11191 are new GitHub accounts that were created just to report the issue through the Report on GitHub button. I see that replying to existing issues is limited to accounts that aren't new, but the same does not go for creating new issues. Would limiting the creation of new issues help mitigate duplicates? Or should known issues be added to the FAQ?
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions