improve bug report template#3080
Merged
georglauterbach merged 2 commits intomasterfrom Feb 9, 2023
Merged
Conversation
Users (and I) are not sure how a field is formatted. The `render: Markdown` puts everything in a \`\`\`markdown block, which is not what I anticipated. So I removed that. Now , users can use Markdown formatting in almost all fields properly.
152db28 to
4a8ae6e
Compare
wernerfred
approved these changes
Feb 9, 2023
polarathene
approved these changes
Feb 9, 2023
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
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
Users (and I) are not sure how a field is formatted. The
render: Markdownputs everything in a ```markdown block, which is not what I anticipated. So I removed that. Now , users can use Markdown formatting in almost all fields properly.Fixes review feedback from #3078.
Type of change
Checklist:
docs/)