docs: update issue templates for Studio 3.0 tools#135
Merged
Conversation
Reflect the latest Uno Platform Studio tooling in the issue forms by adding Uno Platform Studio App, Uno Platform Studio Agent, and Uno Platform Skills to the "Which tool(s) are affected?" dropdowns across the bug-report, enhancement, documentation-issue, and documentation-request templates, and to the concern-examples list and feedback guide. Also align the supported-runtime note to ".NET 9+" and fix the unbalanced bold markdown in the enhancement template, switch the feedback template from "Hot Design™" to "Hot Design®" to match the docs, and fix a "usuable" typo. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
4 tasks
hiadamhere
approved these changes
Jun 9, 2026
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
2 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.
GitHub Issue (If applicable): tracked internally
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The issue templates still describe an earlier version of Uno Platform Studio. The "Which tool(s) are affected?" dropdowns (and the feedback guide) only list Hot Design®, Hot Design® Agent, Uno MCPs, Hot Reload, and Design-to-Code, so reporters have no way to attribute issues or feedback to the newer Uno Platform Studio surfaces.
What is the new behavior?
Templates are updated to reflect the latest Uno Platform Studio tooling:
bug-report.yml,enhancement.yml,documentation-issue.yml, anddocumentation-request.yml.documentation-request.yml.feedback.md: add per-tool feedback prompts for the App, Agent, and Skills; refresh the general-feedback tool list; switch Hot Design™ to Hot Design® to match the docs; fix ausuabletypo.enhancement.yml.No label sets, platform/IDE options, renderer, or
config.ymlcontact links were changed. All issue-form YAML was validated.PR Checklist
Additional Information
The new short links (
studio-agent,studio-skills) are wired to resolve to the corresponding documentation pages as the Studio documentation publishes.