Bug issue template: Rewrote COM Reg. Fix Tool question, to make it more action-oriented - #12276
Merged
Conversation
Collaborator
Author
…more likely to run it before submitting
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
3 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.
Link to issue number:
Closes #12275
Summary of the issue:
The current wording of the bug report issue template, makes the question about running the COM Registration Fixing Tool, a passive question that just gathers information.
Description of how this pull request fixes the issue:
Make the question more likely to provoke the user to try running the tool before submitting the issue, by phrasing it more like the other non-optional questions (such as the one which asks if the issue still happens when you disable add-ons).
Also, this regularizes the name of the tool in the question, to be consistent with the NVDA Tools menu name for the tool.
Testing strategy:
N/A, no code changes.
Known issues with pull request:
None
Change log entry:
None needed.