Merged
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
Collaborator
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR refines GitHub issue templates to improve clarity and help users find the correct entry point when submitting issues. The PR was motivated by confusion where users couldn't identify the right template for feature requests, resulting in missing information.
Changes:
- Renamed issue template titles to be cleaner/more consistent (adding emojis to Bug Report and Feature Request, removing emoji from others, renaming community feature request to "Community Idea")
- Added trailing periods to template
descriptionfields for consistency - Minor wording fix: "for microsoft internal" → "from Microsoft internal" in
02_feature_request.yml
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.github/ISSUE_TEMPLATE/01_bug_report.yml |
Added 🐞 emoji to template name and trailing period to description |
.github/ISSUE_TEMPLATE/02_feature_request.yml |
Renamed from "[Microsoft Internal / Service Team] Feature Request" to "✨ Feature Request"; minor description wording fix |
.github/ISSUE_TEMPLATE/03_community_idea.md |
Renamed from "🚀Feature request" to "Community Idea"; trailing period added to description |
.github/ISSUE_TEMPLATE/04_documentation_issue.yml |
Simplified name (removed emoji) and added trailing period |
.github/ISSUE_TEMPLATE/05_what-if_feedback.yml |
Simplified name (removed "Azure CLI" prefix) and added trailing period |
Comments suppressed due to low confidence (2)
.github/ISSUE_TEMPLATE/02_feature_request.yml:2
- The template name was changed from "[Microsoft Internal / Service Team] Feature Request" to "✨ Feature Request", which removes the critical signal that this template is intended only for Microsoft internal or service team users. Community users seeing two feature-related templates ("✨ Feature Request" and "Community Idea") may be confused about which to use, and may incorrectly pick the internal template. The description on line 2 still says "from Microsoft internal or service team", but the title is the first and most visible indicator. Consider keeping some indication of the internal/service team audience in the name (e.g., "✨ Feature Request (Microsoft Internal / Service Team)") to prevent misuse.
.github/ISSUE_TEMPLATE/03_community_idea.md:3 - Renaming
03_community_idea.mdfrom "🚀Feature request" to "Community Idea" removes the word "feature request" from the community template. When community users look for how to submit a feature request, they will now see "✨ Feature Request" and "Community Idea" — and will likely pick "✨ Feature Request" because it matches their intent, even though that template is intended for Microsoft internal/service teams and asks for fields like PM Contact, Engineer Contact, and Resource Provider. This could actually worsen the problem described in the PR. Consider a name for the community template that retains "feature request" language (e.g., "💡 Community Feature Request") so it clearly signals the right entry point for community users.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
yonzhan
approved these changes
Mar 4, 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
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.
Related command
Description
Our issue template is somewhat confusing. Often, people cannot find the correct entry point for feature requests, which results in missing information in the requests:
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.