Skip to content

Migrate docs build to use PSMD2Yaml and new page template #12185

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Saisang
Copy link
Contributor

@Saisang Saisang commented Jun 27, 2025

When MAML2Yaml is not in the path of monikerMapping.json, reference content in the docset will be built by PSMD2Yaml instead of its predecessor MAML2Yaml. For details, see https://dev.azure.com/ceapex/Engineering/_workitems/edit/783982

Copy link
Contributor

Learn Build status updates of commit d1a13c0:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
❌Error Details

  • Line 0, Column 0: [Error: PSMD2Yaml_InternalError] Internal Error: PowerShell script not found: C:\Program Files\docs-pipeline\Scripts\Get-InstalledPlatyPSVersion.ps1

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.

@Saisang Saisang marked this pull request as draft June 27, 2025 06:07
@Saisang Saisang closed this Jun 27, 2025
@Saisang Saisang reopened this Jun 27, 2025
Copy link
Contributor

Learn Build status updates of commit d1a13c0:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
❌Error Details

  • Line 0, Column 0: [Error: PSMD2Yaml_InternalError] Internal Error: PowerShell script not found: C:\Program Files\docs-pipeline\Scripts\Get-InstalledPlatyPSVersion.ps1

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.

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.

2 participants