Skip to content

Conversation

danieljurek
Copy link
Collaborator

No description provided.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 2967ac1:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
❌Error Details

  • [Error: CannotMergeCommit] Cannot merge commit 2967ac1f8c0c2f46f2325d49211b9e8ecd0d7dbe in branch djurek/fix-mgmt-service-level-links of repository https://github.com/MicrosoftDocs/azure-docs-sdk-python into branch main (commit 7e004f0879e08e9104300f0cc8ffea22f9704842). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

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 Learn 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 or suggestions 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:

@danieljurek danieljurek force-pushed the djurek/fix-mgmt-service-level-links branch from 2967ac1 to d3ade7f Compare February 9, 2023 23:39
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit d3ade7f:

⚠️ Validation status: warnings

File Status Preview URL Details
docs-ref-services/latest/key-vault.md ⚠️Warning View (azure-python) Details
docs-ref-services/latest/service-bus.md ⚠️Warning View (azure-python) Details
docs-ref-services/latest/storage.md ⚠️Warning View (azure-python) Details
docs-ref-services/legacy/key-vault.md ⚠️Warning View (azure-python-previous) Details
docs-ref-services/preview/key-vault.md ⚠️Warning View (azure-python-preview) Details
docs-ref-services/preview/storage.md ⚠️Warning View (azure-python-preview) Details

docs-ref-services/latest/key-vault.md

  • Line 2, Column 1: [Warning: ms-date-missing - See documentation] Missing required attribute: 'ms.date'. A freshness date is required for this content set. Add a date in format MM/DD/YYYY.
  • Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'keyvault'.
  • Line 29, Column 41: [Warning: file-not-found - See documentation] Invalid file link: 'keyvault-certificates-readme'.
  • Line 30, Column 34: [Warning: file-not-found - See documentation] Invalid file link: 'keyvault-keys-readme'.
  • Line 31, Column 37: [Warning: file-not-found - See documentation] Invalid file link: 'keyvault-secrets-readme'.
  • Line 13, Column 163: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/key-vault/general/overview' will be broken in isolated environments. Replace with a relative link.
  • Line 41, Column 28: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/keyvault?view=azure-python-previous' will be broken in isolated environments. Replace with a relative link.
  • Line 41, Column 28: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://docs.microsoft.com/python/api/overview/azure/keyvault?view=azure-python-previous

docs-ref-services/latest/service-bus.md

  • Line 2, Column 1: [Warning: ms-date-missing - See documentation] Missing required attribute: 'ms.date'. A freshness date is required for this content set. Add a date in format MM/DD/YYYY.
  • Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'servicebus'.
  • Line 27, Column 80: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/servicebus-readme?view=azure-python' will be broken in isolated environments. Replace with a relative link.
  • Line 27, Column 80: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://docs.microsoft.com/python/api/overview/azure/servicebus-readme?view=azure-python
  • Line 47, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/storage.md

  • Line 2, Column 1: [Warning: ms-date-missing - See documentation] Missing required attribute: 'ms.date'. A freshness date is required for this content set. Add a date in format MM/DD/YYYY.
  • Line 17, Column 18: [Warning: file-not-found - See documentation] Invalid file link: 'storage-blob-readme'.
  • Line 18, Column 19: [Warning: file-not-found - See documentation] Invalid file link: 'storage-queue-readme'.
  • Line 19, Column 24: [Warning: file-not-found - See documentation] Invalid file link: 'storage-file-share-readme'.
  • Line 20, Column 38: [Warning: file-not-found - See documentation] Invalid file link: 'storage-file-datalake-readme'.
  • Line 56, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
  • Line 58, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/storage/blobs/storage-python-how-to-use-blob-storage' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/legacy/key-vault.md

  • Line 31, Column 41: [Warning: file-not-found - See documentation] Invalid file link: 'keyvault-certificates-readme'.
  • Line 32, Column 34: [Warning: file-not-found - See documentation] Invalid file link: 'keyvault-keys-readme'.
  • Line 33, Column 37: [Warning: file-not-found - See documentation] Invalid file link: 'keyvault-secrets-readme'.
  • Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'sttramer' is not a valid Microsoft alias.
  • Line 15, Column 163: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/key-vault/general/overview' will be broken in isolated environments. Replace with a relative link.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
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 Learn 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 or suggestions 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:

@danieljurek
Copy link
Collaborator Author

This can merge

@danieljurek danieljurek merged commit 4971711 into main Feb 10, 2023
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.

1 participant