Skip to content

Conversation

@azure-sdk
Copy link
Collaborator

Update docs metadata and targeting for release of azure-template

@azure-sdk azure-sdk requested a review from sima-zhu September 3, 2020 23:30
@opbld32
Copy link

opbld32 commented Sep 3, 2020

Docs Build status updates of commit fae74af:

🕙 Pending: waiting for processors (5 builds ahead of you)

⚠️ Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

@opbld30
Copy link

opbld30 commented Sep 4, 2020

Docs Build status updates of commit fae74af:

⚠️ Validation status: warnings

File Status Preview URL Details
docs-ref-services/template-readme.md ⚠️Warning View (azure-node-latest)
View (azure-node-preview)
View (azure-node-legacy)
Details
docs-ref-autogen/overview/ManagedPartner.yml ⚠️Warning View (azure-node-latest) Details
ci-configs/packages-latest.json ✅Succeeded

docs-ref-services/template-readme.md

  • Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
  • Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
  • Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
  • Line 14: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
  • Line 14: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
  • Line 14: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.

docs-ref-autogen/overview/ManagedPartner.yml

  • [Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingpage.services.managedapplications) has already been defined in docs-ref-autogen/overview/ManagedApplications.yml.

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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants