-
Notifications
You must be signed in to change notification settings - Fork 111
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
Creating a "Generic Issue" should not present the user with prompts for a bug report #7528
Comments
yarikoptic
added a commit
to yarikoptic/datalad
that referenced
this issue
Nov 3, 2023
- as reported by @jwodder in datalad#7528 the form is really about reporting a bug, not just opening some generic issue - we also have "Report a Security Vulnerability" internal github issue reporting we enabled in response to datalad#7369; Taken together with default "Open a blank issue", we would make it consistent in being imperative
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I go to create an issue in this repository, the only option applicable to my use cases is to create a "Generic Issue", but the titles of the fields in the form I am directed to all assume that I'm reporting a bug; the very first field is even titled "What is the problem?". What if I'm not reporting a bug and instead am requesting a feature or (as I was just doing) suggesting ways to improve the quality of the codebase?
If I click "Generic Issue", the form I'm presented with (if I'm shown a form at all) should actually be for a generic issue (where "issue" is in the looser GitHub sense of "a thing to be worked on", not "a thing that's wrong"). The current "Generic Issue" setup should instead be used for a "Report a Bug" option on the "New Issue" page.
The text was updated successfully, but these errors were encountered: