Update list-template.md | fix metadata to conform to new guidelines#8368
Merged
Conversation
According to the allowed values for `ms.topic` as now showing in the Contributor's Guide (https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies/mstopic?branch=main), the ms.topic for autogenerated reference content should be `language-reference`. By making this update, the available extensions report will also be removed from management's broken link report. We'll still be able to monitor broken links from the azure-docs-cli repo's daily build report.
|
Hi @dbradish-microsoft, |
️✔️Azure CLI Extensions Breaking Change Test
|
Collaborator
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
Contributor
|
🚫All pull requests will be blocked to merge until Jan 6, 2025 due to CCOA |
Contributor
|
Contributor
Author
|
@jsntcy, This is a metadata update for the Available Azure CLI Extensions report. Can we please publish? |
Contributor
Author
AllyW
reviewed
Feb 6, 2025
AllyW
approved these changes
Feb 8, 2025
wangzelin007
approved these changes
Feb 8, 2025
Jenniferyingni
pushed a commit
to Jenniferyingni/azure-cli-extensions
that referenced
this pull request
Feb 9, 2025
…zure#8368) * Update list-template.md | fix metadata to conform to new guidelines According to the allowed values for `ms.topic` as now showing in the Contributor's Guide (https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies/mstopic?branch=main), the ms.topic for autogenerated reference content should be `language-reference`. By making this update, the available extensions report will also be removed from management's broken link report. We'll still be able to monitor broken links from the azure-docs-cli repo's daily build report. * Update ms.topic to generated-reference
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
5 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.
According to the allowed values for
ms.topicas now showing in the Contributor's Guide (https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies/mstopic?branch=main), the ms.topic for autogenerated reference content should belanguage-reference. By making this update, the available extensions report will also be removed from MSFT's broken link report. We'll still be able to monitor broken links from the azure-docs-cli repo's daily build report.Second, the ms.devlang, ms.tool and keyword metadata has been deprecated.
This PR fixes the following build error: