-
Notifications
You must be signed in to change notification settings - Fork 213
Update GitHub bug template #4321
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
base: develop
Are you sure you want to change the base?
Conversation
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.
Pull Request Overview
This PR refines the GitHub bug report template by introducing clear markdown section headings and inline HTML comments to guide reporters without altering the rendered output.
- Converts plain-text prompts into structured headings and comments for Description, Steps to reproduce, Expected behavior, Screenshots, Environment, and Additional context
- Expands browser examples in the Environment section
- Standardizes use of HTML comments to keep guidance hidden in the final issue
Comments suppressed due to low confidence (2)
.github/ISSUE_TEMPLATE/bug_report.md:35
- [nitpick] Indentation for environment list items is inconsistent; consider using a uniform list style (e.g., no leading spaces before each
-
) to improve readability.
- WordPress Version
.github/ISSUE_TEMPLATE/bug_report.md:18
- [nitpick] This label duplicates the ### Steps to reproduce heading; you can remove it to avoid redundancy and streamline the section.
Steps to reproduce the behavior:
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.
Thank you for these improvements!
Changes proposed in this Pull Request:
I files some bug reports this morning, and I realised that our bug template is not great, as it's not taking advantage of options that are available, including comments that won't be in the visible layout (i.e.
<!-- comment -->
) and header sections that make sense in the final report.This PR proposes some updates to our bug template in GitHub to make it clearer what we are asking, and what will be in the final report.
Testing instructions
Inspection should be sufficient.
Changelog entry
Changelog Entry Comment
Comment
This PR only affects our GitHub bug reporting template. It does not touch our the code or have any impact on users or usage, unless they happen to file a bug report.
Post merge