-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
GitHub: ask for more info in issue templates #10426
GitHub: ask for more info in issue templates #10426
Conversation
5e64e24
to
9543d01
Compare
I think we should refactor the category for issues too, ref: #8097 |
For me the severity tag is completely useless. People reporting bugs should not make that decision anyway. |
d757364
to
8f38ad6
Compare
I pushed refactored templates for compilation, model evaluation, and miscellaneous bugs. I don't know what information would be needed for e.g. a bug report concerning the server and would ask someone more knowledgeable than me to create such a template instead. |
Don't forget my™ problem is always more important than your™ problem. |
In most cases, having the log output is already enough to pinpoint the problem. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now, thanks. I think we can already merge this to see how it goes, and improve from this in the future.
* GitHub: ask for more info in issues [no ci] * refactor issue templates to be component-specific * more understandable issue description * add dropdown for llama.cpp module
This PR updates the issue templates and adds more fields to ask for potentially useful debugging information (since I find that a lot of the time I end up asking the same questions when I am the first responder to issues). A live version of the templates is on my fork.