{CI} Update issue and pr template #4599
Merged
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.
Now we use keyword to route issue and pr.
However, as more and more modules are managed, the misjudgment rate is also getting higher.
The misjudgment rate is many times larger than the omission rate.
The reasons for misjudgment:
az sql mi-arc list failes after update to 2.36.0 azure-cli#22224
az afd profile show returns Null for frontDoorId azure-cli#21751
Dataprotection ModuleNotFoundError 'azure.mgmt.resourcegraph' #4562
Inconsistent return value for "exists" commands azure-cli#21822
"az vmss create" for FLEX does not convert "--edge-zone" to "extendedLocation" in template azure-cli#21793
In the future, az $command will be used for matching.
But this will also lead to an increase in the omission rate.
Azure/azure-cli#21726
So we should also modify template to guide user to fill in the related command.