Update lnxGettingStarted.md#8254
Update lnxGettingStarted.md#8254sdwheeler merged 3 commits intoMicrosoftDocs:stagingfrom mgreenegit:patch-7
Conversation
|
Docs Build status updates of commit 17598aa:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/docs-conceptual/dsc/getting-started/lnxGettingStarted.md | View (>=powershell-5.1) | Details |
reference/docs-conceptual/dsc/getting-started/lnxGettingStarted.md
- Line 15, Column 3: [Warning: file-not-found - See documentation]
Invalid file link: '../../../../azure/governance/policy/concepts/guest-configuration-custom'.
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 c85f6d3: ✅ Validation status: passed
reference/docs-conceptual/dsc/getting-started/lnxGettingStarted.md
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:
|
|
Docs Build status updates of commit 94e5576: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
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:
|
|
Docs Build status updates of commit 94e5576: ✅ 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:
|
PR Summary
PR Context
Select the area of the Table of Contents containing the documents being changed.
Conceptual content
Cmdlet reference & about_ topics
PR Checklist
WIP:or[WIP]to the beginning of thetitle and remove the prefix when the PR is ready.