Add bug report and feature request issue templates - #182
Open
isourabh wants to merge 1 commit into
Open
Conversation
The repo had no issue templates, and SUPPORT.md linked to bug_report.md and feature_request.md, which never existed. Add YAML issue forms for bugs and feature requests that collect the details triage needs up front: affected command/area, repro steps, expected vs actual behavior, and CLI version plus install method. Add a chooser config that disables blank issues and routes usage questions to Discussions, docs to Learn, and vulnerabilities to MSRC. Point the SUPPORT.md links at the new templates, and replace the wiki reference with docs and Discussions since the wiki has no pages and redirects to the repo root. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🟢 Approval recommended
The changes are straightforward GitHub metadata updates (issue forms + support links) and appear consistent and complete for improving issue triage.
Pull request overview
This PR improves issue intake and triage for msstore-cli by adding GitHub issue form templates and updating support links so reporters are guided to structured bug/feature forms (instead of free-form issues or broken template links).
Changes:
- Added GitHub Issue Forms for bug reports and feature requests under
.github/ISSUE_TEMPLATE/. - Added
.github/ISSUE_TEMPLATE/config.ymlto disable blank issues and provide contact links (docs, Discussions, MSRC). - Updated
SUPPORT.mdto point to working templates and to route help/questions to docs + Discussions instead of the (empty) wiki.
File summaries
| File | Description |
|---|---|
| SUPPORT.md | Updates support guidance and fixes broken issue-template links by pointing to the new issue forms, plus adds docs/discussions references. |
| .github/ISSUE_TEMPLATE/bug_report.yml | Adds a structured bug report form capturing area, repro, expected/actual behavior, environment details, and optional verbose logs. |
| .github/ISSUE_TEMPLATE/feature_request.yml | Adds a structured feature request form capturing area, problem, proposed solution, and optional context. |
| .github/ISSUE_TEMPLATE/config.yml | Disables blank issues and adds contact links for docs, Discussions, and MSRC security reporting. |
Review details
- Files reviewed: 4/4 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
isourabh
requested review from
Karthikeyan K (KK911) and
Alexandre Zollinger Chohfi (azchohfi)
September 10, 2026 11:16
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.
Why
The repo had no issue templates at all, so every new issue arrived as free-form text and triage had to ask for the CLI version, OS, and repro steps by hand.
SUPPORT.mdalso linked tobug_report.mdandfeature_request.md, neither of which ever existed in the repo — both links landed on a blank issue.What
New —
.github/ISSUE_TEMPLATE/bug_report.yml— YAML issue form titled[Bug]:, labeledbug,type: Bug. Collects affected command/area (multi-select: init, package, publish, submission, flights, …), description, repro steps, expected vs actual behavior, and environment (msstore --version, OS, install method), plus optional--verboselogs. Header warns against pasting secrets and points toSECURITY.md.feature_request.yml— titled[Feature]:, labeledenhancement,type: Feature. Collects area, problem, proposed solution, and optional alternatives/context.config.yml— disables blank issues and adds contact links for docs, Discussions, and MSRC.Modified —
SUPPORT.md[wiki]reference with[docs]and[discussions]. The wiki is enabled but has no pages, so…/wikiredirects to the repo root; Discussions has 9 live threads and is the real Q&A venue.Verified against the live repo
bugandenhancementexist (the initial draft usedIssue-Bug/Issue-Feature, which don't exist here and would have been silently dropped).BugandFeatureare enabled on themicrosoftorg.Note
config.ymlincludes an explicit MSRC contact link. This duplicates the "Report a security vulnerability" row GitHub generates automatically fromSECURITY.md, and none of the Microsoft repos I checked (terminal, PowerToys, winget-cli, vscode, WindowsAppSDK, playwright, dotnet/sdk) hand-roll one. Kept deliberately so the MSRC form is one click away rather than two — happy to drop it if reviewers prefer the house style.Separately: private vulnerability reporting is currently disabled on this repo. Enabling it is a repo setting, not a file change, but it would give reporters a proper in-GitHub button.