Update Contoso case study to reference Windows 11 instead of Windows 10 #13758
Conversation
…tion in Contoso case study
|
@microsoft-github-policy-service agree |
|
Learn Build status updates of commit 98565f1:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| Details | |||
| microsoft-365/enterprise/contoso-case-study.md | Details | ||
| microsoft-365/enterprise/contoso-identity.md | Details | ||
| microsoft-365/enterprise/TOC.yml | Details | ||
| .openpublishing.redirection.enterprise.json | ✅Succeeded | ||
| microsoft-365/enterprise/contoso-win10.md | ✅Succeeded | ||
| microsoft-365/media/contoso-win10/contoso-win10-fig1.png | ✅Succeeded | n/a (file deleted or renamed) | |
| microsoft-365/media/contoso-win11/contoso-win11-fig1.png | ✅Succeeded |
- Line 0, Column 0: [Warning: redirected-file-not-removed - See documentation]
Redirected file 'enterprise/contoso-win10.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
microsoft-365/enterprise/contoso-case-study.md
- Line 50, Column 3: [Warning: file-not-found - See documentation]
Invalid file link: 'contoso-win11.md'.
microsoft-365/enterprise/contoso-identity.md
- Line 79, Column 87: [Warning: file-not-found - See documentation]
Invalid file link: 'contoso-win11.md'.
microsoft-365/enterprise/TOC.yml
- Line 599, Column 13: [Warning: file-not-found - See documentation]
Invalid file link: 'contoso-win11.md'.
For more details, please refer to the build 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:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
D’oh! Missed the biggest part of this PR…
|
Learn Build status updates of commit f036d62: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Is there a reason for closing this please, @garycentric? @kelleyvice-msft is currently reviewing. |
@connorgurney-me Kelley will review your commits and fix any build issues in a PR in the private repo, where I've fetched your commits. |
Ah, makes more sense! Thanks, Gary. |
3 participants
I'm confident that this PR is comprehensive as I've searched across the entire codebase. However, I'm not 100% sure about the redirect syntax, as there seems to be no public documentation for OPS.