-
Notifications
You must be signed in to change notification settings - Fork 398
Migrate docs build to use PSMD2Yaml and new page template #3667
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
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@sdwheeler Could you fix the errors?
And the warnings:
The other errors/warnings would be fixed in next batch by xmdanni. |
See fixes in #3670 |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@sdwheeler Hi Sean, there is one warning left, would you please refer to this build log and fix it? That's caused by file name case. |
This should be fixed by #3679 |
Learn Build status updates of commit f580079: ✅ Validation status: passed
For more details, please refer to the build report. |
@mtrilbybassett @sdwheeler @xmdanni The PR is ready for review. Preview page https://review.learn.microsoft.com/en-us/powershell/module/az.accounts/add-azenvironment?view=azps-12.5.0&branch=pr-en-us-3667 |
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