-
Notifications
You must be signed in to change notification settings - Fork 2.3k
chore: improve issue template #4276
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
Conversation
| The code should be minimal, have no external dependencies, isolate the | ||
| function(s) that cause breakage. Submit matched and complete C++ and | ||
| Python snippets that can be easily compiled and run to diagnose the | ||
| issue. If possible, make a PR with a new, failing test to give us a |
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.
How about:
In bold near the top: Note that a reproducer in a PR is much more likely to get immediate attention!
Near the top so that people think about their decision bug vs PR immediately.
Then repeat that sentence here, followed by: Failing tests in our CI give us the best starting point for working out fixes.
I could send a PR, plmk.
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.
You can add to this one, I expect?
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.
Done (0f5bc58).
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.
Sorry that one had an accident. Fixed.
|
Thanks! |
Small improvement to issue template, hopefully helping highlight regressions.