Skip to content

feat(GH): update feature template #12225

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.

Sign up for GitHub

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

Open
kmcfaul wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −3
Open

feat(GH): update feature template #12225

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions .github/ISSUE_TEMPLATE/feature_request.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,13 @@ assignees: ''
What is the existing component, if any?

**Describe the feature**
A clear and concise description of the new feature. What is the expected behavior?
A clear and concise description of the new feature. What is the expected behavior? Is there any error handling or user callbacks that need to handled?

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
Include screenshots or links to Marvel or other mockups.
**Are there visuals for this feature? If applicable, please include examples for each state or variant, and for varying widths including mobile and desktop viewports**
Include screenshots or links to Figma or other mockups.

**Any other information?**
Does this feature require keyboard interaction or focus management?
Are there any specific accessiblity considerations?
Copy link

@coderabbitai coderabbitai bot Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix spelling error in user-facing template.

The word "accessiblity" is misspelled and should be "accessibility". This is user-facing text in the issue template.

📝 Proposed fix for the spelling error 
-Are there any specific accessiblity considerations?
+Are there any specific accessibility considerations?
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Are there any specific accessiblity considerations?
Are there any specific accessibility considerations?
🧰 Tools
🪛 LanguageTool

[grammar] ~21-~21: Ensure spelling is correct
Context: ...ocus management? Are there any specific accessiblity considerations? **If applicable, what ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents 
In @.github/ISSUE_TEMPLATE/feature_request.md at line 21, Replace the misspelled
word in the user-facing template line "Are there any specific accessiblity
considerations?" by changing "accessiblity" to "accessibility" so the sentence
reads "Are there any specific accessibility considerations?" and ensure any
other occurrences of "accessiblity" in the same template are corrected as well.


**If applicable, what is your product and what release date are you targeting?**
Loading