-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Add spaces and fix switch to actual MarkDown #28696
Conversation
I've added spaces after the colons and the numbered list does so the reporter doesn't have to do it themselves or worse yet doesn't default to not adding them. I've also removed the HTML comment, because it makes no sense in a MarkDown file, especially when it defaults to edit view when creating an issue. I've converted the link to MarkDown link, too.
@TomasHubelbauer, thanks for your PR! By analyzing the history of the files in this pull request, we identified @egamma to be a potential reviewer. |
This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request. |
Instead of Help > About, we could refer the user to Help > Report Issues which fills in versions and installed extensions. |
@chrmarti Thanks for this! I learnt about this function in my related issue #28697 from @ramya-rao-a and I think this is a much better thing to call out in the issue template. I've updated the PR. |
Thanks @TomasHubelbauer ! |
Actually the HTML comment made sense, because that makes the instruction hide after the issue is filed. Adding that back now. |
@chrmarti Ah I see! That's smart. Thank you for fixing it. |
I've added spaces after the colons and the numbered list does so the reporter doesn't have to do it themselves or worse yet doesn't default to not adding them.
I've also removed the HTML comment, because it makes no sense in a MarkDown file, especially when it defaults to edit view when creating an issue. I've converted the link to MarkDown link, too.