Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meta: Why users cannot create Issues directly #32830

Open
rarkins opened this issue Dec 1, 2024 · 0 comments
Open

Meta: Why users cannot create Issues directly #32830

rarkins opened this issue Dec 1, 2024 · 0 comments
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:docs Documentation

Comments

@rarkins
Copy link
Collaborator

rarkins commented Dec 1, 2024

Describe the proposed change(s).

Users are not allowed to create Issues directly in this repository - we ask that you create a Discussion first.

This approach is based on years of experience supporting users, and observing that 80-90% of what users think are bugs are either misunderstandings, environmental problems, or configuration errors by the users themselves. For what's left, the majority are often feature requests (unimplemented features) and not bugs (malfunctioning features).

Users collectively are terrible at judging what a bug report is, and that poor judgment left our repo full of poorly described and/or invalid bug reports. The majority of Open Source projects without this policy are also full of low quality issues, and it's a bad thing.

Importantly, any Discussion which clearly identifies a problem in Renovate and can be confirmed or reproduced will be converted to an Issue by a maintainer, so as a user finding a valid problem you don't do any extra work anyway.

@rarkins rarkins added the priority-4-low Low priority, unlikely to be done unless it becomes important to more people label Dec 1, 2024
@rarkins rarkins pinned this issue Dec 1, 2024
@rarkins rarkins changed the title Meta: Why users cannot create Bug Report Issues directly in this repo Meta: Why users cannot create Issues directly Dec 5, 2024
@rarkins rarkins added the type:docs Documentation label Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:docs Documentation
Projects
None yet
Development

No branches or pull requests

1 participant