Bulk Validation: Invaid ms.author, ms.technology, absolute links
Docs Build status updates of commit 7173688:
:warning: Validation status: warnings
docs-ref-services/preview/content-delivery-network.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'.
docs-ref-services/preview/core-amqp-readme.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'. -
Line 24, Column 5: [Suggestion: preserve-view-not-set - See documentation]
Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
docs-ref-services/preview/core-http-netty-readme.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'. -
Line 23, Column 5: [Suggestion: preserve-view-not-set - See documentation]
Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
docs-ref-services/preview/core-http-okhttp-readme.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'. -
Line 2, Column 1: [Suggestion: description-missing - See documentation]
Missing required attribute: 'description'. -
Line 22, Column 5: [Suggestion: preserve-view-not-set - See documentation]
Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
docs-ref-services/preview/core-management-readme.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'.
docs-ref-services/preview/core-readme.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'. -
Line 32, Column 5: [Suggestion: preserve-view-not-set - See documentation]
Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
docs-ref-services/preview/core-serializer-avro-jackson-readme.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'.
docs-ref-services/preview/core-serializer-json-gson-readme.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'. -
Line 2, Column 1: [Suggestion: description-missing - See documentation]
Missing required attribute: 'description'.
docs-ref-services/preview/core-serializer-json-jackson-readme.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'.
docs-ref-services/preview/cosmos-db.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Docs Build status updates of commit 4484372:
:warning: Validation status: warnings
docs-ref-services/preview/core-http-netty-readme.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'. -
Line 23, Column 5: [Suggestion: preserve-view-not-set - See documentation]
Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
docs-ref-services/preview/core-test-readme.md
-
Line 2, Column 1: [Warning: ms-prod-missing - See documentation]
Missing attribute: 'ms.prod'. If you specify 'ms.technology', you must also specify 'ms.prod'.
docs-ref-services/preview/core-amqp-readme.md
-
Line 23, Column 5: [Suggestion: preserve-view-not-set - See documentation]
Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
docs-ref-services/preview/core-http-okhttp-readme.md
-
Line 2, Column 1: [Suggestion: description-missing - See documentation]
Missing required attribute: 'description'. -
Line 21, Column 5: [Suggestion: preserve-view-not-set - See documentation]
Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
docs-ref-services/preview/core-readme.md
-
Line 31, Column 5: [Suggestion: preserve-view-not-set - See documentation]
Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
docs-ref-services/preview/core-serializer-json-gson-readme.md
-
Line 2, Column 1: [Suggestion: description-missing - See documentation]
Missing required attribute: 'description'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Docs Build status updates of commit 57bf645:
:white_check_mark: Validation status: passed
docs-ref-services/preview/core-http-netty-readme.md
-
Line 22, Column 5: [Suggestion: preserve-view-not-set - See documentation]
Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
docs-ref-services/preview/core-http-okhttp-readme.md
-
Line 22, Column 5: [Suggestion: preserve-view-not-set - See documentation]
Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Docs Build status updates of commit 50661d9:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Global effort to fix build validation errors
@amishra-dev
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you’d like to see. Thank you!