Clarify issue template to say “full stack trace” #3950
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reporters should always include the full stack trace. Make it more obvious that it is the case (and so we can point to the template in case people don’t).
|
Thanks. I noticed that it may or may not have been helpful on one of the issues recently. It seems like the issue template really needs to be bullet proof without chance of misinterpretation 😅 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Reporters should always include the full stack trace. Make it more obvious that it is the case (and so we can point to the template in case people don’t).
This targets the master branch so that any changes to the template can be seen here on GitHub.
Checklist: