opbld32
commented
2 years ago Docs Build status updates of commit 1210c5b:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| meganbradley-test/test1.md | :warning:Warning | Details |
meganbradley-test/test1.md
- Line 1, Column 1: [Warning: author-missing - See documentation]
Missing required attribute: 'author'. Add the current author's GitHub ID. - Line 1, Column 1: [Warning: title-missing - See documentation]
Missing required attribute: 'title'. Add a title string to show in search engine results. - Line 1, Column 1: [Warning: ms-author-missing - See documentation]
Missing required attribute: 'ms.author'. Add the current author's Microsoft alias. - Line 1, Column 1: [Warning: ms-prod-or-service-missing - See documentation]
One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services. - Line 3, Column 10: [Warning: yaml-header-syntax-error]
While scanning a multiline plain scalar, found invalid mapping. - Line 1, 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
Microsoft authors of articles need to make updates through the private repository, so the updates can be staged and validated by current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.
It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL:
https://github.com/MicrosoftDocs/{docs-repo}Private repo URL:https://github.com/MicrosoftDocs/{docs-repo-pr}We have closed this pull request. Please resubmit the updates through the private repo. For more information, see the contributor guide.