Merged
Conversation
Additional guidance for what type of details should be included with a bug report.
ghost
added
the
Contributor
Author
|
Those of you who have spent more time triaging issues will likely have a better idea of what details people should provide up front. |
Contributor
|
LGTM. A note about how to enable verbose logging might be useful as well. |
|
@hramos updated the pull request. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Additional guidance for what type of details should be included with a bug report.
I've removed the formatting around links as it did not succeed in making the template more readable in the New Issue composer, which is where most people would see this for the first time.